On 16/03/16 08:18, Александр Пешков wrote: > Could somebody explain why Firebird is in the filename translation > business at all? > > Imagine a system, containing linux server, using UTF-8 encoding, some > linux clients (also UTF-8) and some windows clients (cp1251, I use > russian sample) and using russian name for database file. W/o > translation filenames, received from windows client, will binary differ > from one, used by linux clients and server, which will cause file open > failure.
Given that it's not just Firebird that has a problem with the crap M$ still peddle, more generic solutions exist already. Having used alias.conf for many years and kept the alias to 7bit ASCII characters has been one approach, so perhaps this could be expanded to include several aliases all mapping to the one safely wrapped internal name and path? I do find it strange that people still use OS specific settings on networked systems which could well have problems with that. None of my users even know that it's Firebird providing the grunt, as the hack attempts attest, so shouldn't the inter OS conversion problems be handled in a different way? -- Lester Caine - G8HFL ----------------------------- Contact - http://lsces.co.uk/wiki/?page=contact L.S.Caine Electronic Services - http://lsces.co.uk EnquirySolve - http://enquirysolve.com/ Model Engineers Digital Workshop - http://medw.co.uk Rainbow Digital Media - http://rainbowdigitalmedia.co.uk ------------------------------------------------------------------------------ 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=278785231&iu=/4140 Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
