Displaying 3 results from an estimated 3 matches for "convert_utf8_to_utf16".
2011 Sep 01
3
[LLVMdev] [cfe-dev] Unicode path handling on Windows
...probably use LLVM_ON_WIN32 instead of WIN32 but this macro isn't
defined inside FileSystemStatCache and MemoryBuffer for some reason. Both of
these files have an #ifdef section that deals with O_BINARY so maybe these
two sections should be consolidated?
- Functions convert_multibyte_to_utf8 and convert_utf8_to_utf16 have
definitions only on windows so every other platform is currently broken.
On Thu, Sep 1, 2011 at 5:44 PM, Ruben Van Boxem <vanboxem.ruben at gmail.com>wrote:
> Isn't it more straightforward to use utf-8 internally and use the
> conversion functions provided by the win32 API wh...
2011 Sep 01
0
[LLVMdev] [cfe-dev] Unicode path handling on Windows
Op 1 sep. 2011 14:12 schreef "NAKAMURA Takumi" <geek4civic at gmail.com> het
volgende:
>
> Guys, welcome to the too weird i18n world!
> We, Japanese, has got suffered for multibyte charset for 20 years.
>
> I have added a comment in http://llvm.org/bugs/show_bug.cgi?id=10348 .
> Of course I know, I don't think it would be a practical resolution.
>
> FYI,
2011 Sep 01
3
[LLVMdev] [cfe-dev] Unicode path handling on Windows
Guys, welcome to the too weird i18n world!
We, Japanese, has got suffered for multibyte charset for 20 years.
I have added a comment in http://llvm.org/bugs/show_bug.cgi?id=10348 .
Of course I know, I don't think it would be a practical resolution.
FYI, it seems clang can retrieve mbcs path with s/CP_UTF8/CP_ACP/g.
E>bin\clang.exe -S なかむら\たくみ.c
なかむら\たくみ.c:4:2: error: #error
#error
^
1