Closed Bug 1502881 Opened 6 years ago Closed 2 years ago

Firefox Desktop 64 German localization

Categories

(Mozilla Localizations :: de / German, enhancement)

enhancement
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: flod, Assigned: aryx)

Details

Attachments

(4 files)

Starting off a new bug, since there's work coming through Pontoon.

This is diff between the current tip and the sign-off used in 63
https://l10n.mozilla.org/source/diff/?from=72612c2ff687&to=1782169db46c&repo=l10n-central%2Fde

I haven't taken an updated sign-off for beta yet, but I'd really like to take one in the coming days.
Attached patch toolkit, v1Splinter Review
https://hg.mozilla.org/l10n-central/de/rev/16c925b98fd8
Assignee: nobody → aryx.bugmail
Status: NEW → ASSIGNED
Attachment #9027417 - Flags: review?(kairo)
Attached patch devtools, v1Splinter Review
https://hg.mozilla.org/l10n-central/de/rev/ae44e80bb284
Strg+/ als Tastenkombination zum Öffnen der Übersicht der Tastenkombinationen - funktioniert nicht mit deutschsprachiger Tastatur, Strg+Y funktioniert nicht (funktioniert aber, wenn man es für den Gehe-zu-Zeile-Befehl nimmt).
Attachment #9027420 - Flags: review?(kairo)
If it helps, this is the diff between what was in the repository, and what Sebastian landed so far
https://l10n.mozilla.org/source/diff/?from=ca62ca58ef39&to=ae44e80bb284&repo=l10n-central%2Fde
For consistency:
Currently we translate "website" as "Website" and "Webseite" should we stay consistent and only use one of both versions?
Currently "Website" is the translation that occures the most.
I know this is a sensitive issue with some people but we cannot help using both expressions, each depending on the context. I also know that wikipedia is not always free of errors and should therefore not be used uncriticly but its description of a website helps to understand why we need to use "Website" and "Webseite" in German translations (https://de.wikipedia.org/wiki/Website) or use a search "unterschied zwischen website und webseite".

In English we also have the difference between website and web page, although it does not sound quite as similar as the German Website and Webseite, where only one letter ("e") makes all the difference. And let me add that even in English both words often enough are used incorrectly.

I am also sure that lots of the users don't know (and also don't care) about the difference and maybe even get confused by the different use of both words. But it was not us who defined the meaning of both expressions and therefore we should use it correctly. Very simply said: a "Webseite" is just one single page, like the one you see on your screen. You won't see the whole "Website" of a company on the screen, because the Website consists of many Webseiten ("many" = depending on the size of the company or enterprise).

