On 2016-03-11 12:03, Dimitry Sibiryakov wrote: > 11.03.2016 11:56, Mark Rotteveel wrote: >> Please, use UTF-8 for these files (without BOM, BOM is discouraged >> for >> UTF-8). > > Yes, it is discouraged, but it is the only reliable way to detect > file encoding > automatically.
Except that it isn't a reliable way to detect the encoding. It is better to simply say all config files must be UTF-8 and be done with it. > Unfortunately, most of text editors (including Notepad) by default > save files in ANSI > encoding. Forcing configs to be UTF-8 only will cause problems to > not-much-clever users > and a lot of work for support. > Requirement to save configs in UTF-8 with BOM is not too hard to > fulfill for advanced > users if properly documented. No, everything should be UTF-8, no excuses, no exceptions. Almost all tooling for managing or editing config files these days uses UTF-8, holding on to leftovers from the '80s is entirely unnecessary. If a user makes a mistake in a file like this (assuming they even uses non-ASCII filenames), it will be noticed almost immediately because either processing the file would fail due to invalid byte combinations, or the name doesn't match the file.. I consider it a mistake that databases.conf (which is new) doesn't already use UTF-8. I would think that continuing to use or support guesstimate encodings like 'ANSI' in config files would be the bigger mistake. Mark ------------------------------------------------------------------------------ Transform Data into Opportunity. Accelerate data analysis in your applications with Intel Data Analytics Acceleration Library. Click to learn more. http://pubads.g.doubleclick.net/gampad/clk?id=278785111&iu=/4140 Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
