Was checking to see which locales were translated and I noticed that the Frisian translation only has 47 strings, according to https://localize.mozilla.org/projects/accounts

If I go to https://localize.mozilla.org/fy/accounts/LC_MESSAGES/ it seems to have a "0" for client.po.
Not sure exactly what's happening. If I download the client.po and check it locally, it seems to have content, plus it looks like there are translated strings in https://github.com/mozilla/fxa-content-server-l10n/blob/master/locale/fy/LC_MESSAGES/client.po.

I'm probably misunderstanding something, but thought I'd just confirm what I'm seeing.

Thanks,

We're opening this issue because your project has used Travis CI within the last 6 months. If you have already migrated off it, you can close and ignore this issue.

Travis CI is ending free builds on public repositories. travis-ci.com stopped providingthem in early November, and travis-ci.org will stop after December 31, 2020. To avoid disruptions to your workflows, you must migrate to another CI service.

For production use cases, we recommend switching to CircleCI. This service is already widely used within Mozilla. There is a guide to migrating from Travis CI to CircleCI available here.

For non production use cases, we recommend either CircleCI or Github Actions. There is a guide to migrating from Travis CI to Github Actions available here. Github Actions usage within Mozilla is new, and you will have to work with our github administrators to enable specific actions following this process.

If you have any questions, reach out in #github-admin:mozilla.org on matrix.

File: main.ftl
Problem: Paypal should be treated like a brand name, a placeable, and should be spelled correctly - capital Ps.

## payment legal blurb
payment-legal-copy-stripe-paypal = { -brand-name-mozilla } uses Stripe and Paypal for secure payment processing.
payment-legal-link-stripe-paypal = View the Stripe privacy policy and Paypal privacy policy.

After the release of the settings.ftl, let's standardize the treatment of these brand names.

@chenba

Per @vladikoff's https://github.com/mozilla/fxa-auth-mailer/issues/67#issuecomment-125216940

if the "full" templates live in the l10n repo then we should probably move those XSS parse tasks out of the content server and put them into the l10n repo

Please see mozilla/fxa-auth-server#1019 and https://travis-ci.org/mozilla/fxa-auth-server/jobs/75789764.

I was trying to update to get hi translations for email messages, but it fails because OperationalError: ENOENT, lstat '/Users/jrgm/tmp33/fxa-auth-server/node_modules/fxa-auth-mailer/node_modules/fxa-content-server-l10n/locale/hi'

I can "fix" this by manually copying fxa-auth-server/node_modules/fxa-auth-mailer/node_modules/fxa-content-server-l10n/locale/hi-IN to fxa-auth-server/node_modules/fxa-auth-mailer/node_modules/fxa-content-server-l10n/locale/hi-IN, and editing fxa-auth-server/node_modules/fxa-auth-mailer/node_modules/fxa-content-server-l10n/locale/hi/LC_MESSAGES/server.po to set Language: to hi. Um, obviously?

There are 3 wildcard domains, in fxa-content-server-l10n:

1. sr/sr_Latn where sr_Latn is, I think, a mechanical translation of Cyrillic to Latin alphabet.
2. sv/sv_SE where they seem to be independent locales.
3. hi-IN where there is no corresponding hi.

Can we figure out a way to treat these consistently?

See this comment in mozilla/fxa-auth-mailer#46 (comment)

In c26368b, the Language: header was changed from pt_BR to pt-BR, which is unlike all the other country-specific locales in this repository. Was that a correct change? Can they be used interchangeably?

(Of course, crashing on this change is a bug in the fxa-auth-mailer, for any inputs).

