Quote:
Originally Posted by Tex2002ans
Now speaking of bugs, I ran into a very obscure one. I sent the details in a PM to KevinH many moons ago but never got a response. I will fish that one out and see why I didn't post it publicly, and see if it still is buggy in the latest version.
If I remember correctly it had to do with Exporting/Importing Saved Searches, and differences between Windows/Mac's files with Carriage Returns + Line Feeds.
I am probably the only person in a thousand years who actually tried/used/knew about that functionality.  |
Sorry I just that missed that in my PM. Just responded. Not a bug. Your hand-crafted ini file included a utf-8 BOM which it should not have.
No proper utf-8 file needs a BOM (byte order mark) as 8-bit bytes do not have a byte order!
A BOM really makes sense when using an encoding such as utf-16 as it will clearly demonstrate if the the utf-16 (16 bit values) values were written in Big Endian or Little Endian byte order. (ie. utf-16-le vs utf-16-be)
When you export your saved searches, Sigil properly handles the cr/lf issues and properly creates a utf-8 encoded file that can be read in on any platform that Sigil runs on.
If you hand-create an ini file using a text editor, make sure it outputs utf-8 **without** a BOM (as they are meaningless for a utf-8 encoded text file) or post process it to remove the BOM mark if you want it to load on any platform (Mac, Linux, Windows) running Sigil
KevinH