On 16/03/16 11:39, James Starkey wrote: > Or simply restrict database file names to ASCII. It's not like users > have to deal with them, just like they don't have to deal with > identifiers in SQL, or C or Java.
As someone linguistically challenged, I have no problem with my own code, but English is not the most used language on the planet, and for many it creates another complication to programming in their own language, so I can understand that 'restrict database file names to ASCII' is as irritating these days as some of the other 'politically correct' things we have to put up with with. That SQL and other programming languages are essentially 'english' is not real case for only supporting 'english' in the 21st century? But many programming languages and os's still can't cope with this problem anyway so perhaps we have to live with that? :( -- 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
