Poor German translation of ImportMapResolveInvalidBareSpecifierWarnRelative
Categories
(Mozilla Localizations :: de / German, defect)
Tracking
(Not tracked)
People
(Reporter: jochen.kuehner, Unassigned)
Details
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/140.0.0.0 Safari/537.36
Steps to reproduce:
I downloaded latest nightly: firefox-145.0a1.en-US.mac.dmg
And got to a webpage with an error: https://plnkr.co/edit/d3PCWsV6Vo14HIE3ObBf?p=preview&utm_source=legacy&utm_medium=worker&utm_campaign=next&preview
Actual results:
The error message is in german, but in poor quality, seems to be automaticly translated? see:
Uncaught TypeError: Der Spezifizierer "script2.js" war ein blanker Spezifizierer, wurde aber nicht zu etwas neu zugeordnet. Relative Modulspezifizierer müssen mit "./", "../" oder "/" beginnen. script.js:3:8
Expected results:
The error message should be in english, at least I like it to be.
|
||
Comment 1•2 months ago
|
||
The Bugbug bot thinks this bug should belong to the 'DevTools::General' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
Error messages generated by DOM are always localised; this particular translation has been in place for 9 months:
Previously it was: Der Spezifizierer "%S" war ein blanker Spezifizierer, wurde aber nicht zu etwas neu zugeordnet. Relative Modulspezifizierer müssen mit "./", "../" oder "/" beginnen. - I cannot comment if this is better than the current wording.
Bug 1377737 has a discussion about an option to switch just the DevTools UI to English; but that's different from the ask here.
Rather than closing this issue, moving the bug to put the poor translation on the localisation team's radar.
|
||
Comment 3•2 months ago
|
||
The current translation has been around for over 3 years.
If you want, you can provide a better translation here:
https://pontoon.mozilla.org/de/firefox/dom/chrome/dom/dom.properties/?search=ImportMapResolveInvalidBareSpecifierWarnRelative&search_identifiers=true&search_exclude_source_strings=true&string=246429
The ability to use DevTools in English would not change the behavior here.
|
Reporter | |
Comment 4•2 months ago
|
||
I'd rather like to see a option to switch the error messages to english, instead of the devtools. If you search for an error message in the internet, you get better results if you use the english one instead of the german one.
But why du i stell get german error, although i've downloaded the en-us version of firefox nightly?
|
|
Reporter | |
Comment 5•2 months ago
|
||
And for the translation, the chrome error in english is:
Failed to resolve module specifier "script2.js". Relative references must start with either "/", "./", or "../".
Would be in german:
Fehler beim Auflösen des Moduls "script2.js". Relative Verweise müssen entweder mit "/", "./" oder "../" beginnen.
Maybe the chrome error is also not so good, i would love in english:
Failed to resolve module specifier "script2.js". Relative references must start with either "/", "./", or "../".
If it’s a non-relative reference, you need to define how it should be resolved in an import map.
And in german:
Fehler beim Auflösen des Moduls "script2.js". Relative Verweise müssen entweder mit "/", "./" oder "../" beginnen.
Wenn es sich um einen nicht-relativen Verweis handelt, musst du in einer Import-Map angeben, wie er aufgelöst werden soll.
Description
•