[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: xgettext outputs UTF-8 is --from-code=iso-8859-1
|
From: |
Laurent Martelli |
|
Subject: |
Re: xgettext outputs UTF-8 is --from-code=iso-8859-1 |
|
Date: |
Wed, 16 Mar 2005 19:55:04 +0100 |
|
User-agent: |
Gnus/5.1007 (Gnus v5.10.7) Emacs/20.7 (gnu/linux) |
>>>>> "Bruno" == Bruno Haible <address@hidden> writes:
Bruno> Laurent Martelli wrote: A way to avoid this is to keep the
Bruno> strings in the source in ASCII, and use an en.po file to
Bruno> convert the ASCII "x" to the multiplication sign.
>> I'm using PHP and the string is HTML so I used the HTML entity
>> × as a workaround.
Bruno> Yes, this is good as well.
>> Since iso-8859-1 is the default encoding for web pages
Bruno> This is not the case any more. It was a normal assumption
Bruno> about 8 years ago. But since ca. 5 years you shouldn't send
Bruno> out HTML pages with non-ASCII characters (except in &...;
Bruno> notation) unless these pages contain a charset declaration
Bruno> like this:
Bruno> <head> <meta http-equiv="content-type" content="text/html;
Bruno> charset=iso-8859-1"> </head>
Bruno> See http://www.w3.org/TR/REC-html40/charset.html for details.
You are perfectly right. But most web servers have a default
Content-Type of which is "text/html; charset=iso-8859-1". And anyway,
we don't have to worry about the user's browser locale provided we set
the content-type.
>> I understand. And I guess this is were msgconv can be used before
>> msgmerge so that for instance fr.po is kept in iso-8859-1.
Bruno> Yes. If the translator cannot use fr.po in UTF-8, she will
Bruno> need to convert it to ISO-8859-1 using msgconv. Before or
Bruno> after the msgmerge step, doesn't matter.
Do you always refer to a translator as "she" ? I thought it was typo
in your previous mail, but now it seems to be rather consistent ;-)
--
Laurent Martelli
address@hidden Java Aspect Components
http://www.aopsys.com/ http://jac.objectweb.org