e3fee2cf46
Prior to this commit, the Odoo documentation was mainly split between
two repositories: odoo/odoo/doc and odoo/documentation-user. Some bits
of documentation were also hosted elsewhere (e.g., wiki, upgrade, ...).
This was causing several problems among which:
- The theme, config, Makefile, and similar technical resources had to
be duplicated. This resulted in inconsistent layout, features, and
build environments from one documentation to another.
- Some pages did not fit either documentation as they were relevant
for both users and developers. Some were relevant to neither of the
two (e.g., DB management).
- Cross-doc references had to be absolute links and they broke often.
- Merging large image files in the developer documentation would bloat
the odoo/odoo repository. Some contributions had to be lightened to
avoid merging too many images (e.g., Odoo development tutorials).
- Long-time contributors to the user documentation were chilly about
going through the merging process of the developer documentation
because of the runbot, mergebot, `odoo-dev` repository, etc.
- Some contributors would look for the developer documentation in the
`odoo/documentation-user` repository.
- Community issues about the user documentation were submitted on the
`odoo/odoo` repository and vice-versa.
Merging all documentations in one repository will allow us to have one
place, one theme, one work process, and one set of tools (build
environment, ...) for all of the Odoo docs.
As this is a good opportunity to revamp the layout of the documentation,
a brand new theme replaces the old one. It features a new way to
navigate the documentation, centered on the idea of always letting the
reader know what is the context (enclosing section, child pages, page
structure ...) of the page they are reading. The previous theme would
quickly confuse readers as they navigated the documentation and followed
cross-application links.
The chance is also taken to get rid of all the technical dangling parts,
performance issues, and left-overs. Except for some page-specific JS
scripts, the Odoo theme Sphinx extension is re-written from scratch
based on the latest Sphinx release to benefit from the improvements and
ease future contributions.
task-2351938
task-2352371
task-2205684
task-2352544
Closes #945
65 lines
2.2 KiB
ReStructuredText
65 lines
2.2 KiB
ReStructuredText
===============================
|
|
How to translate my website
|
|
===============================
|
|
|
|
Overview
|
|
========
|
|
|
|
In addition to creating great modern websites, Odoo gives you the
|
|
possibility to translate it in different languages.
|
|
|
|
Process
|
|
=======
|
|
|
|
Once your website is created, you have the opportunity to translate it
|
|
in as many different languages as you want.
|
|
|
|
There are two ways to translate your website, you can do it manually or
|
|
automatically with the Gengo App. If you want to do it automatically, go
|
|
to the **App** module and Install **Automated translations through Gengo
|
|
Api** and **Website Gengo Translator**. If you want to do it manually,
|
|
don't install anything, and follow the next step.
|
|
|
|
Now go to your website. On the bottom right corner of the page, click on
|
|
**Add a language**.
|
|
|
|
.. image:: media/translate_website01.png
|
|
:align: center
|
|
|
|
Choose the language in which you want to translate your website and then
|
|
click on **Load.**
|
|
|
|
.. image:: media/translate_website02.png
|
|
:align: center
|
|
|
|
You will see that Now, next to English there is also French, which means
|
|
that the page for the translation has been created. You can also see
|
|
that some of the text has been translated automatically.
|
|
|
|
.. image:: media/translate_website03.png
|
|
:align: center
|
|
|
|
To translate the content of the website, click on **Translate** (here
|
|
**Traduire** since we want to translate the website in French).
|
|
|
|
There, if you have installed the Gengo Translator, You will see that
|
|
next to the **Translate** button you also have a button **Translate
|
|
automatically**. Once you click on that button, you will be asked some
|
|
information on your account. If you don't have an account yet, go to
|
|
`*https://gengo.com/auth/form/login/* <https://gengo.com/auth/form/login/>`__
|
|
in order to create one. You need to ask for a public key and a private
|
|
key.
|
|
|
|
The content you wish to translate will then be translated automatically.
|
|
|
|
.. image:: media/translate_website04.png
|
|
:align: center
|
|
|
|
Now you can see that most of the content is highlighted in yellow or
|
|
in green. The yellow represents the content that you have to translate by
|
|
yourself. The green represents the content that has already been translated
|
|
automatically.
|
|
|
|
.. image:: media/translate_website05.png
|
|
:align: center
|