Hi, Patrick/Patricio/Pato here, coordinating the translation of the software and documentation related to the LibreRouter. I write to the list to let folks know what&#39;s going on and open for feedback about the current plan.<br>
<br>
After considering various options of what platform to use for translation management, I think the most appropriate is <a href="http://TranslateWiki.net">TranslateWiki.net</a>, because it means:<br>
<br>
- someone else takes care of the hosting,<br>
<br>
- is costs us no money (though we could donate some if they need it and if our budget allows), <br>
<br>
- we share the platform with other open source software projects,<br>
<br>
- we join a platform that already has an active community of translators in many languages,<br>
<br>
- the software running the platform is stable and has been in production use to translate the MediaWiki interface for some time,<br>
<br>
- and all of that together means that once we get our process with <a href="http://TranslateWiki.net">TranslateWiki.net</a> going well, it could run easily for years and allow the addition of new languages easily.<br>
<br>
Joining <a href="http://TranslateWiki.net">TranslateWiki.net</a> requires giving direct push commit access to at least one <a href="http://TranslateWiki.net">TranslateWiki.net</a> admin, so that new translations get committed quickly and thus new translations make it into software releases as quickly as practical.<br>
<br>
I hope that we can get a relationship with <a href="http://TranslateWiki.net">TranslateWiki.net</a> setup and translation underway before the end of October, so if you have any ideas, questions, objections, please respond in the next few days.<br>
<br>
[A shortcoming of <a href="http://TranslateWiki.net">TranslateWiki.net</a> is that it can&#39;t handle ODT files, which is the current format for the documentation booklets. We&#39;ll either find a way to convert the booklet text into a compatible format, or we&#39;ll use a different tool (perhaps Zanata) that works well with the current creation process of the booklets. More about documentation translation in another email.]<br>
<br>
For those curious about <a href="http://TranslateWiki.net">TranslateWiki.net</a>, see this page<br>
<a href="https://translatewiki.net/wiki/Translating:New_project">https://translatewiki.net/wiki/Translating:New_project</a><br>
<br>
For those who want to understand i18n and l10n from a software development perspective (that&#39;s internationalization and localization), see:<br>
<a href="https://translatewiki.net/wiki/Translating:Localisation_for_developers">https://translatewiki.net/wiki/Translating:Localisation_for_developers</a><br>
*Developers, please read that, at least a little.*<br>
<br>
To see our conversation so far with <a href="http://TranslateWiki.net">TranslateWiki.net</a>:<br>
<a href="https://translatewiki.net/wiki/Support#LibreRouter:_new_project_with_software_and_HowTo_booklets_54035">https://translatewiki.net/wiki/Support#LibreRouter:_new_project_with_software_and_HowTo_booklets_54035</a><br>
<br>
Once a software has an i18n and l10n structure setup, we add a &quot;qqq&quot; language file for the documentation about each string that will be translated. More details about that here:<br>
<a href="https://www.mediawiki.org/wiki/Localisation#Message_documentation">https://www.mediawiki.org/wiki/Localisation#Message_documentation</a><br>
<br>
<br>
SOFTWARE:<br>
<br>
LibreMesh uses Gettext, and is translated into Spanish:<br>
<a href="https://github.com/libremesh/lime-packages/blob/develop/packages/lime-webui/po/es/lime-webui.po">https://github.com/libremesh/lime-packages/blob/develop/packages/lime-webui/po/es/lime-webui.po</a><br>
<br>
LimeApp uses a JSON format, and is translated into Spanish:<br>
<a href="https://github.com/libremesh/lime-app/tree/master/i18n/translations">https://github.com/libremesh/lime-app/tree/master/i18n/translations</a><br>
<br>
Firmware Chef uses Gettext, and is translated into Spanish:<br>
<a href="https://github.com/libremesh/alterchef/tree/master/altermeshfc/altermeshfc/locale">https://github.com/libremesh/alterchef/tree/master/altermeshfc/altermeshfc/locale</a><br>
<br>
I haven&#39;t yet found the locations of the translation files for the following software, or confirmed whether the software even has translation files:<br>
<br>
- LibreMap<br>
<a href="https://github.com/libremap">https://github.com/libremap</a><br>
<br>
- WiFi Calling (app and server)<br>
-- repository unknown<br>
<br>
- LimeBuild / Cooker / SDK<br>
<a href="https://github.com/libremesh/lime-sdk">https://github.com/libremesh/lime-sdk</a><br>
<br>
- LibreNet6<br>
-- repository unknown<br>
<br>
- Pitbull captive portal<br>
<a href="https://github.com/libremesh/pitbull">https://github.com/libremesh/pitbull</a><br>
<br>
- LibreServer (more complex since it&#39;s an entire GNU/Linux distro, though maybe there&#39;s a central admin interface)<br>
-- repository unknown<br>
<br>
Over the long term, we might consider changing the i18n/l10n format of some of the software to a format preferred by <a href="http://TranslateWiki.net">TranslateWiki.net</a>, as described in this note from <a href="http://TranslateWiki.net">TranslateWiki.net</a>:<br>
&quot;Use of key-based file formats is preferred, like Java properties and Ruby-style YAML. Other supported file formats are PHP arrays, PHP variables and Gettext.&quot; For now, making such a change is not priority and probably not within our capacity. Pau pointed out to me that in LibreMesh, there&#39;s a little program that pulls strings out of the code and puts them in the translation files, and that a similar function would be necessary if we changed to a different format. We could ask at <a href="http://TranslateWiki.net">TranslateWiki.net</a> if they know of such programs.<br>
<br>
~ Patrick