12 Aug
2017
12 Aug
'17
11:42 p.m.
On 08/11/2017 07:45 AM, Nicolas Pace wrote:
So based on this information, which key points would
be relevant to
consider to move forwards?
Please share your points of view so we move on to have a definition.
I'm coordinating the translation of the software and documentation of
the LibreRouter project, and right now we're in the phase of looking at
software options for translation management. While we could use a
dedicated translation platform, such as
https://translatewiki.net
or
http://zanata.org/ ,
another option is to create a multilingual platform that serves as:
- the multilingual community wiki,
- the home for multilingual documentation,
- the platform for coordinating translation of software interfaces and
documentation.
One way to do that would be to copy the infrastructure of
www.translatewiki.net. Another way might be an appropriately configured
CMS instance (Drupal, Tiki, Wiki Suite, Cyclope?, etc.).
I have not looked at the GitHub Wiki, but it almost certainly doesn't
have an advanced translation interface (let me know if it does). Using a
mono-lingual platform seems to me like a sub-optimal way forward given
the diversity of languages in the LibreRouter project.
Pro "Hosted by someone else":
- The TranslateWiki platform has users who enjoy translating free/libre
software interfaces, and they're more likely to translate LibreMesh
stuff that's on their server, so using their server might result in more
translations of higher quality in more languages.
- The complexity of maintaining the server is handled by someone else,
so we can focus on what we're already doing.
Pro "Host it ourselves":
- We could have a single platform for various kinds of content in
multiple languages, with an easy way for people to contribute that's
under our control.
~ Pato