Closed
Bug 74669
Opened 24 years ago
Closed 23 years ago
allow the user to use non localized versions of strings inserted into forward
Categories
(MailNews Core :: Composition, defect)
Tracking
(Not tracked)
RESOLVED
WONTFIX
mozilla1.2alpha
People
(Reporter: sspitzer, Assigned: rchen)
References
Details
spun off of bug #67504
The user who is using the localized version may forward a mail which does not
match with the localized language. For example, when forwarding US-ASCII
message, you may not want to put Japanese string in the message.
we need to do the same thing we need for #23615
1) add a hidden pref (shared by the code we'll write for #23615) to say if the
inserted text should be ASCII version or the localized version
2) add another property to mime.properties that has a localization note "DO NOT
LOCALIZE THIS"
3) fix the code to check the pref to decide what to insert.
nhotta, should the default be "use ASCII" or "use localized"?
let's take this to another bug, instead of reopening this one.
Comment 1•24 years ago
|
||
How about UI for this option? If no UI then I think the default should be "use
ASCII". Cc to msanz, what do you think?
Keywords: l12y
Reporter | ||
Comment 2•24 years ago
|
||
I agree, default to ASCII.
two suggestions:
we could have this as advanced composed prefs, or under some sort of i18n prefs
panel if there are other i18n prefs that would make sense to group together.
Reporter | ||
Comment 3•24 years ago
|
||
for starters, I'd say no UI and make it a hidden pref.
then, we can worry about the UI later.
Kat, what's the feedback from users about this? I remember from the other bug
that this is an old issue that could stay as is. I agree with Seth's last
comment, what do you think?
Comment 5•24 years ago
|
||
This afffects global business users most.
In Japan, we decided some time ago that
keeping headers and simple response line
such as "... wrote:" in ASCII.
The real issue is readability. For ISO-8859-1
languages, at least translated strings can be
displayed. Such is not the case for CJK users
sending ASCII msgs to English speakers.
Keeping the default in ASCII is a good idea but
we should offer an option to L10n folks. Thus
L10n notes should reflect this fact. Something like
"Translate with caution. WerRecommend against
translating for non ISO-8859-1 languages."
Comment 6•24 years ago
|
||
cleaning up nsbranch keywords.
Updated•23 years ago
|
Status: NEW → ASSIGNED
Comment 8•23 years ago
|
||
Reassign, I am working for reply header change as bug 70842.
Assignee: ducarroz → nhotta
Status: ASSIGNED → NEW
Updated•23 years ago
|
Status: NEW → ASSIGNED
Target Milestone: mozilla1.0 → mozilla0.9.7
Comment 9•23 years ago
|
||
Change the summary, the bug is actually for forward instead of reply.
Summary: allow the user to use non localized versions of strings inserted into replies → allow the user to use non localized versions of strings inserted into forward
Comment 10•23 years ago
|
||
For forward, there is a string "-------- Original Message --------" which may be
customized.
But other strings are from the original message headers and I am not sure we
should allow customising them. Currently, they are externalized to .property
file but I am not sure they should be localized.
My current plan is to make only "-------- Original Message --------" to be
editable by moving it to pref.
-------- Original Message --------
Subject: [Bug 74669] allow the user to use non localized versions of strings
inserted into replies
Date: Mon, 29 Oct 2001 10:05:37 -0800 (PST)
From: bugzilla-daemon@mozilla.org
To: nhotta@netscape.com
Updated•23 years ago
|
Target Milestone: mozilla0.9.7 → mozilla0.9.8
Updated•23 years ago
|
Target Milestone: mozilla0.9.8 → ---
Comment 13•23 years ago
|
||
English is just another localization.
When user using a English build and forwarding a Japanese
message, you may not want to put English string in the message neither.
>1) add a hidden pref (shared by the code we'll write for #23615) to say if the
>inserted text should be ASCII version or the localized version
What is ASCII version? English in ASCII ? or French in ASCII ? or Dutch in
ASCII? Why the user prefer send out English instead of French when he is using
Japanese build?
I think this is an over design issue. mark this as wontfix
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → WONTFIX
Comment 14•23 years ago
|
||
Arg. if someone decides to forward an english message to me and they happen to
use a japanese localization the result will be a very ugly message because of
fonting issues. plus mozilla might ask me to download a font just so i can
render text which says in japanese that someone wrote the message.
ascii-7.
Updated•20 years ago
|
Product: MailNews → Core
Updated•17 years ago
|
Product: Core → MailNews Core
You need to log in
before you can comment on or make changes to this bug.
Description
•