Even though I have no vote, I would say stick with ISO-8859-1 or similar.
Writing documentation in xml is fine, but if a translator has to start converting all his chars (�, �, �, �, �, �) to unicode, it will be a bit of a hassle.


�Tetsuya, out of curiosity, what is your favourite editor that doesn't support latin1?

If localized files/docs could use local STANDARD encodings, it would make life easier on translators. Tetsuya, you could write directly in kanji (is that the right name?) :-)

My 2 cents,
  Agust�n.

Tetsuya Kitahata wrote:

Hello,

I think that some of current documents (e.g. news.xml, trans/es/*.xml)
have "ISO-8859-1" encoding style. However, my favorite text editor
can not read them properly (garbled chars) at the point of "Umlauts" and "Ntildes" etc.


I want these particular letters to be converted into "Unicode Escape Sequence Style" (\uxxxx).

Also, the header lines of the xmls, <?xml version="1.0" encoding="ISO-8859-1"?>
->
<?xml version="1.0" encoding="UTF-8"?>


Thirdly, I want the guideline of translations to be slightly
changed to be fit in these above.

Any thoughts?

If there's no objections, I think I can do this by myself.
(Just using "native2ascii" with codepage 1252)

Sincerely,

-- Tetsuya ([EMAIL PROTECTED])

--
<Agustin/>

Agust�n Mart�n Barbero
agusmb at netscape dot com
agusmba at terra dot com




--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to