153150 - Need to be able to control page encodings (Character coding menu)

Status: VERIFIED FIXED

(Camino Graveyard :: General, defect)

Description

[Simon Fraser [no longer active]]

From: Shoshannah Forbes <[e-mail]>
Newsgroups: public.mozdev.chimera
Subject: Chimera international support
Date: Thu, 20 Jun 2002 19:17:22 +0300

I have been using Mozilla for a while on OSX/9 to browse Hebrew web 
pages. Since I wanted something faster, I went and downloaded Chimera 
0.3.0.

I looks great and is indeed much faster then Mozilla. However, I didn't 
find any place where I can control the Encodings. No problem with pages 
with a correct charset declaration, however there is no way to set the 
correct default encodings for pages that do not specify encoding, or to 
override pages which specify incorrect encodings. I am I missing 
something? Or is that feature really missing? What are the plans 
regarding incorporating internation support into chimera?

Comment 1

[Shoshannah Forbes]

Considering the number of pages out there with missing or incorrect encoding, it
is close to impossible to use chimera for browsing international pages. This is
a major issues for non Latin1 users (basicly, most of the world)

Comment 2

[Greg K.]

Looks like we need a Chimera Internationalization meta bug.

Comment 3

[saari (gone)]

we should revisit the need for charset control in a bit. CC'ing ftang

Comment 4

[Mike Pinkerton (not reading bugmail)]

other embedding projects are using some new encoding sniffer code that they're
quite happy with instead of the heinous encoding menu. i'd prefer we hook up that.

Comment 5

[Shoshannah Forbes]

Re: the encoding sniffer- How does it work with pages that have incorrect
encoding marked?
Does it work with all encodings? Even those that do not have autodetect feature
in mozilla (like Hebrew).

Re Comment #2 : Should I open such a bug? Who should I assign it to?

Comment 6

[Brant Gurganus]

[RFE] is deprecated in favor of severity: enhancement.  They have the same meaning.

Comment 7

[kaldari]

*** Bug 180703 has been marked as a duplicate of this bug. ***

Comment 8

[Shoshannah Forbes]

Is anything going on here? Are we at least going to be able to set deafult
encoding when none is set in the page? I am sick of tired being unable to view
pages since they didn't specify encodings and I have no way to tell chimera what
to use.

The encoding sniffer does not help, since it doesn't support Hebrew in any of
the mozilla porjects.

I really think we should up the severty of this bug, since it is not a "nice to
have" feature, but it is actaully prevnting from viewing web sites.

for example:
http://www.rest.co.il/yoezer/

Comment 9

[Simon Fraser [no longer active]]

I would agree that this is a serious issue for many international users.

Comment 10

[Joshua Ochs]

Reposting a useful comment from one of the duplicates of this bug, for those who
are having trouble with the universal detector change made in mid-November:

In the meantime, you can turn universal auto-detect on manually by deleting the
following line in all-chimera.js (which is inside the Chimera package):

pref("intl.charset.detector", "universal_charset_detector");

Comment 11

[Shoshannah Forbes]

>you can turn universal auto-detect on manually

too bad this dos not helplanguages the auto detector does not cover, like hebrew :-(

Comment 12

[Simon Fraser [no longer active]]

*** Bug 184543 has been marked as a duplicate of this bug. ***

Comment 13

[Tobias Weber]

To Joshua's comment: I don't know what change you refer to, but if there are two
detectors now, http://aoshimak.tripod.co.jp/ is only correctly displayed *with*
the all-chimera.js hack.

Comment 14

[Suraj K. Rai]

I tried adding the intl.charset.detector pref as per comment 10 but I was not
able to render http://aoshimak.tripod.co.jp/ properly.  Btw...what is the
all-chimera.js hack?

I think the best solution is to have the Character Encoding menu AND also a
preference for selecting the default encoding.  Mozilla and IE both have both of
these features.  Omniweb supports default encoding via preferences.  Chimera
should at least support one of these if not both.

Comment 15

[Tobias Weber]

Re Suraj: By *with* hack I mean the pref() line has to be *removed* to display
the page. So whatever this changes, I'd make it the default ;-)

Comment 16

[Shoshannah Forbes]

I will repeat again:
There are languages which are supported by mozilla/chimera, that are not
detected by the autodetect.
Therefore, relaying on the autudetect and those hack, will not work users of the
above languages.
Having the menu / option for default encoding are a must- not an extra.

Comment 17

[Shoshannah Forbes]

did you notice that this is the only Mac osx browser _without_ and encoding
menu? Even the new Apple Safari (a browser with a very simple UI) has one.
There is a reason for that.
Thanks

Comment 18

[Mike Pinkerton (not reading bugmail)]

landed one equiv to safari's. worked for the simple sites i tried, obviously not
an exhaustive test. I'll leave that to the experts ;)

Comment 19

[kaldari]

Tested on http://aoshimak.tripod.co.jp/. Works great.

Comment 20

[Suraj K. Rai]

Excellent! It works great.  Now the thing that would make it complete is if we
could set our default encodings in systems preferences.  Maybe that should be
filed as another bug/feature request.

Comment 21

[Suraj K. Rai]

I meant Chimera Preferences and not Systems Preferences.

Comment 22

[kaldari]

Suraj,check out bug 161337 and bug 182610. They cover the issues you mention.

Comment 23

[Simon Fraser [no longer active]]

Another thing we may want to do is store a charset for a bookmark, if you change
the charset while viewing a bookmarked page.