docs: add french user-manual translations #1876
Conversation
|
The screenshot aren't translated, and I don't know how to best handle them. Should we change the paths pointing to them, or should we create symlinks to the existing files ? I will try changing the paths, hope docusaurus handle well the multiple path computation. |
|
It seems we cannot have a partially translated documentation. Seems like if we only translate the user-manual, some link from the admin-manual to the user-manual will be broken.
I already use a really long relative path to get the untranslated screenshots, which seem a bit dirty. |
jooola
force-pushed
the
docs_fr
branch
3 times, most recently
from
d0c51bc
to
e25e6c1
Compare
|
/website-preview |
|
🚀 Preview deployment succeeded! Website preview: https://libretime.github.io/pr-1876/ |
|
/website-preview |
|
🚀 Preview deployment succeeded! Website preview: https://libretime.github.io/pr-1876/ |
|
Docusaurus does not support partially translated documentation. I feel this is gonna be a nightmare to maintain, we currently duplicate all the documentation once again, and we are starting to have a matrix of languages / versions to maintain which I think should not be handled inside the repository (#1913). I don't know if this complexity comes specially from docusaurus or any multilingual system, but I'll try to experiment with mkdocs/sphinx to see if they have a better way for handling this. Maybe once we remove the version from the matrix, we will be able to have something simpler. |
|
In addition, keeping track of the changes between multiple languages seem also to be a complex topic. We might want to extract the translated documentation to it's own repository, and use a bot to raise issues if we detect changes on the default documentation. |
|
I think this should go in a dedicated repository, with it's own name spaced URL e.g. |
No description provided.