[prev in list] [next in list] [prev in thread] [next in thread] 

List:       mozilla-i18n
Subject:    RE: Making the encoding selection UI easier to use
From:       Jonathan Rosenne <rosenne () qsm ! co ! il>
Date:       2000-12-23 10:18:32
[Download RAW message or body]

I suggest that the user selection remain in force only while he is in the same
site and the HTML has the same charset specification or lack of it.

When the user moves to another site or the charset specification changes the
selection to return to the default.

Jony

> -----Original Message-----
> From: Jungshik Shin [mailto:jungshik@www.ykga.org]On Behalf Of Jungshik
> Shin
> Sent: Friday, December 22, 2000 6:21 AM
> To: mozilla-i18n@mozilla.org; mozilla-ui@mozilla.org
> Subject: Re: Making the encoding selection UI easier to use
>
>
> In <Pine.LNX.4.10.10012170011060.18824-100000@Sina.sharif.ac.ir>,
> Roozbeh Pournader  wrote:
>
>
> : On 16 Dec 2000, Xslf wrote:
>
> :> I think that the behavior that assumes the default from the previous site
> :> makes sense, since most users I know spend most of their time
> using just one
> :> or two languages, so most pages are in the encoding of the previous page.
>
> : This should of course be optional, since Persian is not encoded in one
> : wrong way only, but many!!
>
> I agree this should be made optional.
>
> Even for those who usually browse web pages in a couple of languages,
> the behavior that you think makes sense can be pretty inconvenient.
> To take myself as an example, frequently I hop between  Korean pages
> (mostly in EUC-KR) and  pages in ISO-8859-1 (even English pages have some
> accent and other characters that go beyound the repertoire of US-ASCII
> which is a subset of all Korean encodings) and the behavior forces me to
> set the encoding manually EVEN if the page I'm viewing has the correctly
> specified encoding either via http header or meta tag.
>
> Jungshik Shin
>

[prev in list] [next in list] [prev in thread] [next in thread]