[wp-polyglots] Tips for translating with Rosetta

[Morgan Doocy]

I only suggested using escapes because of the fact that Rosetta 
compiles its MO files in UTF-8, and there is no means of converting the 
MOs to the user's character encoding on-the-fly within WordPress. Ryan, 
what do you think about implementing this? It would allow users to 
enter literal characters no matter how they work on translations, and 
not have to worry about it being compatible with the user's selected 
encoding.

Morgan

On Feb 16, 2005, at 8:21 AM, Ryan Boren wrote:

> On Wed, 2005-02-16 at 10:10 -0500, K Suominen wrote:
>> I think you are misunderstanding.
>>
>> The problem you are describing is solved by using entities in the po
>> file, on which there is no disagreement.
>>
>> I just find it quite impractical (I'd like to say "impossible") to
>> enter the translations using entities as opposed to typing the
>> appropriate keys on my keyboard.
>
> Only use escapes for characters in exceptional circumstances. Create
> pages using an encoding that supports all the characters you need.
>
> http://www.w3.org/TR/2004/WD-i18n-html-tech-char-20040509/#IDAPNGO
>
> I suggest everyone use UTF-8 as this is what WordPress (and most
> everything else) supports best.  If you want to put non-UTF-8
> translations in the repository, add the character set to the filename.
> es_ES.ISO-8859-1.po
>
> Ryan
>
>
> _______________________________________________
> wp-polyglots mailing list
> wp-polyglots at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-polyglots