Re: charset="ISO-8859-15"



On 6/28/06, Kurt Maute <kurt maute us> wrote:
We've got a Spanish translation of the Planner user guide, and it seems
to use ISO-8859-15 as its character set rather then UTF-8 (i.e. it needs
charset="ISO-8859-15" in its header in order to transform correctly.

Is there any rule or guideline against this?
...or maybe more importantly, any rule that we must use UTF-8?

For application translations (regular po files), we do require them to
be encoded in UTF-8.

I'm not sure of whether we have any similar formal requirement for
docs translations, but I think it would not make sense not to have it,
given the above.

I think you're pretty safe to give the offending translator a slap and
tell him or her to start using UTF-8. ;-)


Christian



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]