Re: [boost] Fw: [locale] Formal review of Boost.Locale library

Subject: Re: [boost] Fw: [locale] Formal review of Boost.Locale library
From: Mathieu Champlon (m.champlon_at_[hidden])
Date: 2011-04-15 04:27:36

On 14/04/2011 21:11, Artyom wrote:
> Yes, boost::locale::translate receives "char *" as input
> as it uses ASCII text as key.
>
> You write the code originally in English using ASCII
> and they translated to Wide Strings or to narrow
> according to the context.
>
> So basically your keys or original text should be ASCII
> (and gettext would warn you if it does not)
>
> However translations are anything you wish.
>
> If you want to embed Japanese to the text you
> are welcome to do this but in such case you
> do not need translate.
>
> Only when the message is not found in dictionary
> it is converted to wide strings by simple
> casting each ASCII character to wide one.
>
> This is how gettext (and most other translations
> systems) work.
>
> There is nothing wrong with this.
>

Hi,

For having worked in Japan for a while I can assure you that most 
programmers not only do not speak english but they also do not read it.
The work-flow you describe is actually impracticable for them.

If for instance a Japanese company is building a product for the 
Japanese, Korean and Chinese markets (and that's it), it's a bit 
cumbersome to suggest they should hire a programmer who can understand 
English in order to take care of the translation code.
And the same goes for the localization company they will likely 
subcontract the translations to...

MAT.