Bug#408220: iceape-browser: Composer declares wrong encoding

Mike Hommey mh at glandium.org
Sat Jan 27 17:26:19 CET 2007


On Sat, Jan 27, 2007 at 05:17:15PM +0100, Braun Gábor <braung at renyi.hu> wrote:
> > > The problem: the encoding declared in the file is ISO-8859-1 while the
> > > file itself is UTF-8.
> >
> > Here is a simple work around for you: Select another encoding and select
> > UTF-8 again. It will work then. I'll investigate as to why ISO-8859-1 is
> > not selected.
> 
> The workaround works for me.
> 
> A remark to your last sentence: I think that the preselected charset should be
> the one in the locale (or in a configurable user option) since 
> the user probably uses this charset for the most of his text files.

On this, I don't want to differ too much from upstream, and upstream
decides it from intl.charset.default setting that are defined by each
(seamonkey) locales, which may have unknown impact on the rest of the
suite.

Anyways, I found a way to fix the issue properly, but that also means
iso-8859-1 will be the default charset. But at least it will be
correctly set.
Also note that changing the charset setting in the view menu changes the
meta tag as well as the charset used to save the file.

Mike




More information about the pkg-mozilla-maintainers mailing list