Welcome

https://www.fsf.org/campaigns/priority-projects/internationalization says, " Internationalization is the process of designing software so that it can be adapted to various languages and regions without engineering changes.

Internationalization is a feature ethically tied to the values of free software, and is often a strength of free software. But we can do better: Free software can accept translation contributions from anyone who submits them, whereas proprietary software companies historically only bother with languages it serves their profit and other interests to include. When we internationalize free software, we make it easier for others to adapt and spread it in other languages and regions. "

I think each project goes through a few tasks in this process:

Maintainer writes code and makes translation strings available for translation

Translatable strings can be extracted and stored with, for example, GNU gettext.

• GNU Octave
• irssi
• elinks
• links
• laravel (non-free site) 1 2 3
• freenode

Volunteers translate the translation strings

This happens for example here:

• Palemoon ????
• SuMO (support.mozilla.org) — Mozilla products knowledge base
• xfce
• LibreOffice (Document Foundation) - interface and documentation for LibreOffice. bug reports for interface; wiki translated on the spot
• GNU websites translation team
• transifex.com (non-free; avoid)
• translatewiki.net a translate wiki
• trommons.org, including Rosetta Foundation volunteers as they merged their site into trommons a while ago
• babelzilla Mozilla Add-ons translation
• TranslationProject GNU and non-GNU projects; communicates .po files over email
• https://chapters.gnu.org/pootle/
• add a pootle instance to GNU Savannah so that a separate repository with .po files is automatically synced with approved translations from pootle?
• *GNU Ring uses the non-free transifex site?

Many projects don't have enough volunteers or languages.

Maintainer uploads multilingual documentation to a website

If people read multilingual documentation then they engage into translation more? This again needs a maintainer to extract translation strings and volunteers to translate them; could use a multilingual CMS such as

• Drupal (in PHP),
• hugo,
• ikiwiki (in Perl),
• jekyll (in Ruby; jekyll notes),
• pelican, or
• nicola,
• ...

List of software without multilingual documentation:

• ...

List of software with multilingual documentation:

• ...

Task: Improve translation quality

• Survey translators and maintainers to find out what works well?
• Do a correlation between number of languages and what translation techniques are used?
• Use a freedom respecting ?group translation site? Which ones are 'better'?
• Outreach to get more languages? How?
• Motivation to keep maintaining existing translations? How?

Extra

• словари