Closed Bug 37183 Opened 20 years ago Closed 20 years ago

[i18n]Hardcoded strings in nsMsgStatusFeedback.cpp


(SeaMonkey :: MailNews: Message Display, defect, P3, major)

Windows NT


(Not tracked)



(Reporter: rchen, Assigned: alecf)



(Whiteboard: [nsbeta2+] fix in hand)

I believe "Loading document..." is hardcoded in nsMsgStatusFeedback.cpp:

   setAttribute( rootWebshell, "Messenger:Status", "value", "Loading 
Document..." );

and "Document: Done" is hardcoded at

   setAttribute( rootWebshell, "Messenger:Status", "value", "Document: Done" );

Please move them to properties file.
Keywords: nsbeta2
Target Milestone: --- → M17
Blocks: 12394
Putting on [nsbeta2+] radar.  
Whiteboard: [nsbeta2+]
Thanks for volunteering for these Alec!
Assignee: selmer → alecf
Localizability requirement -> QA contact to myself.
QA Contact: lchiang → momoi
Summary: Hardcoded strings in nsMsgStatusFeedback.cpp → [i18n]Hardcoded strings in nsMsgStatusFeedback.cpp
fix in hand, waiting for tree to open
Whiteboard: [nsbeta2+] → [nsbeta2+] fix in hand
fix is in!
Closed: 20 years ago
Resolution: --- → FIXED
verified with June 2 build
While the strings have been extracted, I don't think we have the
full solution here yet for the following reasons:

1. The dynamic msg status shows up only in a separate mail viewing
   window. In the main Messenger View window, we are still using
   the static text from messenger.dtd file.
2. In a Message Compose window, the status msg is dynamic, but the wording
   is not consistent with other windows. It says "Done loading document"
   while other mail windows (also in 4.x) all say "Document: Done".  While 
   this may be loaded from, there needs to be
   consistency in wording.

and a question,

3. Are the "..statusText.label" in messenger.dtd and messengercompose.dtd
   still needed?

Re-opening for 1 and 2.
Resolution: FIXED → ---
those are different bugs! The bug was making the strings localizable, you're 
talking about aesthetic bugs that have nothing to do with i18n... and they are 
definately not beta stoppers. 

re-closing this bug, please file new bugs if the current behavior is a big deal.
Closed: 20 years ago20 years ago
Resolution: --- → FIXED
OK. I looked into this a bit more and found that the status message
became static some time before the current fix went in. 
The original reason for this bug was that we noticed the status
messages in PR1's Messenger window was only partially localized 
in PR1-Japanese build while they were dynamically changing. 
At PR1, the status message was dynamic. Some of the builds from late 
April still had a dynamic status message while the one from 5/16 does 

Alec, you're right in that there is a separate bug here. But I could
not discount a possibility that another bug was introduced during 
this fix. 
I would hesitate to verify this fix fully. Presumably, the effects of the 
extraction would be there once the other bug is fixed but I can only 
guess that that might be the case for the Messenger window.
In any case I'll file a separate bug for the static message status, 
I'm going to verify this now based on the separate mail
viewing window where I can see the message change and reflect 
what alecf has done for us.  I'll file a new bug on the non-dynamic 
state of the message status.  If that bug is fixed and if these
status msgs don't appear, then I'll re-open the bug. Until then,
let's consider this bug fix verified.
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.