[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: |
Bruno Haible |
|
Subject: |
Re: xgettext outputs UTF-8 is --from-code=iso-8859-1 |
|
Date: |
Wed, 16 Mar 2005 19:28:36 +0100 |
|
User-agent: |
KMail/1.5 |
Laurent Martelli wrote:
> Bruno> A way to avoid this is to keep the strings in the source in
> Bruno> ASCII, and use an en.po file to convert the ASCII "x" to the
> Bruno> multiplication sign.
>
> I'm using PHP and the string is HTML so I used the HTML entity ×
> as a workaround.
Yes, this is good as well.
> Since iso-8859-1 is the default encoding for web pages
This is not the case any more. It was a normal assumption about 8 years ago.
But since ca. 5 years you shouldn't send out HTML pages with non-ASCII
characters (except in &...; notation) unless these pages contain a
charset declaration like this:
<head>
<meta http-equiv="content-type" content="text/html; charset=iso-8859-1">
</head>
See http://www.w3.org/TR/REC-html40/charset.html for details.
> 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.
Yes. If the translator cannot use fr.po in UTF-8, she will need to convert
it to ISO-8859-1 using msgconv. Before or after the msgmerge step, doesn't
matter.
Bruno