I also fully agree that sometimes it is a real pain, especially if the context is not clearly defined and we only find out later that we used the wrong word in a string. Sometimes it even can happen that a string is valid for both, the Website and a Webseite (or more Webseiten"), I've stumbled over those myself. I don't know what others think about it, but I prefer and will stick to the correct use of both words in German translations.
now that's some helpful context right there ^^

nice, thx for sharing it with such an extensive explanation!
I'll look right into it and apply it :)
We actually had a bug on this very Bugzilla system some time ago where we discussed the issue in depth and moved to a consistent handling like Artist described in comment #7. :)
Attachment #9027417 - Flags: review?(kairo) → review+
Comment on attachment 9027418 [details] [diff] [review]
dom, netwerk, security, v1

Review of attachment 9027418 [details] [diff] [review]:
-----------------------------------------------------------------

::: dom/chrome/security/security.properties
@@ +101,5 @@
>  UnknownClearSiteDataValue=Kopfzeile Clear-Site-Data gefunden, aber mit unbekanntem Wert "%S".
> +
> +FeaturePolicyUnsupportedFeatureName=Feature Policy: Unbekannte Funktionalität (Feature) "%S" wird ignoriert.
> +# TODO: would be nice to add a link to the Feature-Policy MDN documentation here. See bug 1449501
> +FeaturePolicyInvalidEmptyAllowValue= Feature Policy: Leere Liste an Werten für Funktionalität (Feature) "%S" wird übersprungen.

Das Leerzeichen zwischen "=" und dem deutschsprchigen String ist inkonsistent.

Zusätzlich: Haben wir absichtlich keine Übersetzung für "Feature Policy"?

::: security/manager/chrome/pipnss/pipnss.properties
@@ +284,5 @@
>  certErrorMismatch=Das Zertifikat gilt nicht für den Namen %S.
>  # LOCALIZATION NOTE (certErrorMismatch1, certErrorMismatchSinglePrefix1, certErrorMismatchMultiple1): %1$S is replaced by the brand name, %2$S is replaced by host name.
>  certErrorMismatch1=Websites bestätigen ihre Identität mittels Sicherheitszertifikaten. %1$S vertraut %2$S nicht, weil das Sicherheitszertifikat nicht für %2$S gilt.
> +# LOCALIZATION NOTE (certErrorMismatch3, certErrorMismatchSinglePrefix3, certErrorMismatchMultiple3): %1$S is replaced by the brand name, %2$S is replaced by host name.
> +certErrorMismatch3=Websites bestätigen ihre Identität mittels Zertifikaten. %1$S vertraut dieser Website nicht, weil das von der Website verwendete Zertifikat nicht für %2$S gilt.

Hmm, warum haben wir etwas inkonsistent in diesen wiederholten Satz einaml "Zertifikate" und einmal "Sicherheitszertifikate"?
Attachment #9027418 - Flags: review?(kairo) → review+
Comment on attachment 9027419 [details] [diff] [review]
browser, v1

Review of attachment 9027419 [details] [diff] [review]:
-----------------------------------------------------------------

::: browser/chrome/browser/browser.dtd
@@ +1006,5 @@
>  <!-- LOCALIZATION NOTE (contentBlocking.fastBlock.blocking.label):
>       This label signals that this type of content blocking is turned
>       ON, so this is a positive thing. It forms the verb in (imaginary) sentence
>       "Firefox is blocking Slow-Loading Trackers"-->
> +<!ENTITY contentBlocking.fastBlock.blocking.label "Blockierend">

Hmm, "Blockierend" klingt für mich, als würden die Tracker blockierend sein, aber aus dem Kommentar klingt es, als würde Firefox sie blockieren, also vielleicht ist hier "Blockieren" besser?

Das gleiche glit für die anderen *.blocking.label in den folgenden Änderungen.

::: browser/chrome/overrides/netError.dtd
@@ +160,5 @@
>  <!ENTITY certerror.introPara2 "&brandShortName; hat ein mögliches Sicherheitsrisiko erkannt und <span class='hostname'/> nicht geladen. Falls Sie die Website besuchen, könnten Angreifer versuchen, Passwörter, E-Mails oder Kreditkartendaten zu stehlen.">
>  
>  <!ENTITY certerror.expiredCert.secondPara "Am wahrscheinlichsten sind Datum- und/oder Uhrzeit auf Ihrem Computer nicht korrekt, was &brandShortName; daran hindert, eine gesicherte Verbindung zu nutzen.">
>  
> +<!ENTITY certerror.sts.introPara "&brandShortName; hat ein mögliches Sicherheitsrisiko erkannt und daher <span class='hostname'/> nicht aufgerufen, denn die Website benötigt eine verschlüsselte Verbindung.">

besser "..., da die Website eine verschlüsselte Verbindung benötigt."?

::: browser/extensions/formautofill/formautofill.properties
@@ +124,5 @@
>  streetAddress = Straße und Hausnummer
>  
>  ## address-level-3 (Sublocality) names
>  # LOCALIZATION NOTE (neighborhood): Used in IR, MX
> +neighborhood = Neighborhood

Vielleicht "Nachbarschaft"? Ein paar weitere könnten auch übersetzt werden. Wenn wir eher bei den englischen bleiben sollten, dann sollte village_township auch niocht übersetzt werden.
Attachment #9027419 - Flags: review?(kairo) → review+
Attachment #9027420 - Flags: review?(kairo) → review+
Status: ASSIGNED → RESOLVED
Closed: 2 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: