http://d.puremagic.com/issues/show_bug.cgi?id=8020
--- Comment #5 from Dmitry Olshansky <[email protected]> 2012-05-04 07:48:07 PDT --- (In reply to comment #4) > Dmitry, we should not assume the name string is in UTF8, it may be also some > another 8-bit code page in being supported in Windows, like 125x and so on. > Such encoding should be done by application itself. Nope, char is UTF-8 codeunit period. See TDPL, language spec etc. Legacy one-byte encodings should be transfered in bytes/ubytes whatever. BTW NTFS is UTF-16 (or subset of it). > What I think is to have File/open/popen( wstring, string mode ) which should > care about UTF16 names. Surprisingly I found some links in DMC includes to > _wfopen receiving wchar_t which should exacly help here. Then someone just needs rig current std.file to call toUTF16/toUTFz (see std.uni) and forward the result to the right _wfopen on win32. UTF-16 been the defacto standard in Windows for a looong time. This is all is just embarracing. -- Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email ------- You are receiving this mail because: -------
