Closed
Bug 84181
Opened 23 years ago
Closed 23 years ago
Visual Hebrew (ISO-8859-8) needs to be re-ordered in Mail/Browser Default encoding list
Categories
(Core :: Layout: Text and Fonts, defect)
Tracking
()
RESOLVED
FIXED
People
(Reporter: momoi, Assigned: mkaply)
Details
Attachments
(1 file)
(deleted),
patch
|
Details | Diff | Splinter Review |
** Observed with 6/5/2001 Win32 branch build **
Currently there is no way to choose Hebrew (ISO-8859-8) for
mailing messages since it is missing from the Mail Composer selection list.
Related to this is the Edit | Prefs | Mail&Newsgroup |
Composition | Default Mail Send charset.
That list does not contain any item for Arabic or Hebrew.
I think we should expand the list to include these
2 scripts so that users can set appropriate defaults.
Reporter | ||
Comment 1•23 years ago
|
||
I am wondering how important ISO-8859-8 is for mailing
in Hebrew. There is currently no way to choose this
encoding for mail composition.
Comment 2•23 years ago
|
||
The Hebrew and Arabic encodings don't appear in the initial selection list in
Mail Composer, but I was able to add them easily enough with the Customize dialog.
They then also appeared among the options for Default Mail charset.
If it's possible to leave out a specific encoding, ISO-8859-8 should certainly
NOT appear either in Mail Composer or Page Composer, since we have no support
for entering text in visual order.
Reporter | ||
Comment 3•23 years ago
|
||
Simon, more questions.
1. What is the default email encoding for Hebrew mail?
2. Should Visual Hebrew (ISO-8859-8) be available as the
default mail viewing encoding via Edit | Prefs |Mail &
Newsgroups | Mesage Display | Languages?
(The same question for default browser encoding.)
If the answer to these 2 questions are "NO", then we
should resolve this bug as "Wontfix". If the answer to
question #2 is yes, then we should probably keep this
bug open.
Reporter | ||
Comment 4•23 years ago
|
||
The question #1 is so that we can include what is considered
"default" email encodings for Arabic or Hebrew into
the initial default mail compose encoding list. While
you can add these encodings, if we can offer them from the
beginning, that would make it easier for users.
Reporter | ||
Comment 5•23 years ago
|
||
Correction:
> If the answer to these 2 questions are "NO", then we
> should resolve this bug as "Wontfix"
should read as follows instead:
"If the answer to question #2 is "NO", then we
should resolve this bug as "Wontfix". "
Comment 6•23 years ago
|
||
Default mail encoding for Hebrew mail is ISO-8859-8-i
Visual Hebrew should certainly be available as default browser encoding. I don't
think it's necessary as an option for default mail viewing encoding
Reporter | ||
Comment 7•23 years ago
|
||
> Visual Hebrew should certainly be available as
> default browser encoding. I don't think it's necessary
> as an option for default mail viewing encoding.
I think we use the same list for both browser and mail
display encoding defaults.
Based on Simon's comments, I will change this bug into
a request to put in Visual Hebrew (ISO-8859-8)
for the Browser/Mail Display default list.
Changed the summary accordingly and also the
product categry to Browser. The list is probably still
shared by Browser and Mail, so this should get
Visual Hebrew into the Mail View default list as well.
Product: MailNews → Browser
Summary: Visual Hebrew (ISO-8859-8) missing from Mail Composer selection → Visual Hebrew (ISO-8859-8) missing from Mail/Browser Default encoding list
Comment 8•23 years ago
|
||
Is Visual Hebrew really missing, or is the problem that it doesn't appear with
the other Hebrew encodings, but in its alphabetical place?
Should we just change "Visual Hebrew" to "Hebrew (Visual)"?
Assignee | ||
Comment 9•23 years ago
|
||
This line in navigator.properties:
http://lxr.mozilla.org/seamonkey/source/xpfe/browser/resources/locale/en-US/navi
gator.properties#28
Sets the outgoing mail charsets I believe.
Do we need to add Hebrew and Arabic charsets to this list?
Reporter | ||
Comment 10•23 years ago
|
||
> Is Visual Hebrew really missing, or is the problem that it doesn't appear with
> the other Hebrew encodings, but in its alphabetical place?
You're right. Visual Hebrew is in the default list but because the list is sorted alphabetically, it
shows up far apart from the rest of the Hebrew encodings.
I think we should follow Chinese (e.g. Chinese Traditional, Chinese Simplified) by making wording
change as follows:
Hebrew Visual (ISO-8859-8)
Note: We probably should avoid using 2 instances of parentheses.
As to the default Mail composer charset list, I suggest adding only the HE/AR charsets we want to recommend as
Internet mail standards. This is what we do with all other language scripts where there are multiple
charsets in use for browsing. Other encodignsd can be added via the customize dialog
Summary: Visual Hebrew (ISO-8859-8) missing from Mail/Browser Default encoding list → Visual Hebrew (ISO-8859-8) needs to be re-ordered in Mail/Browser Default encoding list
Comment 11•23 years ago
|
||
I agree with momoi, namely that
1) We should have only iso-8859-8-i for Hebrew and iso-8859-6 for Arabic
initially present in the mail charsets menu, and others available by customization.
2) We should rename Visual Hebrew to Hebrew Visual in charsetTitles.properties
Updated•23 years ago
|
QA Contact: momoi → zach
Comment 12•23 years ago
|
||
Mass-move all BiDi Hebrew and Arabic qa to me, zach@zachlipton.com.
Thank you Gilad for your service to this component, and best of luck to you
in the future.
Sholom.
Comment 13•23 years ago
|
||
Reporter | ||
Comment 14•23 years ago
|
||
Tao, please review this patch.
Comment 15•23 years ago
|
||
r=tao. Note that you don't need to change any directory/file under mozilla/l10n.
Comment 16•23 years ago
|
||
Checked in (since http://www.mozilla.org/hacking/reviewers.html says no sr= is
required for a change that only affects localized content)
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
Component: Layout: BiDi Hebrew & Arabic → Layout: Text
QA Contact: zach → layout.fonts-and-text
You need to log in
before you can comment on or make changes to this bug.
Description
•