-
Notifications
You must be signed in to change notification settings - Fork 35
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WE transition: I18n: convert *.properties
to message.json
files.
#876
Comments
Looks like they've implemented it. (See here, note the highlighted lines: https://dxr.mozilla.org/mozilla-central/rev/a461fe03fdb07218b7f50e92c59dde64b8f8a5b0/toolkit/components/extensions/test/xpcshell/test_ext_i18n.js#31,67,123,129-132) |
I've created a branch with a first commit containing the symlink: |
Done. Thank you @beriain :) See myrdd@b97890e and #877 |
Task:
convert all
*.properties
locale files (src/locale/*/requestpolicy.properties
) to the WEmessage.json
files.Docs:
Details:
src/conditional/webextension/_locales/*/message.json
src/conditional/legacy/content/_locales
with targetsrc/conditional/webextension/_locales
(relative target!).properties
files contain many unlocalized strings. They are all duplicated in the non-en-US
locale files. (For example, search for the stringLearn more about rules.
in all properties files.) All those duplicated messages can be removed, except in theen-US
locale.*.dtd
files as they are! They are used only for the Request Log, which will not be ported for now, see WE transition: Request Log #872.To be considered
The.properties
files contain many unlocalized strings, all being duplicated in each locale. I'm not sure if Mozilla implemented message "fallback" (see https://www.chromium.org/developers/design-documents/extensions/how-the-extension-system-works/i18n#TOC-Locale-fallback).The text was updated successfully, but these errors were encountered: