Closed Bug 62715 Opened 20 years ago Closed 12 years ago

Clean up and clarify mime.properties and mimeheaders.properties files

Categories

(MailNews Core :: MIME, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: momoi, Unassigned)

References

Details

(Keywords: l12y)

The files "mime.properties" and "mimeheaders.properties" contain
several same items, which are targets for localization.
We would like know which ones are used where so that
proper localization can proceed. (E.g. Followup-to).
Because of uncertainty, L10n could not translate some
of the items.
Sending it to sspitzer while rhp is on vacation.
QA Contact: esther → momoi
Added the 'l12y' keyword.
Keywords: l12y
adding nsbeta1 keyword to localizability bugs
Keywords: nsbeta1
accepting.
Status: NEW → ASSIGNED
OS: Windows NT → All
Hardware: PC → All
marking nsbeta1+ and moving to mozilla0.8
Whiteboard: [nsbeta1+]
Target Milestone: --- → mozilla0.8
QA contact to ji. Some localizabilty bugs are dependent on this bug.
QA Contact: momoi → ji
reassigning to ducarroz
Assignee: sspitzer → ducarroz
Status: ASSIGNED → NEW
moving to mozilla0.9
Target Milestone: mozilla0.8 → mozilla0.9
marking nsbeta1- and moving to future milestone.
Keywords: nsbeta1nsbeta1-
Whiteboard: [nsbeta1+] → [nsbeta1+ 2/13]
Target Milestone: mozilla0.9 → Future
I would suggest to make the comments more clear in both mime.properties and 
mimeheaders.properties so that 
the localizers will know which UI corresponds to which string. If the string 
shouldn't be localized, we need to 
make sure the localization note describes it.  

ducarroz, let's work together to make it happen, shall we?

ok, no problem...
ducarroz, let's talk about it this Thursday (3/15).
In the meeting, ducarroz pointed out "mimeheaders.properties" is no longer used 
in Netscape 6.5. It has been replaced by "msgHdrViewOverlay.dtd" in mail. He 
will either remove the file from Netscape installer or add the comment "This 
file is longer used in Netscape 6.5" in the file. 

As regarding "mime.properties", there is no string used as a protocal or token. 
The strings in the file are mainly for error messages and inline forward 
headers. "It is safe to localize all the srings.", he said.  The only mirror 
problem he can think of is "inline forward" will forward the header strings and 
the receiver will receive the sender's header strings displayed on the mail. If 
the receiver doesn't have the font, it may show garbages.

Kat, please add your comments and let us know what we may be missing. Thanks.

As for mime.properties strings used in error msgs and inline forward headers,
it is OK for them to be localizable but I would be careful about translating
them. For Japanese, I think it would be desirable to leave inline forward
headers in English.
As to error msgs, I would like to know what type of errors before
I make recommendations.
ducarroz, can you answer Kat's question regarding the type of errors msgs in 
mime.properties? We also need to add the comments to the file to indicate which 
strings are used in "inline forward" header.  Thanks.
adding jenm. Please evaluate this one. Someone needs to assign a milestone to this.
Scott - This one says [nsbeta1+ 2/13], but not "cut". Is this targeted to get 
fixed or cut for nsbeta1?
Keywords: nsBranch
Blocks: 99230
cleaning up nsbranch keywords. 
Keywords: nsbranch
No longer blocks: 99230
getting nsbranch- back; I want to keep track of bugs that people nominated and
were latered. This will help us for a first round of bug in the next release

Keywords: nsbranch-
Status: NEW → ASSIGNED
Blocks: 107067
Keywords: nsbranch-
ji - is this still valid? thanks
Depends on: 57115
ji, if this is no longer occurring, then let's close it out.
Whiteboard: [nsbeta1+ 2/13]
There are string items in "mime.properties" and "mimeheaders.properties", which 
caused problems if we localized them. 

Are the bugs fixed yet? If not, ducarroz, can you add the comments to the files?
The strings are:

1000=Subject

# Resent-Comments
## @name MIME_MHTML_RESENT_COMMENTS
## @loc 
1001=Resent-Comments

# Resent-Date
## @name MIME_MHTML_RESENT_DATE
## @loc 
1002=Resent-Date

# Resent-Sender
## @name MIME_MHTML_RESENT_SENDER
## @loc 
1003=Resent-Sender

# Resent-From
## @name MIME_MHTML_RESENT_FROM
## @loc 
1004=Resent-From

# Resent-To
## @name MIME_MHTML_RESENT_TO
## @loc 
1005=Resent-To

# Resent-CC
## @name MIME_MHTML_RESENT_CC
## @loc 
# LOCALIZATION NOTE (1006): Do not translate "CC" below.
1006=Resent-CC

# Date
## @name MIME_MHTML_DATE
## @loc 
1007=Date

# Sender
## @name MIME_MHTML_SENDER
## @loc 
1008=Sender

# From
## @name MIME_MHTML_FROM
## @loc 
1009=From

# Reply-To
## @name MIME_MHTML_REPLY_TO
## @loc 
1010=Reply-To

# Organization
## @name MIME_MHTML_ORGANIZATION
## @loc 
1011=Organization

# To
## @name MIME_MHTML_TO
## @loc 
1012=To

# CC
## @name MIME_MHTML_CC
## @loc 
# LOCALIZATION NOTE (1013): Do not translate "CC" below.
1013=CC

# Newsgroups
## @name MIME_MHTML_NEWSGROUPS
## @loc 
1014=Newsgroups

# Followup-To
## @name MIME_MHTML_FOLLOWUP_TO
## @loc 
1015=Followup-To

# References
## @name MIME_MHTML_REFERENCES
## @loc 
1016=References

# Name
## @name MIME_MHTML_NAME
## @loc 
1017=Name

# Type
## @name MIME_MHTML_TYPE
## @loc 
1018=Type

# Encoding
## @name MIME_MHTML_ENCODING
## @loc 
1019=Encoding

# Description
## @name MIME_MHTML_DESCRIPTION
## @loc 
1020=Description

# Message ID
## @name MIME_MHTML_MESSAGE_ID
## @loc 
1021=Message-ID

# Resent Message ID
## @name MIME_MHTML_RESENT_MESSAGE_ID
## @loc 
1022=Resent-Message-ID

Keywords: nsbeta1
i will...
Keywords: nsbeta1nsbeta1-
Product: MailNews → Core
Assignee: ducarroz → nobody
Status: ASSIGNED → NEW
QA Contact: ji → mime
Product: Core → MailNews Core
Priority: P3 → --
Target Milestone: Future → ---
AFAICT, WFM. 

Closing, file new bugs if there actually are bugs there. This bug doesn't really tell.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.