Sorry, there was a problem refreshing the list of connected services.
There was a problem replacing your recovery codes.
There was a problem uploading your profile picture
There was a problem deleting your avatar
There was a problem updating your display name.
There was a problem creating this email.
There was a problem sending the verification code.
There was a problem retrieving your code.
There was a problem verifying your recovery code.
Sorry, there was a problem refreshing the recovery key.
Sorry, there was a problem verifying your session
Sorry, there was a problem refreshing that email.
Sorry, there was a problem re-sending the verification code.
Sorry, there was a problem changing your primary email.
Sorry, there was a problem deleting this email.
Sorry, there was a problem verifying your session.
Sorry, there was a problem refreshing two-step authentication.
Sorry, there was a problem verifying your session

Some of these have ending periods, some don't.

Per mozilla/fxa-content-server#2244

We removed a weird ligature in mozilla/fxa-content-server's app/scripts/templates/change_password.mustache template (from finished to finished).

We still have the ligatures in the keys for all these locales in this repo (see fr's client.po file). Not sure if we need to search/replace or copy/paste and add new translations for the ligature and non-ligature versions, or if these strings will just stop displaying translated values once we push out the new fxa-content-server code.

I've had a few people ask me for the link before, but not sure if it is worth adding the https://localize.mozilla.org/projects/accounts link to README.md.

URL: https://accounts.stage.mozaws.net/support
Locale: zh-TW
Screenshot:

The strings missed for translation already exists in https://github.com/mozilla/fxa-content-server-l10n/blob/master/locale/zh_TW/LC_MESSAGES/client.po#L418 . Maybe need an update for string id reference?

File: firefox-accounts/settings.ftl

Problem:

• cs-disconnect-lost-advice-content = Since your device was lost or stolen, to keep your information safe, you should change your { -product-firefox-accounts } password in your account settings. You should also look for information from your device manufacturer about erasing your data remotely.

• delete-account-confirm-title = You’ve connected your { -product-firefox-accounts } to { -brand-mozilla } products that keep you secure and productive on the web:

Should { -product-firefox-accounts } be { -product-firefox-account } (singular)?

When submit the fixes, the string IDs need to be different. We can add "rev" or "2" at the end of the current IDs to differentiate.

Some new strings ("%d days", %d minutes" etc.) need plural string handling with ngettext. Otherwise they can't be translated properly in many languages.

https://wiki.gnome.org/TranslationProject/DevGuidelines/Plurals

@splewako

File: settings.ftl
Problem: The string None is used in settings for both Primary email and Secondary email. In some languages, these two have two separate genders associated with them, thus None will be translated differently.

row-defaults-status = None

Suggestion: Add another string for None, one for each of the emails, with detailed comments/or string ID name so localizers know where the word is used.

Fixes include new IDs.

@chenba

All this stings in this link need to update with some Details because We in Arabic language we need to know number of times of thing like:

• "days ago" string should be "%S days ago"
• "hours ago" string should be "%S hours ago"

so we can translate it by adding number of days in middle "منذ %S يومًا" but without we can't translate them.

*this way already use in other projects, check this strings in transvision

I’m almost positive a ’s’ is missing here https://github.com/mozilla/fxa-content-server-l10n/blob/master/locale/en_US/LC_MESSAGES/client.po#L448
@shane-tomlinson , do you confirm?

This link should not be in the po file:
https://github.com/mozilla/fxa-content-server-l10n/blob/master/locale/zh_CN/LC_MESSAGES/client.po#L116

@mathjazz We are going to be removing the link from this repo, do we also need to update this somewhere else?

Per mozilla/fxa-content-server#1067 (comment)

Found in 647310d16b700efacd8ba0adce7c5f475db8e194 on https://latest.dev.lcip.org/ver.json.

{
  "version": "0.13.0",
  "commit": "647310d16b700efacd8ba0adce7c5f475db8e194",
  "l10n": "885344b3b4"
}

Looks like the following locales are still showing duplicated email addresses:

$ grep -ir "You are signed in as" locale -A 1 | grep "%(email)s"

1. locale/ca/LC_MESSAGES/client.po-msgstr "Heu iniciat la sessió com: %(email)s"
   
2. locale/cy/LC_MESSAGES/client.po-msgstr "Rydych wedi mewngofnodi fel: %(email)s"
3. locale/he/LC_MESSAGES/client.po-msgstr "מחובר כעת בתור %(email)s"
   
4. locale/ko/LC_MESSAGES/client.po-msgstr "로그인 중: %(email)s"
5. locale/lt/LC_MESSAGES/client.po-msgstr "Jūs prisijungę kaip: %(email)s"
6. locale/nb_NO/LC_MESSAGES/client.po-msgstr "Du er logget inn som: %(email)s"
7. locale/pl/LC_MESSAGES/client.po-msgstr "Jesteś zalogowany jako: %(email)s"

As noted in https://github.com/mozilla/fxa-auth-mailer/issues/54#issuecomment-117355682, we should send notices to dev-l10n and dev-l10n-web whenever we add news strings to be translated. I don't think we should entirely automate this, but it'd be nice if the extract_strings.sh script could spit out a draft email highlighting the changes and remdind the runner of where to send it.

We are going to merge the two locales into one to fully utilize the community resources. The plan is:

Dev:

• FxA creates an bn folder at repo
• Move bn-BD repo content to bn repo and confirm it's all there (bn-BD has more content in comparison)
• Remove bn-BD, bn-IN repos

Pontoon (l10n);

• Pontoon dev migrates the data to bn (this includes contributors histories)
• L10n PM confirms the update and closes this issue.

@shane-tomlinson let me know if you are the person to speak about how to carry out this task.

For the reasons described in #79 (comment)

Firefox OS 2.2 will be supporting Arabic strings. In conjunction with this push, FxA needs to localize into Arabic. If at all possible, we'd love to do this by the end of March so we can test UI layout in Arabic.

@mathjazz, is Arabic localization reasonable in this time frame? Thanks!

As of January 1 2019, Mozilla requires that all GitHub projects include this CODE_OF_CONDUCT.md file in the project root. The file has two parts:

1. Required Text - All text under the headings Community Participation Guidelines and How to Report, are required, and should not be altered.
2. Optional Text - The Project Specific Etiquette heading provides a space to speak more specifically about ways people can work effectively and inclusively together. Some examples of those can be found on the Firefox Debugger project, and Common Voice. (The optional part is commented out in the raw template file, and will not be visible until you modify and uncomment that part.)

If you have any questions about this file, or Code of Conduct policies and procedures, please reach out to [email protected].

(Message COC001)

SyntaxError: app/scripts/lib/experiments/password-strength.js: Unexpected token (12:16)
10 | */
11 | class PasswordStrengthExperiment extends BaseExperiment {
12 | notifications = {
| ^
13 | 'account.created': 'onAccountCreated',
14 | 'password.error': 'onPasswordError',
15 | };
Warning: Command failed: node_modules/.bin/babel --plugins=babel-plugin-syntax-dynamic-import,dynamic-import-webpack --presets es2015 app/scripts --out-dir .es5
SyntaxError: app/scripts/lib/experiments/password-strength.js: Unexpected token (12:16)
10 | */
11 | class PasswordStrengthExperiment extends BaseExperiment {
12 | notifications = {
| ^
13 | 'account.created': 'onAccountCreated',
14 | 'password.error': 'onPasswordError',
15 | };
Use --force to continue.

Aborted due to warnings.

When accessing FxA settings, my locale is en-CA and it appears to contain a bunch of those paragraph/pilcrow characters. They are visible in production.

I can see them in the file: https://github.com/mozilla/fxa-content-server-l10n/blob/master/locale/en_CA/settings.ftl#L122

If we are going to copy pt_PT to pt, it does not make sense to keep pt in this repo and have a potential contributor start unwittingly doing the translations for it.

Ref #81, mozilla/fxa-content-server#3224.

@mathjazz, @rfk

I might be wrong, but you're taking original translations starting with uppercase, and reusing them after making them lowercase via JS.
https://github.com/mozilla/fxa/blob/07cefc18148d0b17f5240120a84fe151a5032088/packages/fxa-content-server/app/scripts/models/support-form.js#L15

That is incredibly fragile (I'd go as far as to say it's broken):

• JS might not be able to manage the correct transformation for locales.
• You don't know what capitalization a language should use in the middle of a sentence.
• In the middle of a sentence it might need a different case.

Originally posted by @flodolo in #420

There is quite a bit of inconsistency in using straight and curly quotes throughout the main.ftl and settings.ftl files. Let's clean them up so they are all curly in localizable content.

See https://travis-ci.org/mozilla/fxa-content-server-l10n/jobs/173707141

Errors in the locale/de/auth.ftl are causing the following issues:

• 11783 - App store badge missing from postVerify template when browser's language is set to German
• 11784 - Special char displayed near text in postAddAccountRecovery template HTML when German is selected
• 11785 - Variables not replaced with the correct text in subscriptionDowngrade and subscriptionUpgrade templates (HTML and plaintext) - German

Hi. It seems some strings are not pushed into production, even if they were translated 15 days ago (and made few changes today on Pontoon).
Do we need a manual intervention for this or do we need to wait more for an automatic update?

grunt l10n-lint --verbose
....
Reading locale/templates/LC_MESSAGES/client.pot...OK
Reading locale/templates/LC_MESSAGES/messages.pot...OK
Warning: Cannot convert undefined or null to object Use --force to continue.

This occurs using node 4. Also fails on travis: https://travis-ci.org/mozilla/fxa-content-server-l10n/jobs/172871222

IIUC, we're currently in a situation where we can't extract strings for the upcoming train until the previous train has shipped to production. If we do so, there's a risk that strings required by the previous train will get removed or overwritten.

Let's change the process the ensure forward-compatibility with previous trains. The simplest option is probably just to keep all old strings around forever, at least to start with. We can see how much of a problem that might cause in practice and implement e.g. some sort of pruning scheme at a later time.

Check out https://travis-ci.org/mozilla/fxa-content-server-l10n/builds/173707139, we are still testing against node 0.10.x

Currently, string extraction is a manual process as outlines in #35. This is prone to user error and could be scripted to a large extent. A simple grunt or bash script to extract the strings from both the content server and auth mailer would be useful.

Ref #35

https://github.com/mozilla/fxa-content-server-l10n/blob/master/locale/sr_Latn/LC_MESSAGES/server.po#L9 is anomalous in that the local is sr_Latn, but the Language: is sr. That is not consistent with other locales like zh_CN, zh_TW, pt_BR, nb_NO.

@rfk Our localizer @jordis reported that the dev site has not been up to date to reflect what's translated in Pontoon. https://pontoon.mozilla.org/ca/firefox-accounts/. This is what we have on Pontoon for the FxA project: https://pontoon.mozilla.org/projects/firefox-accounts/info/. Has the info changed or do we have a sync issue?

This string should have a translation of "to continue to %(serviceName)s", made specefically for en_US in Verbatim, but it shows up empty in the po file: https://github.com/mozilla/fxa-content-server-l10n/blob/master/locale/en_US/LC_MESSAGES/client.po#L619

Ref: https://circleci.com/gh/mozilla/fxa-content-server-l10n/3668

The production branch on this repository is not protected against force pushes. This setting is recommended as part of Mozilla's Guidelines for a Sensitive Repository.

Anyone with admin permissions for this repository can correct the setting using this URL.

If you have any questions, or believe this issue was opened in error, please contact us and mention SOGH0001 and this repository.

Thank you for your prompt attention to this issue.
--Firefox Security Operations team

@shane-tomlinson The issue was brought up in issue #320. Though the issue resolved some problems, however, it is not the issue that localizer @jordis brought up.

In ./locale/zh_CN/LC_MESSAGES/client.po:661-671 there may be some invalid translations:

#: app/scripts/templates/force_auth.mustache:9
#: app/scripts/templates/sign_in.mustache:25
#: app/scripts/templates/sign_up.mustache:13

msgid ""
"By proceeding, you agree to the <a id=\"fxa-tos\" href=\"/legal/terms"
"\">Terms of Service</a> and <a id=\"fxa-pp\" href=\"/legal/privacy\">Privacy "
"Notice</a> of Firefox cloud services."

msgstr ""
"继续提交即代表您同意 %(serviceName)s (%(serviceUri)s) 的 <a id=\"service-tos"
"\" href=\"%(termsUri)s\">服务条款</a>和<a id=\"service-pp\" href="
"\"%(privacyUri)s\">隐私声明</a>。"

It looks like the id attributes got switched from fxa-tos to service-tos and fxa-pp to service-pp.
Similarly, it looks like the URLs may have been changed slightly:

There are also %(serviceName)s and %(serviceUri)s strings in the zh_CN translation which I don't see in en_US.

This script will do all the copying and should run right before prod deploy to get the most translations.
This is a bit of opposite to the "extract_strings", that one runs right after prod is built.

• Automatically copy/symlink "pt-PT" to "pt" #81
• We might need to copy hi-IN to hi
• sv_SE => sv
• Remove all existing copy task in content-server https://github.com/mozilla/fxa-content-server/blob/master/grunttasks/copy.js#L86 and copy them as part of this script

(Sorry, I'm not sure if this is the correct way of reporting this. Let me know if not, and I'll file elsewhere.)

https://github.com/mozilla/fxa-content-server-l10n/blob/master/locale/de/LC_MESSAGES/server.po#L355

The '$' in ... %(invoiceTotal)s $ ... is not necessary since invoiceTotal itself is localized with a currency symbol.

(I'm aware of comments for .pot files. Unfortunately, at the moment there's no simple way to add them for the email templates in fxa-auth-server, from where the emails are sent.)

@shane-tomlinson Here's a GIF of me extracting strings from fxa-content-server and merging the new templates in this repo.

The last step (not recorded) is opening a PR here and waiting for mathjazz's okay to merge.

As described in #44 (comment)

@shane-tomlinson Our Belarusian localizer reported that his work has not shown up on production despite completing it more than a month ago: https://accounts.firefox.com/. When he switches to uk (Ukrainian) as the preferred language, it works. However when he switches to be as the preferred language, the localized content doesn't show up.

Currently strings marked as "fuzzy" are used on the live web pages. In case a translation is out of date, it makes invalid translations to show up instead of English. For example, right now it says "Konto zostało zweryfikowane" ("Verified account") instead of "Account picture" on Polish pages. It's very confusing to users. "Fuzzy" strings in the PO file format are not supposed to be used: https://www.gnu.org/software/gettext/manual/html_node/Fuzzy-Entries.html#Fuzzy-Entries.

A few errors have been identified from PR #479:
1). main.ftl: Should be occurred inAn unexpected error has *occured* while processing your payment, please try again

2). [main.ftl]: add Stripe as a brand name on the top of the file so these strings can be tagged correctly like other third party brands: https://github.com/mozilla/fxa/blob/0ab97ffd95721127890d27167a6404a60d4af2ab/packages/fxa-payments-server/public/locales/en-US/main.ftl#L89-L97

3). Ellipsis vs 3 periods: there are a few strings in the PR, but periods are used in place for Ellipsis.
a). Confirming subscription...
b). Error confirming subscription...
c). Please wait while we process your payment...
d). Updating billing information...

NOTE:

• Numbers 1 + 2 require new string IDs.
• Number 3 can keep the same ID. We hope the communities use ellipsis when translating the strings. These hopefully only impact en-CA and en-GB locales, but hopefully they update these when leveraging them.

We had a little snafu in #9, corrected in #10.