Translate the text on those files from source language to target languageīuild the documentation in target language using the translated textsīesides these steps, once we have published our first translated version of our documentation,
In both methods, we need to follow these steps to translate our documentation:Ĭreate translatable files (. In this guide we will focus our efforts around two different methods: manual and using Transifex. There are many different ways to manage documentation in multiple languages by using different tools or services.Īll of them have their pros and cons depending on the context of your project or organization. Once this work is done, you can setup your project under Read the Docs to build each language of your documentation by reading Localization of Documentation. This guide walks through the process needed to manage translations of your documentation. Manage Translations for Sphinx projects ¶ Manually Importing Private Repositories.See the complete list of language codes and country codes to find your exact locale. So, the Brazilian Portuguese file would be called ptBR.mo. pt for Portuguese) followed by the country code (e.g. Hide a Version and Keep its Docs Online The naming convention is based on the language code (e.g.For example, ptBR for Brazilian Portuguese, deAT for Austrian German or id. Build documentation from up to date translation The comment will then appear in the resulting.pot file to see if there were any updates to be added too.
#PORTUGUESE BRAZILIAN AS POEDIT FILE SUGGEST HOW TO#
0 kommentar(er)
