On 2016-03-11 13:02, Lester Caine wrote:
> On 11/03/16 11:49, Dimitry Sibiryakov wrote:
>> 11.03.2016 12:43, Alex Peshkoff wrote:
>>> > On 03/11/2016 02:28 PM, Dimitry Sibiryakov wrote:
>>>>> >> >11.03.2016 12:19, Alex Peshkoff wrote:
>>>>>>> >>> >>When 2 different files will be opened as same dbb in SS 
>>>>>>> that will be
>>>>>>> >>> >>definitely not very convenient.
>>>>> >> >     SS rely on file name when is looking if database is 
>>>>> already opened?
>>> > Currently yes. The main reason is that inode is missing in NT.
>>    Ok, then we can leave decision about case sensitivity on 
>> comparison to each single
>> piece of code. For internal DB identification and configs we don't 
>> have to have the same
>> rules, right?
>
> The fact that windows does not currently support UTF8 for file names 
> is
> the problem here? Having moved over to Linux for servers some time 
> ago,
> I'm a little behind on just what M$ has done with relation to WCHAR
> encoding, but it's not directly compatible with handling UTF8 within
> applications? While PHP does not fully handle UTF8, it does not 
> mangle
> anything UNTIL it links to windows functions.

Using UTF-8 everywhere is a matter for Firebird. Transcoding to the 
UTF-16 expected by Windows APIs is a problem that should be localized to 
the file access done by Firebird on Windows.

Mark

------------------------------------------------------------------------------
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=278785111&iu=/4140
Firebird-Devel mailing list, web interface at 
https://lists.sourceforge.net/lists/listinfo/firebird-devel

Reply via email to