L10n Review PR #225
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,33 @@ | ||
| content-feedback_question = War diese Übersetzung hilfreich? | ||
| content-feedback_reason = Warum war diese Übersetzung nicht hilfreich? | ||
| content-feedback_thanks = Vielen Dank für die Rückmeldung! | ||
|
|
||
| reference_toc_header = In diesem Artikel | ||
|
|
||
| footer_tagline = Dein Bauplan für ein besseres Internet. | ||
| footer_mofo = Besuche die gemeinnützige Muttergesellschaft der <a data-l10n-name="moco">Mozilla Corporation</a>, die <a data-l10n-name="mofo">Mozilla Foundation</a>. | ||
| footer_copyright = Teile dieses Inhalts sind ©1998–2024 von einzelnen mozilla.org-Mitwirkenden. Inhalte sind verfügbar unter <a data-l10n-name="cc">einer Creative-Commons-Lizenz</a>. | ||
|
|
||
| theme_default = Systemstandard | ||
|
|
||
| blog_time_to_read = { $minutes -> | ||
| [one] { $minutes } Minute Lesezeit | ||
| *[other] { $minutes } Minuten Lesezeit | ||
| } | ||
| blog_post_not_found = Blogartikel nicht gefunden. | ||
|
|
||
| blog_previous = Voriger Artikel | ||
| blog_next = Nächster Artikel | ||
|
|
||
| No = Nein | ||
| Submit = Abschicken | ||
| Yes = Ja | ||
|
|
||
| Report = Report | ||
|
|
||
| obs_title = HTTP Observatory | ||
| obs_landing_intro = Das 2016 gestartete HTTP Observatory verbessert die Sicherheit durch Analyse der Einhaltung bewährter Sicherheitspraktiken. Es hat durch 47 Millionen Scans Einblicke in über 6,9 Millionen Websites geliefert. | ||
| obs_assessment = Das von Mozilla entwickelte HTTP Observatory führt eine umfassende Bewertung der HTTP-Header und weiterer zentraler Sicherheitskonfigurationen einer Website durch. | ||
| obs_scanning = Der automatisierte Scan-Prozess liefert Entwicklern und Website-Administratoren detailliertes, handlungsorientiertes Feedback und konzentriert sich darauf, potenzielle Sicherheitslücken zu erkennen und zu beheben. | ||
| obs_security = Das Tool unterstützt Entwickler und Website-Administratoren maßgeblich dabei, ihre Websites in einem sich stetig weiterentwickelnden digitalen Umfeld gegen häufige Sicherheitsbedrohungen abzusichern. | ||
| obs_mdn = Das HTTP Observatory bietet wirksame Sicherheitseinblicke auf Grundlage von Mozillas Expertise und Engagement für ein sichereres Internet sowie basierend auf etablierten Trends und Richtlinien. | ||
| Original file line number | Diff line number | Diff line change | ||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| @@ -0,0 +1,102 @@ | ||||||||||||||||||||||
| article-footer_last-modified = This page was last modified on <time data-l10n-name="date">{ $date }</timestamp> by <a data-l10n-name="contributors">MDN contributors</a>. | ||||||||||||||||||||||
|
||||||||||||||||||||||
| article-footer_last-modified = This page was last modified on <time data-l10n-name="date">{ $date }</timestamp> by <a data-l10n-name="contributors">MDN contributors</a>. | |
| article-footer_last-modified = This page was last modified on <timestamp data-l10n-name="date">{ $date }</timestamp> by <a data-l10n-name="contributors">MDN contributors</a>. |
Tags don't match
Outdated
There was a problem hiding this comment.
This is more stylistic - but can we consistently use dashes - instead of underscores for string IDs?
E.g. article-footer-last-modified
Outdated
There was a problem hiding this comment.
Could you include a comment to describe variables? Something like the below:
| article-footer_source_title = Folder: { $folder } (Opens in a new tab) | |
| # Variables: | |
| # $folder (String) - Link to github folder | |
| article-footer_source_title = Folder: { $folder } (Opens in a new tab) |
Outdated
There was a problem hiding this comment.
What is this variable for? Or is it for formatting?
There was a problem hiding this comment.
Looking into this it seems its just the character *. It's best to either use the character itself here, or if there area reasons for not wanting localizers to be able to adjust it, then perhaps its best to remove it from the string and style on the backend.
Outdated
There was a problem hiding this comment.
Could you include a comment for the variable here and similar date variables below?
| baseline_high_extra = This feature is well established and works across many devices and browser versions. It’s been available across browsers since { $date }. | |
| # Variables: | |
| # $date (String) - a localized date string in format Month YYYY (e.g. December 2024) | |
| baseline_high_extra = This feature is well established and works across many devices and browser versions. It’s been available across browsers since { $date }. |
Outdated
There was a problem hiding this comment.
Nitpick, maybe changing the second This feature to It.
Outdated
There was a problem hiding this comment.
Please also include a comment to provide context for these browser variables? (E.g. are these formatted lists? examples of what they would look like)
Outdated
There was a problem hiding this comment.
What are shown in { $supported } and { $unsupported }? Add a comment will provide context will help.
Outdated
Outdated
There was a problem hiding this comment.
| reference_toc_header = In this article | |
| # Header text followed by a table of contents | |
| reference_toc_header = In this article |
The toc in the string ID might not be easily recognized by localizers so we should include some sort of context.
Outdated
There was a problem hiding this comment.
For links, we typically use this format <a href="{ $moco }">Mozilla Corporation</a> for example.
There was a problem hiding this comment.
I think this depends on the backend, it appears that's how bedrock is doing things for their footer links, but might not be applicable in this case.
Outdated
There was a problem hiding this comment.
Can we make 1998–2024 dynamically updated?
Outdated
There was a problem hiding this comment.
Need a comment on what the variable is for, like the kind of queries.
Outdated
There was a problem hiding this comment.
So this string is about how fast results can be found, not how many results found in X number of articles.
Outdated
There was a problem hiding this comment.
This string won't work as it is, assuming $results also returns a number of matches, you'll encounter grammatical errors even in English - Found 1 results in 1 milliseconds.
The likelihood is higher in a language like Russian which has 3 different plurals depending on the number returned.
Fluent plurals would fix this, but unfortunately it gets too complicated when you have two plural selectors in the same message. To fix this I'd split this into two independent sentences.
search-stats-results = { $results ->
[one] Found { $results } match.
*[other] Found { $results } matches.
}
search-stats-time = { $time ->
[one] Search took { $time } millisecond.
*[other] Search took { $time } milliseconds.
}
Outdated
There was a problem hiding this comment.
I'm guessing this is an existing string taken from somewhere? But reviewing this I think the natural English would be
1-minute read / 10-minute read
(Please feel free to confirm with content team)
In that case this string might be better as:
blog-time-to-read = { $minutes ->
*[other] { $minutes }-minute read
}
We'd still want to keep the plural selector in there to trigger plurals for other languages.
Outdated
There was a problem hiding this comment.
Another style request for string IDs, can we keep everything lowercase?
Also we should namespace with a more descriptive name, e.g. report-page-title
Outdated
There was a problem hiding this comment.
Should HTTP Observatory be localized or treated as a brand term / left unlocalized?
Outdated
There was a problem hiding this comment.
Is it better to change the websites and scan numbers to variables to minimize the needs for updates in the future?
Outdated
There was a problem hiding this comment.
| obs_mdn = The HTTP Observatory provides effective security insights, guided by Mozilla's expertise and commitment to a safer and more secure internet and based on well-established trends and guidelines. | |
| obs_mdn = The HTTP Observatory provides effective security insights, guided by Mozilla’s expertise and commitment to a safer and more secure internet and based on well-established trends and guidelines. |
Outdated
Outdated
There was a problem hiding this comment.
Add a comment for this section, suggesting that these set of strings are related to Compatibility and where the strings appear. Is this from a report generated as the result of a search?
Outdated
There was a problem hiding this comment.
This likely needs a comment to say what "No" is refuting here (e.g. is this refusing some request, or is it short for No compatibility or something else?)
Outdated
There was a problem hiding this comment.
Please add a comment where these strings show up? The context will help understand what these strings refer to, in the search result or the report?
Outdated
There was a problem hiding this comment.
What does vendor mean here? Is this related to the name of vendor? Example what a "prefix" looks like would also help with context.
Outdated
There was a problem hiding this comment.
Are these strings shown in a graph , table generated from a search result? Please add a comment for the section to give some context.
Outdated
There was a problem hiding this comment.
Need examples for vendor and prefix look like in this context.
Outdated
There was a problem hiding this comment.
| sidebar-filter-matches = { $matches -> | |
| [0] No matches | |
| [1] { $matches } match | |
| *[other] { $matches } matches | |
| } | |
| sidebar-filter-matches = { $matches -> | |
| [0] No matches | |
| [one] { $matches } match | |
| *[other] { $matches } matches | |
| } |
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,2 @@ | ||
| blog_toc_title = En este artículo | ||
|
|
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1 @@ | ||
| blog_toc_title = Dans cet article |
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,2 @@ | ||
| blog_toc_title = この記事では | ||
|
|
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1 @@ | ||
| blog_toc_title = 목차 |
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,2 @@ | ||
| blog_toc_title = Neste artigo | ||
|
|
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1 @@ | ||
| blog_toc_title = В этой статье |
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1 @@ | ||
| blog_toc_title = 在本文中 |
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1 @@ | ||
| blog_toc_title = 在本文中 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Noting here that there seem to be string IDs here that don't match anything in en-US source.