On 2/4/22 13:41, Dimitry Sibiryakov wrote:
Alex Peshkoff via Firebird-devel wrote 04.02.2022 9:53:
  Remember me please why isc_lc_ctype isn't used to determine encoding of database name and DPB values?

Due to limitations of WideCharToMultiByte API. (with posix iconv this cabe easily done)

  Do you mean that client would have to have a table matching Firebird charset names and Windows codepages?


Sorry, windows-specific part was implemented not by me. As gar as I know there were more serious problems.
Table will certainly be needed, but IMO it's not too big deal.
I suppose you suggest to fallback to existing way when there is no isc_dpb_lc_ctype in DPB?

BTW, service name during service attach isn't converted into UTF-8 at all.

It was always ascii :D

  Except host name part.


Host name is not sent over the wire.
I doubt names resolver in system using (for example) cp1251 will accept host name in utf8.




Firebird-Devel mailing list, web interface at 
https://lists.sourceforge.net/lists/listinfo/firebird-devel

Reply via email to