Translations

[allo-]

Help us to translate the site.

[Atavic]

So it's in english only for now?

[allo-]

Yes. But there is support for translations, note the _() at
https://github.com/allo-/firefox-profilemaker/blob/master/forms.py#L95

There is currently no support for automatic .po generation for the settings, but it should work to compile them with ./manage.py compilemessages. See https://github.com/allo-/firefox-profilemaker/issues/74 and an (unfinished) example at rmoch@ec7c0fa.

[Atavic]

Can't I just fork and translate the json files in /settings/?

[allo-]

If you use gettext, the site can easily switches from one language to another and there are good programs which allow you to match your translation with changed strings in future versions, so you can update it without search what's changed.

Have a look at the wikipedia page for gettext: https://en.wikipedia.org/wiki/Gettext. The system features things like plural forms, fuzzy matching, single line vs. block translations and much more. And there are a lot of programs to make it easier to deal with the files. I like to use gtranslate, but from the screenshots Poedit looks nice as well.

If you really want to, go on and translate the raw text. This can still be converted to gettext files and I do not want to stop you from helping. If you want to do so, put your translated files in another folder, so I can merge them without overwriting the original files.

[olivertzeng]

If you use gettext, the site can easily switches from one language to another and there are good programs which allow you to match your translation with changed strings in future versions, so you can update it without search what's changed.

Have a look at the wikipedia page for gettext: https://en.wikipedia.org/wiki/Gettext. The system features things like plural forms, fuzzy matching, single line vs. block translations and much more. And there are a lot of programs to make it easier to deal with the files. I like to use gtranslate, but from the screenshots Poedit looks nice as well.

If you really want to, go on and translate the raw text. This can still be converted to gettext files and I do not want to stop you from helping. If you want to do so, put your translated files in another folder, so I can merge them without overwriting the original files.

Is it fixed rn? I can help with zh_TW. But I really do want to ask if this website supports Firefox forks such as Waterfox.

[allo-]

No support for translations yet. If you are interested in tacking this, there are two possible approaches:

• load name/description from second JSON file with the same name (or a field referencing the filename of the setting. This won't support any gettext tooling, but only needs one to load the field from another file.
• Generate fake python files from the JSON files, that can then be translated using gettext tooling. When loading the JSON files use gettext with the string from the JSON file that was translated in the generated python file.

For the webinterface itself Django already has good gettext support.

---

Firefox forks should work with most settings and the other settings are silently ignored.
Forks from earlier versions may not support all enterprise policies (only relevant for the enterprise policy export and not for the prefs.js or profile.zip export) and I am not sure if the method for pre-installing extensions works for all forks.