Closed Bug 38834 Opened 24 years ago Closed 24 years ago

oflabel not localizable in file wizardManager.properties

Categories

(Core :: Internationalization: Localization, defect, P3)

Product:
Core
Component:
Internationalization: Localization
Platform:
x86
Windows NT
Type:
defect

Tracking

()

Status:
VERIFIED FIXED

People

(Reporter: amasri, Assigned: alecf)

References

Details

(Whiteboard: [nsbeta2-]) 

in file /chrome/global/locale/wizardManager.properies, the statement, 
oflabel=of, is not sufficient for localization. It should be part of a formatted 
string that includes other elements with which it will be concatenated.
Allan, can you find out who owns this file? Reassign it to the owner and ask for 
the explanation. We should report the concatenation in a sentence as bugs.
This variable also appears in file, 
/profile/resources/locale/en-US/createProfileWizard.properties
Assignee: rchen → alecf
yeah, this is me, but I think someone in i18n needs to explain to me how to do
this. How do I do a formatted string in JS?
Other properties files just use the %ld, %s, %ud, etc. in the proper location in 
the string. See 
http://lxr.mozilla.org/seamonkey/source/mailnews/mime/resources/mime.properties 
for examples. They seem to follow C string formatting rules. 
I know that, what I need is a JavaScript function that will format this stuff
for me (i.e. exposing PR_smprintf or the like from JS)
Bill Law wrote a function that does this for 
http://lxr.mozilla.org/seamonkey/source/xpfe/components/xfer/resources/downloadP
rogress.js
ok, but bill is insane.
before tague left, he said he was going to expose this from JS. I'm going to see 
if I can track it down myself.
cc bobj and ftang.
Blocks: 12394
Keywords: nsbeta2
[nsbeta2+]
Whiteboard: [nsbeta2+]
whoops, operator error, should be nsbeta2-
Whiteboard: [nsbeta2+] → [nsbeta2-]
marking M18.
Target Milestone: --- → M18
we have a method now of formatting strings from JS so this should be an easy
fix.
Status: NEW → ASSIGNED
Keywords: nsbeta3
Fix in hand.
fix went in a few days ago
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
oh no, wait. I just checked that fix in now (it's been in my tree for a few
days)
I verified this in 2000-09-19-05 build.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.