LibreRouter: new project with software and HowTo booklets

Jump to: navigation, search

Please summarize the below thread in the editing box. You may use any wikitext in your summary. When you finish, click "Save page".

You do not have permission to edit this page, for the following reason:

The action you have requested is limited to users in the group: Users.

You can view and copy the source of this page.

Return to Summary:Support/LibreRouter: new project with software and HowTo booklets.

Hi, we're curious about whether TranslateWiki might be a good home for the translation of a project we're working on, the LibreRouter. We want to translate software interfaces, documentation, and also an illustrated booklet about how to use the LibreRouter. There's more info about the project at

The code is in the repositories at, and is in English. All the software is in active development or pre-development. One of the apps in active development that's already giving attention to translation is

The source language for the HowTo booklets is Spanish. The text for those booklets isn't ready to translate yet, though we hope to have first drafts ready no later than mid-October.

Some people from our community would join the translation effort, especially for English, Spanish, Portuguese, and maybe German and Afrikaans.

We've tried the interface for translating software strings on TranslateWiki, and we like it. We're not sure if the format of the HowTo booklets is compatible with TranslateWiki, since those are long paragraphs of text. We tested on Zanata, and it worked with .ODT files.

If we need to use a different file format for the code i18n/l10n or for the booklets, we're open to that.

We're interested in TranslateWiki because of the community of translators already active here, and the long-term continuity of the TranslateWiki platform and community.

Does this look like a good match, LibreRouter with TranslateWiki? What would be necessary or desirable actions from the LibreRouter community in order to move forward? We're available to chat on IRC or via e-mail or here on this thread.

Pato (talk)15:05, 21 September 2017

Hi TranslateWiki team,

I wonder how to get in touch with you so that we can figure out whether LibreRouter can join TranslateWiki. I don't see any email address to write to, and the IRC webchat isn't working at the moment (and I don't usually spend any time on IRC). I will respond here to the items listed on the New Project criteria page, and hopefully this will make it clearer whether LibreRouter can join TranslateWiki.

- Openness: yes, LibreMesh software and documentation use free and open source licenses, such as GPLv3.

- Development: yes, LibreMesh is in active development, using a Git repository for version control. The project has periodic releases of LibreMesh, and will have periodic releases of other software and documentation (which has't yet reached first release). Time to get translations into use is currently unknown, and depends on how often network maintainers update the firmware on their router (perhaps we could automate part of this process to make TIU faster, or have a translation-only auto-update so as not to deal with potential software bugs and version incomatibilities between routers on a network), and how often users update Lime-App on their phones. More discussion could be helpful.

- Integration: It seems very reasonable that TranslateWiki staff could have direct push commit access.

- i18n Support: two key parts of the LibreRouter system support i18n already (LibreMesh GUI and Lime-App), though I do not know if they support the details of i18n mentioned on the TranslateWiki New Project page. I have passed the Localization for Developers link to developers and they're looking at it.

- Communication: I am the current liason, and I am not active in development. I have communication with the developers, and it's feasible that one of the developers may takeover the liason role and/or at least one developer might be active in I am a user and tester of the software and documentation.

- File formats: yes, we use translation files, I don't know if they're in one of TranslateWiki's preferred formats. Here's a translation file for Lime-App , and I'll find one for LibreMesh.

We need to start translating this month, October 2017.

What else do you need to know in order to decide whether LibreRouter can join TranslateWiki?

cheers, Pato

Pato (talk)20:35, 6 October 2017

The JSON format looks okay except we don't include the language code as a key in the file (it's already there in the filename). Would you consider changing that format?

Is the repository in GitHub your main repository?

I would request to add some message documentation to guide the translators (see

Nike (talk)20:45, 6 October 2017

Does taking the language code as a key out of the file just mean removing the line   "es": { As well as the closing bracket } ?

Yes, the repository in GitHub is our main repository.

We will add some message documentation to guide the translators based on the advice at It might take us a week or so to start adding that documentation.

Pato (talk)21:03, 14 October 2017

Yeah if the file looks like following, then we support the format.

  "key": "value",
Nike (talk)14:10, 15 October 2017

Also, what are the howto booklets you mention in the subject? Our primary focus is on software user interfaces. [edit] We don't currently support ODT files. Some kind string extraction to another format would be needed. Are the booklets created so that they can be automatically generated from the translated texts (i.e. no hardcoded positionings with length restrictions)?

Nike (talk)20:46, 6 October 2017

The HowTo booklets are a series of guides about the social, technical, and economic aspects of how to create and maintain a community network, with the LibreRouter as the example hardware and software. The idea is that each booklet will be laid out by hand after translating. This means that an automated workflow (as is used in software) is not our plan for the first three languages, and we would join only for the software interfaces.

However, if anyone can suggest a workflow to create the booklets that aligns with the way functions, we're interested to try it out since that could facilitate the translation of the booklets into many more languages. Perhaps the ODT parser from the Zanata translation management platform could be included in, or perhaps we could use a different format. Or perhaps a bit of the BookType software used to create the books at could be reused.

Pato (talk)21:22, 14 October 2017

I haven't done that before. I am sure there are string extraction plugins for ODT. The problem is that usually booklets have quite tight positioning and size constraints. Doing the layout manually for many dozens of languages (and dealing with possibly frequent updates) doesn't scale. But a flexible or simple ODT file we could probably support if there is a suitable parser-generator we can integrate.

Nike (talk)14:29, 15 October 2017