Den 2021-04-19 kl. 17:52, skrev Alex Peshkoff via Firebird-devel:
On 4/19/21 6:43 PM, Dimitry Sibiryakov wrote:In my own recent config parsers I separate ANSI files from UTF-8 files by BOM and handle them accordingly but I use Unicode for internal processing which Firebird doesn't.Telling true I doubt that separating ANSI from UTF8 is actual - noone (well, almost noone) will use utf8 on windows or ANSI on linux. What may be interesting (and does cause troubles) is separating OEM vs. ANSI on windows.
I, for one, use Notepad++ for all my text file editing, and have it set to UTF-8 with BOM as default enconding. I would not be surprised if there are many others with some kind of similar setup.
That said, I tend to not change encoding of existing files, so if the Firebird installation ships with .conf files in a specific encoding, that encoding will probably remain at my site.
Not sure I think core-5198 is a good idea though. You could write in the docs which rules and assumptions regarding encoding are used in Firebird, and leave it at that, assuming those rules and assumptions are reasonable. For example, on Windows, presence of a BOM should be respected of course. If not, try to auto detect, at least distinguish between UTF-8 and ANSI (assuming the codepage of the current locale, e.g. win-1252), and the Windows-native Unicode encoding UTF-16.
Regards, Kjell
<<attachment: kjell_rilbe.vcf>>
Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
