On 24/07/2015 11:54, Alex Peshkoff wrote: > On 07/24/2015 03:14 PM, Adriano dos Santos Fernandes wrote: >> On 24/07/2015 09:11, Dimitry Sibiryakov wrote: >>> 24.07.2015 13:53, Adriano dos Santos Fernandes wrote: >>>> We could safely assume that a sequence of ascii characters means the >>>> same thing in every charset, as we do not use wide character sets. >>> ASCII characters are not problem. National characters are. >>> >> Things means different things when you selectively trim them out of >> context. So the context: >> >> "For example searching for "inet:" prefix in unicode text file using it >> as utf8 even for english-only script we will have problems." > Adriano, initially it was said that in passwords (to be precise - not > only passwords, but also logins and filenames) from CONNECT command in > ISQL we currently can use international characters, provided they are in > current OS session locale. Next Dimitry pointed out that in a script > they may be provided in another charset, referenced by SET NAMES > command. As far as I understand the discussion is about what can be done > in such case. > This is well known and has said when utf8_dpb tag was implemented.
If Windows is not consistent, we can't do a good thing. Please note that ISQL is just a process. It can be called from another process (not cmd), it can be called with stdin (not -i) redirected, etc. The only problem I see is that you need to hash passwords on the client, and if they are not in UTF-8 (and utf8_dpb is not used), you can't produce a consistent hash to compare to the server one (which was done in UTF-8). Adriano ------------------------------------------------------------------------------ Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
