Christopher Barker wrote:
> Michael Droettboom wrote:
>
>> I think the real reason this wasn't done is that its tricky to do at the
>> C level in a cross-platform way. At present it uses the regular POSIX
>> fopen in C, which isn't really "Unicode aware".
>>
>
> The actual error is from
Michael Droettboom wrote:
> I think the real reason this wasn't done is that its tricky to do at the
> C level in a cross-platform way. At present it uses the regular POSIX
> fopen in C, which isn't really "Unicode aware".
The actual error is from trying to put the filename in a std::string,
b
I think the real reason this wasn't done is that its tricky to do at the
C level in a cross-platform way. At present it uses the regular POSIX
fopen in C, which isn't really "Unicode aware". See the "Unicode
filenames" section of the link below for some of the complications.
Linux is particu
