[wp-polyglots] Tips for translating with Rosetta

[K Suominen]

Also, reading the W3C page, I understand that they encourage writing
the page in the character set that supports all the characters needed
for the page.  Since the author knows the full content of the page, it
is easy.

I have existing content in ISO-8859-1 that I mix in with WordPress
content.  That's why I've set the character set in WordPress to
ISO-8859-1 as well.

Is the intent only to support UTF-8 in localized versions of
WordPress?  I hope not.

+ Kim


On Wed, 16 Feb 2005 10:21:02 -0600, Ryan Boren <ryan at boren.nu> 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
>