Le 09/10/2019 à 14:25, Rafael Fontenelle a écrit :
Weblate can link the source string location (filename and line) in
the
source code, allowing the translator to click the link and browse the
source file in the exact line. This makes it easier for the translator
to check the context of a string while on the Weblate editor web
interface.
Well, this features exists and will work as expected for "normal projects".
The thing is, the demonstration projects we have are about our
documentation system.
Because of the way tool we use for our documentation works (Antora), we
choose to structure the localization file following the same scheme that
the published website.
We also decided to have translation component per page, making it way
easier to fix errors and coordinate team work.
So, here is an example:
https://translate.stg.fedoraproject.org/projects/fedora-l10nproject/
contains the translation of every subpages of
https://docs.stg.fedoraproject.org/en-US/project/
https://translate.stg.fedoraproject.org/projects/fedora-l10nproject/maste...
is
https://docs.stg.fedoraproject.org/en-US/project/index.html
https://translate.stg.fedoraproject.org/projects/fedora-l10nproject/maste...
is
https://docs.stg.fedoraproject.org/en-US/project/leadership/
etc.
https://translate.stg.fedoraproject.org/projects/fedora-l10nproject/nav/
is the navigation menu
https://translate.stg.fedoraproject.org/projects/fedora-l10nproject/maste...
are some generic metadata used by Antora for all pages.
Please note I created 3 projects, but we'll end-up having 29 translation
projects, only for our documentation.
Hope it help!