Closed Bug 450488 Opened 16 years ago Closed 15 years ago

[de] Mistakes in german localisation /browser

Categories

(Mozilla Localizations :: de / German, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: atopal, Assigned: atopal)

Details

(Keywords: fixed1.9.0.4)

Attachments

(1 file)

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?
Status: NEW → ASSIGNED
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"
Attached patch small fixesSplinter Review
Attachment #339473 - Flags: approval1.9.0.3?
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
Yes, but in German we don't want to "antropologize" the browser.
Summary: Mistakes in german localisation /browser → [de] Mistakes in german localisation /browser
Hardware: PC → All
Attachment #339473 - Flags: approval1.9.0.4? → approval1.9.0.4+
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.
Already fixed on trunk?
Keywords: fixed1.9.0.4
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?
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.
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-
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
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
(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!
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.
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?
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.

Attachment

General

Created:
Updated:
Size: