Displaying 4 results from an estimated 4 matches for "multibytetoutf16".
2011 Sep 06
0
[LLVMdev] [cfe-dev] Unicode path handling on Windows
...d when they are in fact multibyte strings.
Now I really hope I haven't broken anything because llvm::sys::fs::exists is
called in a number of places, but I'm guessing that none of the paths that
are passed to it are really UTF8?
I think entire llvm::sys::fs module should be changed to use
MultibyteToUTF16 instead of UTF8ToUTF16 before calling windows api functions
(unless somebody knows that we actually have UTF8 paths on windows somewhere
in the code)?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20110906/06...
2011 Sep 02
2
[LLVMdev] [cfe-dev] Unicode path handling on Windows
The patch should work for unicode filename, I just realized that it doesn't
work for unicode directories. FileSystemStatCache calls ::stat for
directories, and this doesn't work for utf8 input the same way ::open
doesn't work. I tried to replace it with ::_wstat but this function has a
different signature. I think we should take a different approach:
1. convert all command line input
2011 Sep 07
2
[LLVMdev] [cfe-dev] Unicode path handling on Windows
...fact multibyte strings.
>
> Now I really hope I haven't broken anything because llvm::sys::fs::exists is called in a number of places, but I'm guessing that none of the paths that are passed to it are really UTF8?
>
> I think entire llvm::sys::fs module should be changed to use MultibyteToUTF16 instead of UTF8ToUTF16 before calling windows api functions (unless somebody knows that we actually have UTF8 paths on windows somewhere in the code)?
2011 Sep 07
0
[LLVMdev] [cfe-dev] Unicode path handling on Windows
...> > Now I really hope I haven't broken anything because llvm::sys::fs::exists
> is called in a number of places, but I'm guessing that none of the paths
> that are passed to it are really UTF8?
> >
> > I think entire llvm::sys::fs module should be changed to use
> MultibyteToUTF16 instead of UTF8ToUTF16 before calling windows api functions
> (unless somebody knows that we actually have UTF8 paths on windows somewhere
> in the code)?
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/att...