Closed
Bug 132826
Opened 23 years ago
Closed 22 years ago
Need to remove some l10n notes in messenger.properties
Categories
(MailNews Core :: Localization, defect)
Tracking
(Not tracked)
VERIFIED
FIXED
mozilla1.0
People
(Reporter: ji, Assigned: tetsuroy)
Details
(Whiteboard: [ADT3], Got /a=rjesup)
Attachments
(1 file)
1.37 KB,
patch
|
nhottanscp
:
review+
jesup
:
approval+
|
Details | Diff | Splinter Review |
Since bug 57440 is fixed, default folder names are localizable now. We need to remove the following l10n notes in messenger.properties. # LOCALIZATION NOTES (inboxFolderName): DO NOT TRANSLATE (bugzilla #64199) inboxFolderName=Inbox # LOCALIZATION NOTES (trashFolderName): DO NOT TRANSLATE (bugzilla #64199) trashFolderName=Trash # LOCALIZATION NOTES (sentFolderName): DO NOT TRANSLATE (bugzilla #64199) sentFolderName=Sent # LOCALIZATION NOTES (draftsFolderName): DO NOT TRANSLATE (bugzilla #64199) draftsFolderName=Drafts # LOCALIZATION NOTES (templatesFolderName): DO NOT TRANSLATE (bugzilla #23625). # Fix to bug 23625 requires to create template folder URI for new IMAP account, # which requires the folder name to be picked from here like for other special folders templatesFolderName=Templates # LOCALIZATION NOTES (unsentFolderName): DO NOT TRANSLATE (bugzilla #64199) unsentFolderName=Unsent Messages
Comment 1•23 years ago
|
||
L10N issue. L10N group, please triage.
Will fix it. ->nsbeta1+.
Attachment #76773 -
Attachment description: patch for L10N notes update → patch for L10N notes update. It doesn't impact application but giving the correct instruction.
Comment 5•23 years ago
|
||
Comment on attachment 76773 [details] [diff] [review] patch for L10N notes update. It doesn't impact application but giving the correct instruction. r=nhotta Ray, do you want to put a comment for the remaining issue (bug 129530)?
Attachment #76773 -
Flags: review+
If they are the same strings and related, I can. Can you provide the patch?
Comment 7•23 years ago
|
||
132826 Need to remove some l10n notes in messenger.properties Impact Summery Impact Platform: Localization Tools Impact language users: ALL localize build Probability of hitting the problem: N/A Severity if hit the problem in the worst case: N/A Way of recover after hit the problem: N/A Risk of the fix: NONE Potential benefit of fix this problem: This is not a BUG bug a task log. It require to change the comment part of localizable file so the localization will begin to translate some strings that we don't want them to translate. It is NO risk fix.
Comment 8•23 years ago
|
||
This should be adt2 since it will impact all the localization projects based on the English dtd/property files. Without this change, those ~50 localization won't pick up the changes.
Comment 9•23 years ago
|
||
Ray is out on vacation this week. If this needs to get fixed this week, perhaps we should reassign it? Frank - Who do you suggest?
Updated•23 years ago
|
Status: ASSIGNED → NEW
Comment 10•23 years ago
|
||
reassign to yokoyama roy- can you ask for superreview ? this is a NO RISK high impact bug (impact all localization , German, Franch, Japanese, Spanish, etc). roy- after got sr, please mark as adt1.0.0 in the keywords field. thanks
Assignee | ||
Updated•22 years ago
|
Status: NEW → ASSIGNED
Whiteboard: [ADT3] → [ADT3], need /sr
Assignee | ||
Comment 12•22 years ago
|
||
only messenger.properties file change. No need for /sr. Ask for /a
Whiteboard: [ADT3], need /sr → [ADT3], need /a
Comment 13•22 years ago
|
||
Comment on attachment 76773 [details] [diff] [review] patch for L10N notes update. It doesn't impact application but giving the correct instruction. a=rjesup@wgate.com under the assumption that modifications to this file do not require sr=. If they do, please obtain sr= before checkin
Attachment #76773 -
Flags: approval+
Assignee | ||
Updated•22 years ago
|
Whiteboard: [ADT3], need /a → [ADT3], Got /a=rjesup
Comment 15•22 years ago
|
||
adt1.0.0+ (on ADT's behalf) for approval to checkin to 1.0. Pls check this in today. Low risk, that only impacts L10N process.
Assignee | ||
Comment 16•22 years ago
|
||
checked-in
Assignee | ||
Comment 17•22 years ago
|
||
marking as FIXED
Status: ASSIGNED → RESOLVED
Closed: 22 years ago
Resolution: --- → FIXED
Updated•20 years ago
|
Product: MailNews → Core
Updated•16 years ago
|
Product: Core → MailNews Core
You need to log in
before you can comment on or make changes to this bug.
Description
•