On 03/23/2016 12:04 PM, Mark Rotteveel wrote: > On 22-3-2016 15:10, Alex Peshkoff wrote: >> On 03/22/2016 04:54 PM, Jim Starkey wrote: >>> On 3/22/2016 8:33 AM, Dimitry Sibiryakov wrote: >>>> Hello, All. >>>> >>>> Because there is nothing like isc_spb_lc_ctype, must be established >>>> a rule for >>>> determining of encoding of all strings passed into services and back. I >>>> suggest to use >>>> following: >>>> If isc_spb_utf8_filename is included in SPB, all strings are >>>> supposed to be in UTF8. >>>> Otherwise they are in ANSI code page on Windows and current locale >>>> on *nix. >>>> >>>> Do you agree? >>>> >>> I don't agree. It would be better all around if everything passing over >>> the wire is passed as utf-8. >> Certainly - but we must support old clients. > In that case wouldn't it be better to bump the SPB version and declare > that from that version strings buffers are UTF-8 only?
isc_spb_utf8_filename is enough, see no need to have new version. Version is bumped when clumplets format is changed incompatibly (like use of 32-bit clumplet length in new SPB version). Changing encoding rules does not look like such change. ------------------------------------------------------------------------------ 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=278785351&iu=/4140 Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
