157979 - Need seperate header for printing

Status: RESOLVED FIXED

(MailNews Core :: Printing, defect)

Description

[Ying-Lin Xia]

Currently the mail printing header is sharing same strings with mail 
forward-as-attachment, in file mimeheader.properties. We need to seperate them, 
cause for localization, we need to keep the forward header in English, but 
localize the print header.

Comment 1

[nhottanscp]

This is mail specific.

Comment 2

[Ying-Lin Xia]

This problem is found in bugscape bug 15671:

With the current Ja build, when a mail is printed out, the header lables, like
Subject: To: and etc. are still in English.
Please refer the following fixed i18n bug:
http://bugzilla.mozilla.org/show_bug.cgi?id=86980
and bug for l10n notes:
http://bugzilla.mozilla.org/show_bug.cgi?id=125446,

But please make sure the fix for this bug doesn't introduce regressions to bug 
14230

------- Additional Comment #4 From [e-mail] 2002-07-17 10:49 -------

According to nhotta, we won't localized the header lables, like
Subject: To: and etc. They should be in English.

------- Additional Comment #5 From Naoki Hotta 2002-07-17 11:10 -------

That is true for message compose/send (for JA build). For message view/print, 
we
can localize them. I think the current problem is that the strings are shared
for view and compose.

------- Additional Comment #6 From Ying-Lin Xia 2002-07-17 13:48 -------

Right, I just made a test. The strings in file mimeheader.properties are shared 
by both print and forward-as-attachment. Which means we can not translate it 
now.

Comment 3

[nhottanscp]

There is another file called "mime.properties" which also has "To", "From", etc.

Comment 4

[nhottanscp]

I think I can change nsMimeBaseEmitter::MimeGetStringByName to get the string
differently based on 'mFormat' value. We want to avoid the localized strings to
be quoted and sent out (e.g. to the receiver who cannot handle the localized
strings).
The function currently uses mimeheader.properties. I can change it to use
mime.properties for quoting if we are sure that is not localized.
Basically, either mimeheader.properties or mime.properties has to stay unlocalized.

Comment 5

[nhottanscp]

Attachment: Use tranlated strings for headers if not quoting.

Comment 6

[Jean-Francois Ducarroz]

Comment on attachment 104195 [details] [diff] [review]
Use tranlated strings for headers if not quoting.

R=ducarroz

Comment 7

[David :Bienvenu]

I think nsCRT::strcmp is deprecated, though it does check for null args, so if
the strings might be null, you could still use it, I guess.

doesn't this leak val? should we use nsXPIDLString?
+    PRUnichar *val = nsnull;
+
+    res = m_stringBundle->GetStringFromID(aID, &val);
+
+    if (NS_FAILED(res)) 
+      return nsnull;
+
+    return ToNewUTF8String(nsAutoString(val));
+  }

Comment 8

[nhottanscp]

Attachment: Changed to use strcmp, fixed the leaks.

Comment 9

[David :Bienvenu]

Comment on attachment 104207 [details] [diff] [review]
Changed to use strcmp, fixed the leaks.

sr=bienvenu

Comment 10

[nhottanscp]

checked in to the trunk