Difference between revisions of "User:Kebap/translation infrastructure"
Jump to navigation
Jump to search
(Created page with "History: * https://github.com/Mudlet/Mudlet/issues/856 - Setup a web-based translation service for Mudlet * https://github.com/Mudlet/Mudlet/issues/1664 - Translation infrast...") |
m |
||
| Line 14: | Line 14: | ||
Processes for each: | Processes for each: | ||
| − | + | # Find out a way to tell outdated texts from relevant current texts which need translation. | |
| − | + | # Get texts out of sources (see above). Can this be automated with any tool? Who should be responsible? | |
| − | + | # Get texts in to translation tool. | |
| − | + | # Translating inside tool (ok this is to be expected, but also needs good interface and workflows) | |
| − | + | # Translators report confusing strings back to Mudlet team with information how they need to be adjusted. | |
| − | + | # Mudlet team updates text in source. Either because of reports, or because of natural evolution. | |
| − | + | # Updated texts from source need updates in translation tool. Export and import again, plus diff. | |
| − | + | # Translated texts will be finished. Export them from translation tool. Automation again? | |
| − | + | # Import translated text to source. | |
| − | + | # Display of translations in source. Here we will need some sort of language toggle switch in each source. | |
| Line 33: | Line 33: | ||
* Wordpress internationalisation workflow | * Wordpress internationalisation workflow | ||
** http:// www.cardinalpath.com/multilingual-wordpress-international-seo/ | ** http:// www.cardinalpath.com/multilingual-wordpress-international-seo/ | ||
| − | * integration to Crowdin | + | * integration to [[User:Kebap/Crowdin|Crowdin]] |
** Mediawiki | ** Mediawiki | ||
** Github | ** Github | ||
Revision as of 21:11, 2 June 2018
History:
- https://github.com/Mudlet/Mudlet/issues/856 - Setup a web-based translation service for Mudlet
- https://github.com/Mudlet/Mudlet/issues/1664 - Translation infrastructure of Mudlet web-presences
Main sources of text:
- Mudlet client itself
- Mudlet website
- Mudlet wiki
- "other" spontaneus texts need to be included manually
Processes for each:
- Find out a way to tell outdated texts from relevant current texts which need translation.
- Get texts out of sources (see above). Can this be automated with any tool? Who should be responsible?
- Get texts in to translation tool.
- Translating inside tool (ok this is to be expected, but also needs good interface and workflows)
- Translators report confusing strings back to Mudlet team with information how they need to be adjusted.
- Mudlet team updates text in source. Either because of reports, or because of natural evolution.
- Updated texts from source need updates in translation tool. Export and import again, plus diff.
- Translated texts will be finished. Export them from translation tool. Automation again?
- Import translated text to source.
- Display of translations in source. Here we will need some sort of language toggle switch in each source.
References:
- Another great in-depth look at several alternatives and the process in general in this master study thesis about “Translations in libre software”: https:// larjona.wordpress.com/translations-in-libre-software/
- multilingual plugins for Wordpress: https:// wordpress.org/plugins/search/multilingual
- Polylang: https:// wordpress.org/plugins/polylang/
- Wordpress internationalisation workflow
- http:// www.cardinalpath.com/multilingual-wordpress-international-seo/
- integration to Crowdin
- Mediawiki
- Github