Hello Michele,
Thanks for raising the question. This is not a typo. Before adding
Brave, the index file compared six browsers. With the addition of the
Brave page, there are now seven. Notice that the string ID indicates
that this is a "fallback". In fact, there are a few of them in this page
to reflect this change.
This is like tagging in the old format. With Fluent and the 80% rule of
completion, the activation of the new strings will be somewhat different
depending on the logic and there are a few scenarios. I will get back to
this topic and update everyone, as well as the testing doc once we get
some clarity:
https://mozilla-l10n.github.io/localizer-documentation/products/mozilla_org/testing.html#how-to-test-localized-pages-on-the-production-server.
If the pages are kept up to date, with each reiteration, the activation
of the strings will be more straight forward. They may not be all at
once, but most likely string by string once the page passes the 80%
completion. Even if it drops to below 80% due to updates, the page will
remain activated on production. For this update, it is not time
sensitive, so there is not a window to switch from old to new, but
driven by the completion of each community.
Thank you,
Peiying
> _______________________________________________
> dev-l10n-web mailing list
>
dev-l1...@lists.mozilla.org
>
https://lists.mozilla.org/listinfo/dev-l10n-web