Thanks for the update. Looks like clang can't handle Windows-1252. On Mon, Jul 27, 2015 at 3:01 AM, awt <[email protected]> wrote:
> Alon, it turns out that the source file that I was working on belongs to a > Visual Studio project that was encoded with Windows-1252. I was able to > pass compilation after saving the file with utf-8 encoding. > > > On Sunday, July 26, 2015 at 7:21:10 PM UTC-7, awt wrote: >> >> This is the error that I saw in the compilation stage: >> >> xxx.cpp:49:25: error: illegal character encoding in string literal >> StringClass dummyString(L"<E9>l<E8>ve - <E0> la fa<E7>on - >> ch<E2>teau"); >> >> On Friday, July 24, 2015 at 10:43:39 AM UTC-7, Alon Zakai wrote: >>> >>> What is the exact output? It would help to know what reports the error - >>> the clang frontend, emscripten backend, or another part of the toolchain. >>> >>> On Fri, Jul 24, 2015 at 3:35 AM, awt <[email protected]> wrote: >>> >>>> Hi, >>>> >>>> I have the following string literal in my program: >>>> >>>> "élève - à la façon - château" >>>> >>>> Emscripten reports an error 'illegal character encoding in string >>>> literal' when it encounters the string above. Has anybody come across this >>>> before? >>>> >>>> -- >>>> You received this message because you are subscribed to the Google >>>> Groups "emscripten-discuss" group. >>>> To unsubscribe from this group and stop receiving emails from it, send >>>> an email to [email protected]. >>>> For more options, visit https://groups.google.com/d/optout. >>>> >>> >>> -- You received this message because you are subscribed to the Google Groups "emscripten-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
