There are only several of those strings: https://searchfox.org/mozilla-central/rev/7539ad54ddc720a0553efd07ca681b9a409f9887/netwerk/locales/en-US/necko.properties#5-15

but they show up quite a bit in arewefluentyet.com - and the keys like 6 and 12 are hard to debug.

We should migrate it to more meaningful keys and use Fluent.

This is some subset of https://searchfox.org/mozilla-central/search?q=symbol:M_969b4ac57a0ae13a&redirect=false - I don't think we need to migrate all of necko.properties at once, just the error keys, so maybe just one or two of those callsites.

What is the priority for this work? Should the necko team do this or the fluent team?

Hi Dragana, I'd mark it as P4 - it's a tech debt reduction (low) but as part of the major platform Key Result ("Unify Localization").

The work should be done by the necko team as part of tech debt reduction cycle.

Thank you.

Jens, can you prioritize this with our other work?

Hi Manuel, can you take this?

Yes, I'll look into this.

My currently gathered information on this bug:

• The status code is directly mapped to the .properties translation using the FormatStatusMessage function: /uriloader/base/nsDocLoader.cpp#1230 -> this is where the change to .fluent for this bug report happens (and is still TODO for me)

  • EDIT(2022-01-11 from asking in matrix room #l10n-dev:mozilla.org): Other examples of using Fluent in C++: https://searchfox.org/mozilla-central/search?q=Localization%3A%3ACreate&path=.cpp&case=true&regexp=false

• FormatStatusMessage is implemented in /intl/strres/nsStringBundle.cpp#945-995

• Only other usage of FormatStatusMessage I can see: /dom/xslt/xslt/txMozillaXSLTProcessor.cpp#1033, so I guess this function could get deprecated and removed soon

• migration of the strings is is rather painless because of https://github.com/mozilla/properties-to-ftl

From a review of the current arewefluentyet.com M2 data, it looks like the CookieLaxForced2 string from necko.properties is also formatted during startup. Should that get its own bug, or will it get migrated along with the numerical messages here?

Comment on attachment 9260146 [details]
WIP: Bug 1733498 - Migrate necko errors l10n strings from properties to Fluent

Revision D136612 was moved to bug 1771867. Setting attachment 9260146 [details] to obsolete.

Manuel, is the patch that was at https://phabricator.services.mozilla.com/D136612?id=532851 before it got renamed & reformatted to something completely different something that might still eventually land?

Oh, thats where the duplicate patch came from ^^. I'll look into restoring and completing the patch.