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

Status: RESOLVED WORKSFORME

(MailNews Core :: MIME, defect)

Description

[Katsuhiko Momoi]

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.

Comment 1

[Katsuhiko Momoi]

Sending it to sspitzer while rhp is on vacation.

Comment 2

[Katsuhiko Momoi]

Added the 'l12y' keyword.

Comment 3

[msanz]

adding nsbeta1 keyword to localizability bugs

Comment 4

[(not reading, please use [e-mail] instead)]

accepting.

Comment 5

[scottputterman]

marking nsbeta1+ and moving to mozilla0.8

Comment 6

[Katsuhiko Momoi]

QA contact to ji. Some localizabilty bugs are dependent on this bug.

Comment 7

[scottputterman]

reassigning to ducarroz

Comment 8

[scottputterman]

moving to mozilla0.9

Comment 9

[scottputterman]

marking nsbeta1- and moving to future milestone.

Comment 10

[rchen]

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?

Comment 11

[Jean-Francois Ducarroz]

ok, no problem...

Comment 12

[rchen]

ducarroz, let's talk about it this Thursday (3/15).

Comment 13

[rchen]

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.

Comment 14

[Katsuhiko Momoi]

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.

Comment 15

[rchen]

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.

Comment 16

[Michele Carlson]

adding jenm. Please evaluate this one. Someone needs to assign a milestone to this.

Comment 17

[Jaime Rodriguez, Jr.]

Scott - This one says [nsbeta1+ 2/13], but not "cut". Is this targeted to get 
fixed or cut for nsbeta1?

Comment 18

[Scott MacGregor]

cleaning up nsbranch keywords. 

Comment 19

[msanz]

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

Comment 20

[Michele Carlson]

ji - is this still valid? thanks

Comment 21

[Jaime Rodriguez, Jr.]

ji, if this is no longer occurring, then let's close it out.

Comment 22

[rchen]

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

Comment 23

[Jean-Francois Ducarroz]

i will...

Comment 24

[Magnus Melin [:mkmelin]]

AFAICT, WFM. 

Closing, file new bugs if there actually are bugs there. This bug doesn't really tell.