10-19-2023, 09:30 AM | #16 |
Grand Sorcerer
Posts: 27,992
Karma: 199001268
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
|
It's the encoding of the ini files that changed. Qt6 caused us to have to move to utf-8 encoded ini files (rather than the previous ascii with escaped unicode chars).
Clips and saved searches can be exported/imported. I believe the user is looking for a way to export from Qt6 Sigil in a way that can be imported into Qt5 Sigil. I could be mistaken though. Last edited by DiapDealer; 10-19-2023 at 12:57 PM. |
10-19-2023, 03:12 PM | #17 |
Sigil Developer
Posts: 8,116
Karma: 5450818
Join Date: Nov 2009
Device: many
|
When did Qt6 default to utf-8 for an ini file? I did not see that anywhere?
And going backwards using Qt6 ini files from Sigil-2.x to Sigil 1.x versions is not going to work without some extra python decoding and encoding software being written. Going from Qt5 Sigil-1.x ini files to Qt6 Sigil-2.x files should be automatic when Sigil is first started and no Qt6 ini files are found. Last edited by KevinH; 10-19-2023 at 03:57 PM. |
10-19-2023, 05:31 PM | #18 | |
Grand Sorcerer
Posts: 27,992
Karma: 199001268
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
|
Quote:
Check out the comment here: https://github.com/Sigil-Ebook/Sigil.../main.cpp#L359 in commit: https://github.com/Sigil-Ebook/Sigil...b5644d73727b98 If not for the escaped codepoints from old inis being automatically converted to their utf-8 char counterparts by Qt6, what was it about them that were not backward compatible? Last edited by DiapDealer; 10-19-2023 at 06:30 PM. |
|
10-19-2023, 08:46 PM | #19 |
Sigil Developer
Posts: 8,116
Karma: 5450818
Join Date: Nov 2009
Device: many
|
I thought we did it just to be safe! Now I don't remember. I am getting old!
Update: You are right. Found this in qsetting.cpp history on qtbase on github. https://github.com/qt/qtbase/commit/...564d07e02a90b7 So to convert a Qt6 ini file to Qt5 we must read it as utf-8 and then percent encode.. Last edited by KevinH; 10-19-2023 at 09:13 PM. |
10-19-2023, 09:26 PM | #20 |
Grand Sorcerer
Posts: 27,992
Karma: 199001268
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
|
It was a long time ago. We've been testing Sigil with Qt6 for quite a long time now.
For the record: I'm not really sold on it (export to Qt5 sigil) being a feature we need to incorporate into Sigil. I just wanted to make sure I wasn't going crazy! Those that can update to the latest Sigil--should (in my opinion). And I'm not nuts about adding a feature to the latest Sigil just to make it possible to export clips and saved searches for use with the unsupported Windows 7 versions of Sigil. Perhaps an external tool/script to downgrade a Qt6 INI? Last edited by DiapDealer; 10-19-2023 at 09:38 PM. |
10-20-2023, 02:59 AM | #21 | ||
Enthusiast
Posts: 31
Karma: 10
Join Date: Jun 2011
Location: Lima, Peru
Device: Kindle 10Gen / Kobo Aura HD / Nook STR
|
Hi. Sorry for not being clearer earlier (English is not my native language).
Quote:
Sigil QT5 exports an .ini file (ANSI/escaped) > Sigil QT6 imports it: No problems. Sigil QT6 exports an .ini file (UTF-8) > Sigil QT5 imports it: Special characters end up scrambled. Quote:
We tried to solve it but the online converters we found are somewhat limited: For example, the Spanish word "añadir" used to be stored in QT5 as "a\xf1\x61\x64ir". Online converters just change it to "a\u00f1adir". "\u00"/"\u" could easily be changed to "\x"… but when importing QT5 doesn't know where the unicode chars end and imports them all wrong. ... as a part of the Sigil package? Fair enough! Thank you very much for your answers! |
||
10-20-2023, 07:46 AM | #22 |
Sigil Developer
Posts: 8,116
Karma: 5450818
Join Date: Nov 2009
Device: many
|
I believe that Qt5 uses escaped Latin-1 character encoding (ISO-8859-1) not utf-8.
So to read it convert each \xXX to a byte with hex value XX and interpret it as the iso-8859-1 character it represents. I have no idea what it does when there is no iso-8859-1 character equivalent. Last edited by KevinH; 10-20-2023 at 07:54 AM. |
10-22-2023, 05:41 AM | #23 |
Chalut o/
Posts: 420
Karma: 145424
Join Date: Dec 2017
Device: Kobo
|
For the Windows installer, is there a command line argument to specify the destination directory?
In general: What is the complete list of arguments of the Windows installer? and where I can found it? Context: I try to install Sigil by Chocolatey, but the default location used is not the one I want. I can pass additionnal argument but I absolutly no idea how to found the list of all install args. Thanks |
10-22-2023, 06:30 AM | #24 |
Grand Sorcerer
Posts: 27,992
Karma: 199001268
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
|
I don't really use the installer from the command line on Windows. I don't even know if want you want to do is possible or not. But the command-line parameters available for InnoSetup (which is what sigil uses to create its Windows installer) is here: https://jrsoftware.org/ishelp/index....c=setupcmdline
Good luck. |
10-22-2023, 08:00 AM | #25 |
Chalut o/
Posts: 420
Karma: 145424
Join Date: Dec 2017
Device: Kobo
|
Ok, that work.
/DIR="x:\dirname" Thanks |
Thread Tools | Search this Thread |
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Sigil-1.3.0 Released | DiapDealer | Sigil | 8 | 09-15-2020 08:03 AM |
Sigil-1.2.0 Released | DiapDealer | Sigil | 77 | 07-16-2020 12:55 PM |
Sigil-0.9.18 Released | DiapDealer | Sigil | 20 | 09-13-2019 09:08 AM |
Sigil-0.8.900 released for testing - Wait for Sigil-0.8.901 | KevinH | Sigil | 106 | 10-04-2015 10:41 AM |
Sigil 0.8.2 Released | user_none | Sigil | 12 | 12-22-2014 06:02 PM |