Re: [boost] [locale] Review results for Boost.Locale library

Subject: Re: [boost] [locale] Review results for Boost.Locale library
From: Matthew Chambers (matt.chambers42_at_[hidden])
Date: 2011-04-26 15:56:02

On 4/26/2011 6:41 AM, Mathias Gaunard wrote:
> On 26/04/2011 11:17, Sebastian Redl wrote:
>
>> GCC has options to control both the source (-finput-charset) and the
>> execution character set (-fexec-charset). They both default to UTF-8.
>> However, MSVC is more complicated. It will try to auto-detect the source
>> character set, but while it can detect UTF-16, it will treat everything
>> else as the system narrow encoding (usually a Windows-xxxx codepage)
>> unless the file starts with a UTF-8-encoded BOM. The worse problem is
>> that, except for a very new, poorly documented, and probably
>> experimental pragma, there is *no way* to change MSVC's execution
>> character set away from the system narrow encoding.
>
> A long time ago, I asked Vladimir Prus to help me add an option to Boost.Build that would allow to
> automatically prepend the BOM to source files when using MSVC, but unfortunately he was never able
> to help me do this.
>
> I think that with a Unicode library getting in Boost, this feature is becoming even more important.

Do you mean editing the source file in-place? That would be pure crazy. On the other hand, copying 
the source file to the build directory while prepending the BOM and then building from that would be 
pretty cool! Which one of these were you wanting?

-Matt