Closed
Bug 450488
Opened 16 years ago
Closed 15 years ago
[de] Mistakes in german localisation /browser
Categories
(Mozilla Localizations :: de / German, defect)
Mozilla Localizations
de / German
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: atopal, Assigned: atopal)
Details
(Keywords: fixed1.9.0.4)
Attachments
(1 file)
1.46 KB,
patch
|
Pike
:
approval1.9.0.4+
|
Details | Diff | Splinter Review |
chrome\browser\pageInfo.properties => generalSiteIdentity [Unnecessary escaped character \D] Die Website gehört %S\Dies wurde bestätigt von %S >>> Hier sollte bestimmt ein \n Zeilenumbruch sein, oder? Message: found diff at chrome\browser\places\places.dtd => cmd.find.key ORIGINAL: f LOCALIZED: s >>> warum hatten wir im Deutschen einen anderen Key? Muss das sein? ERROR: different expression(s) at chrome\browser\search.properties => error_loading_engine_msg2 ORIGINAL: %S could not download the search plugin from: %S LOCALIZED: Die Suchmaschine konnte nicht heruntergeladen werden von: %S >>> Da die Variablen nicht nummeriert sind, wird vermutlich ein falscher String verwendet, wenn wir die erste Variable einfach auslassen (oder die Reihenfolge nicht einhalten), oder nicht?
Assignee | ||
Updated•16 years ago
|
Status: NEW → ASSIGNED
Assignee | ||
Comment 1•16 years ago
|
||
Pike, do you see a solution here? I dont't want to use the first variable, but only the last for "%S could not download the search plugin from: %S"
Assignee | ||
Comment 2•16 years ago
|
||
Attachment #339473 -
Flags: approval1.9.0.3?
Comment 3•16 years ago
|
||
The second one is en-US: error_loading_engine_msg2=%S could not download the search plugin from:\n%S de: error_loading_engine_msg2=Die Suchmaschine konnte nicht heruntergeladen werden von:\n%S Sounds like %S konnte die Suchmaschine nicht herunterladen von:\n%S
Assignee | ||
Comment 4•16 years ago
|
||
Yes, but in German we don't want to "antropologize" the browser.
Updated•16 years ago
|
Summary: Mistakes in german localisation /browser → [de] Mistakes in german localisation /browser
Updated•16 years ago
|
Hardware: PC → All
Updated•16 years ago
|
Attachment #339473 -
Flags: approval1.9.0.4? → approval1.9.0.4+
Comment 5•16 years ago
|
||
Comment on attachment 339473 [details] [diff] [review] small fixes a=me for 3.0.4, please land with a check-in comment referencing this bug and my approval, and use the fixed1.9.0.4 and verified1.9.0.4 keywords to track landing and testing.
Comment 6•16 years ago
|
||
Already fixed on trunk?
Assignee | ||
Updated•16 years ago
|
Keywords: fixed1.9.0.4
Assignee | ||
Comment 7•16 years ago
|
||
Pike, anything we can do, if we don't want to use the first %s, or do we have to wait for L20n to do things like that?
Comment 8•16 years ago
|
||
There was a trick to actually use %1$0S or so to use the string, but with zero width. I used to know how to specify the width, but don't ad-hoc.
Assignee | ||
Comment 9•16 years ago
|
||
Do you, by any chance, know where to look that up? I'd really rather not "antropologize", if there is other way. And we should document that in the Wiki, I'm sure we are not the only locale with that problem-
Comment 10•16 years ago
|
||
It's using http://mxr.mozilla.org/mozilla-central/source/xpcom/glue/nsTextFormatter.cpp#945, not exactly sure how that's phrased. Either reverse engineer the code or trial and error. Notes are welcome on http://developer.mozilla.org/Talk:En/XUL_Tutorial/Property_Files
Comment 11•16 years ago
|
||
Mir ist gerade noch eine Unstimmigkeit zu error_loading_engine_msg2 in en-US aufgefallen. Im Comment werden die Variablen nämlich nummerisch unterschieden - im eigentlichen String dann aber nicht so verwendet?! Stellt sich die Frage, ob wir für die Übersetzung die nummerischen Variablen wirklich verwenden können, denn dann würde sich unser oben genanntes Problem eh erledigen. # LOCALIZATION NOTE (error_loading_engine_msg2): %1$S = brandShortName, %2$S = location error_loading_engine_msg2=%S could not download the search plugin from:\n%S
Comment 12•16 years ago
|
||
(In reply to comment #11) Ups, Vorsicht: mein Kommentar bezog sich ja auf toolkit! Dort in toolkit/search/search.properties ist der gleiche String mit identischer ID!
Comment 13•16 years ago
|
||
I recall the parser issuing an error when using %2$S without %1$S. Generally, you should be able to use the orderings always, though there might be edgecases where the calling code looks like calling into the formatter, but instead is doing some js code for replacing or whatnot.
Assignee | ||
Comment 14•15 years ago
|
||
Alexander, the string moved there in 1.9.1. I just changed it on the branch to see what we are dealing with. Pike, do you know, how to trigger this error message?
Assignee | ||
Updated•15 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•