Continuing the conversation from https://github.com/libremesh/lime-packages/issues/257#issuecomment-365522564 , including @Nikerabbit, part of the TranslateWiki team: @Nikerabbit wrote: text is okay), so you could copy the markdown readme on the wiki and make it translatable using that feature. Practically, that would mean that future changes should be done to the translatable page and exported back to the repository (or doing changes twice, but overwriting the wiki version with a fresh copy from the repository won't work). https://translatewiki.net/wiki/Translating:Lib.reviews/FAQ pages to the repository are not automated yet. Within LibreMesh, I see four types of text to translate (besides software interfaces): - web sites - software README files - instructional booklets - subtitles # WEB SITES The web pages of www.libremesh.org are here: https://github.com/libremesh/lime-web/tree/master/docs . We talked about changing from Jekyll to a website engine that has more elegant multilanguage functionality (such as Nikola http://nikola.readthedocs.io/en/latest/manual/#multilingual-posts), but for now we're still on Jekyll. Our conversation about this is at https://github.com/libremesh/lime-web/issues/22 . There are two language-specific issues open for the website: https://github.com/libremesh/lime-web/issues/35 Italian and https://github.com/libremesh/lime-web/issues/33 Brasilian Portuguese. One group used Zanata to translate a few pages. I'm tempted to move libremesh.org to a platform that allows translation of the site content on the site, so that all translation can happen on-site instead of pasting it into TranslateWiki, translating, and copying the translation back to the website (or back to a file on GitHub). The www.librerouter.org website runs CyclopeCMS, which has [kind of awkward, admin-dependent] multilingual capabilities, however the site will be moved to WordPress, which has various multilingual options. We welcome and recommendations of WordPress multilingual and translation tools. # README FILES For some software, we want to translate the README but not the software, mostly for command line programs. These include: - lime-sdk https://github.com/libremesh/lime-sdk/blob/develop/README.md - LibreNet6 http://docs.altermundi.net/LibreNet6/Setup I imagine this is the same workflow as for text pages: paste into TW, translate, copy to the appropriate place in a file or web page. # INSTRUCTIONAL BOOKLETS The booklets aren't published yet, but we've already translated some of the drafts by using online pads (EtherPad) and offline OmegaT+. The booklet formats and workflow can be changed if necessary. Currently, the translation happens with TXT files, with a PDF of the original (in Spanish) to give visual context (there are images in the booklets). The booklet creators then paste the translated text and publish a PDF in the target language. There are no plans at the moment to publish the booklets as web pages, though this is a possibility, and might be a good idea. # SUBTITLES There are instructional videos that will be narrated in Spanish or English, and then we'll create subtitle files, and then translate the subtitles. In the past I've used SubtitleEditor on my computer, and www.dotsub.com. If we can put the SRT or other format in a GitHub repo and translate them on TranslateWiki, great. ~ Pato