mozilla-l10n / www-l10n Goto Github PK

Remove " in <a { $top }"> - this is causing some linter errors in the vendor's delivery but somehow translation from the Pontoon is fine.

Please update the string. The string ID can remain the same.

@craigcook

A user reported that the line on https://www.mozilla.org/fr/firefox/new/, "Faites ce que vous avez à faire en ligne.
navigateur Firefox ne vous épie jamais." should be "Faites ce que vous avez à faire en ligne.
Le navigateur Firefox ne vous épie jamais." The "Le" should be added to the beginning of the 2nd sentence in the tag line.

I believe the string ID is firefox-desktop-download-do-what-you-do which is here:

I don't personally speak French, I'm just reporting what was reported to me.

cc @peiying2

There's an unclosed link in the es-ES VPN landing page that's breaking the page layout:

https://www.mozilla.org/es-ES/products/vpn/

https://github.com/mozilla-l10n/www-l10n/blob/master/es-ES/products/vpn/landing.ftl#L24

I'm working on the MOFO fundraising banner for 2021 and I noticed some locales are using incorrect / mismatching currencies.

You can see each corresponding value by clicking "Donate" and viewing the next page.

• https://www-dev.allizom.org/cy/ shows $ instead of £.
• https://www-dev.allizom.org/el/ shows $ instead of €.
• https://www-dev.allizom.org/ja/ shows $ instead of ￥.
• https://www-dev.allizom.org/nn-NO/ shows NOK instead of kr.
• https://www-dev.allizom.org/ru/ shows $ instead of ₽.
• https://www-dev.allizom.org/sv-SE/ shows SEK instead of kr.

Here's the string in question: https://github.com/mozilla/bedrock/blob/master/l10n/en/banners/fundraising.ftl#L13-L16

File name: en/products/vpn/platform-post-download.ftl
String: … then signing into your existing { -brand-name-firefox } account on the new device. …

{ -brand-name-firefox } account should be { -brand-name-firefox-account }

@alexgibson when tou migrate the next batch of files, let's update the file to include Facebook:

your existing { -brand-name-firefox } account on the new device. this string contains a coding error that became obsolete. Let's remove it as soon as possible so communities don't have to translate the string and try to fix it on their own which introduces linter error.

We may have fixed a few of this type recently. Let's try to remove them too.

@craigcook

There are two errors in the update to the .toml file:
1). The newly added file is out of alphabetical order in the list of files.
2). The file name is incorrect, containing two .ftl.

@alexgibson

en/firefox/welcome/13.ftl is not shown in Pontoon. Need to add an entry to the config file pontoon.toml. https://github.com/mozilla-l10n/www-l10n/blob/master/configs/pontoon.toml

• File: en/products/vpn/more/when-to-use-a-vpn.ftl
• Current: https://www-dev.allizom.org/products/vpn/more/when-to-use/
• Expected: https://www-dev.allizom.org/en-US/products/vpn/more/when-to-use-a-vpn/

Spotted by https://github.com/mozmeao/www-site-checker

• https://github.com/mozilla-l10n/www-l10n/blob/master/ia/mozorg/about/this-site.ftl#L35 is talking about Fluent and it should be talking about Protocol. Note that the variable being used will also need updating because fluent isn't available for this string
• https://github.com/mozilla-l10n/www-l10n/blob/master/ia/mozorg/about/this-site.ftl#L20 uses $libro when the variable is called $book

Go to: Settings -> Webhooks -> [Add webhook].

• Payload URL: https://gitlab.com/api/v4/projects/10706092/ref/master/trigger/pipeline?token=TOKEN (I'll send you the token separately)
• Content type: default is fine
• Secret: leave blank
• Which events would you like to trigger this webhook?: Just the push event
• Active: checked

This string 30-day money-back guarantee is used multiple times on this page. For some languages, the translation is different depending on context. Let's break it up into types:

• Standalone string
• One of the bullet items

When a fix is added, let's make sure the string IDs and comments provide good context so it is clear which string is used where.

We need to remove the localized versions because of these PRs: PR 401 and PR 402

The brand name placeholder is incorrectly spelled.

What I see: { -brandname-firefox-browser }

What is expected: { -brand-name-firefox-browser }

When this is fixed, make sure to update the string ID.