Source code which is written in UTF-16

Now I’m using the latest compiled Jucer on Mac, it exports source code in UTF-16. It’s a problem because when I compiled it on Xcode, I got a lot of warnings “warning: null character(s) ignored” and two fatal errors around #include rows.

I had to convert the exported source code to UTF-8 manually everytime I modified the component on Jucer.

I think it should be exported in UTF-8 instead of UTF-16, what do you think about it?

Best regards,

this has been reported already in

there isn’t any patch tho… but i don’t think it would be so difficult to patch…

what about a jucer component flag to select output file encoding ?

I patched my version - last line of jucerDocument:

[code] return headerFile.replaceWithText (h, false, false)

         && cppFile.replaceWithText (cpp, false, false);



Yes, I just hit this myself. Very annoying that gcc can’t understand it, but I think bruce’s patch is the best way to go with this.

Ohh… I’m so sorry.

I also vote for the idea! :slight_smile:

Thanks Bruce and Jules, I will choose that patch for the moment. :slight_smile:

Best regards,