Translation update proposed for dom/chrome/security/security.properties:STSCouldNotSaveState

RESOLVED FIXED

Status

RESOLVED FIXED
4 years ago
10 months ago

People

(Reporter: gion-andri, Assigned: flod)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [transvision-feedback])

The string:
Strict-Transport-Security: An error occurred noting the site as a Strict-Transport-Security host.

Is translated as:
Strict-Transport-Security: Ein Fehler ist beim Vermerken dieser Website als Public-Key-Pins-Host aufgetreten

And should be:
Strict-Transport-Security: Ein Fehler ist beim Vermerken dieser Website als Strict-Transport-Security aufgetreten


Feedback via Transvision:
https://transvision.mozfr.org/?sourcelocale=en-US&locale=de&repo=aurora&search_type=entities&recherche=dom/chrome/security/security.properties:STSCouldNotSaveState
(Assignee)

Comment 1

10 months ago
Sorry for the lack of replies. I just fixed the string in Pontoon, since the error is self-explanatory
Assignee: nobody → francesco.lodolo
Status: NEW → RESOLVED
Last Resolved: 10 months ago
Resolution: --- → FIXED

Comment 2

10 months ago
Fun when people who are not in the German L10n community just change stuff without review while we internally review our stuff. Well, maybe time to just leave this part of the community and don't worry any more.
(Assignee)

Comment 3

10 months ago
(In reply to Robert Kaiser from comment #2)
> Fun when people who are not in the German L10n community just change stuff
> without review while we internally review our stuff. Well, maybe time to
> just leave this part of the community and don't worry any more.

Did you see the actual change?
https://hg.mozilla.org/l10n-central/de/rev/86226e3844b6

English: Strict-Transport-Security: An error occurred noting the site as a Strict-Transport-Security host.

Existing Translation: Strict-Transport-Security: Ein Fehler ist beim Vermerken dieser Website als Public-Key-Pins-Host aufgetreten

New translation replaces "Public-Key-Pins-Host", which is not in the original English string, with "Strict-Transport-Security-Host", which might be bad German, but at least it's not factually wrong.

Comment 4

10 months ago
It's not about the change itself, more about a general thing, which probably doesn't belong in the bug
(Assignee)

Comment 5

10 months ago
I prefer to avoid touching localized strings, unless there are silly errors like a misspelled variable name that I can safely fix.

At the same time, it's not OK to ignore a bug report for 3 years, while the rest of the localization moves on. In this specific case, I think it's better to ship an improvable string than one with an evident error.

Also, slightly related: https://blog.mozilla.org/l10n/2018/05/31/the-importance-of-reviewing-suggestions/

Comment 6

10 months ago
(In reply to Francesco Lodolo [:flod] from comment #5)
> I prefer to avoid touching localized strings, unless there are silly errors
> like a misspelled variable name that I can safely fix.
> 
> At the same time, it's not OK to ignore a bug report for 3 years, while the
> rest of the localization moves on. In this specific case, I think it's
> better to ship an improvable string than one with an evident error.

That's all true.

> Also, slightly related:
> https://blog.mozilla.org/l10n/2018/05/31/the-importance-of-reviewing-suggestions/

I'll take a look once I can fit it into my very busy schedule, thanks.
You need to log in before you can comment on or make changes to this bug.