Review of the Docs translation processes #54
Labels
No labels
Contributors' Guidance
Improve written Material
Contributors' Guidance
technical support measures
effort
high
effort
low
effort
medium
good first issue
help wanted
meeting topic
needs changes
needs reporter feedback
needs review
needs vote
priority
high
priority
low
priority
medium
priority
on hold
type/content
type/misc
No milestone
No project
No assignees
5 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
docs/tickets#54
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
As a reminder: We need to coordinate the translation process with the translation group, as soon as the migration to forge is completed. In the meantime, it is on hold.
As far as I am aware, a lot of this work has already started. It could be better documented, however? The best people to ask for information would be @jibecfed, @peartown, or @rffontenelle might be able to clarify in more detail.
Hi there, first step is to read the docs created by peartown and darkano :p
https://docs.fedoraproject.org/en-US/localization/doc_l10n/
Does it helps?
A good place to communicate with our three Localization admins (peartown, rffontenelle & myself) is the #l10n:fedoraproject.org matrix channel
As @jibecfed mentioned in another issue noted, it is "fine to start large translation workflow from a tooling point of view. Everything is up and ...".
So let's start it.
What are the next steps to take? E.g., there are Server docs or CoreOS docs which are perfectly fine.
I'm specifically interested in Server docs, I can select language 'de' at the top, but nothing happens. Same with CoreOS. And – a little bit of teasing – if I read Documentation Translation Workflow the German text supposed to come up, looks strange from a German point of view.
If I look into translated sources repository, many part of the docs are there, including text for other languages.
For some parts, e.g. Docs home page, translation basically works, at least to some extent, and with some violation of the page design.
For some parts the naming is strange, e.g. "master" instead of "main".
I guess, we need a working plan to improve the situation.
@pboy The language list you see in the language switch doesn't necessarily mean that specific docs were translated. The language switch is generated by rebuild-site.py from all existing languages in translated-sources repository.
Fedora Server Docs in German is showing English texts because it was not translated yet. See fedora-docs-l10n-fedora-server translation project in Weblate and the fedora-server l10n repository. Please notice the fedora-server directory doesn't exist for German in translated-sources repository.
The 'master' or 'main' you mention is the version name set in the antora.yml file. If the doc maintainers set
version=master, then that value is used in the l10n file path (e.g.po/master/nav.po), but ifversion=~then it fallbacks tomain.Note: the Documentation Translation Workflow needs to be updated in several aspects. For instance, main is the default since
docs/translations-scripts@dc2e0ac7a0, but this document still mentions 'master'.@jibecfed wrote in #54 (comment):
I noticed the docs only describe how to do this on Pagure. 😕 We have reached the point where Pagure is completely offline now.
https://docs.fedoraproject.org/en-US/localization/doc_l10n/#_repository_creation
Are there are plans to update this documentation so more folks could help set up Fedora Docs repositories for translations?
@jflory7 https://forge.fedoraproject.org/docs/translations-scripts#adding-a-new-repository
That page indeed needs to be updated. I'll try to work on it this weekend.
@rffontenelle Thanks, that is super useful in the meantime! Getting it up onto the docs site would make sure it is easy to discover.
@pbokoc @hricky I am wondering whether the Antora modules -> topics migration could impact how localization gets done? It might not, but it is something we should look at closely when we make these changes, per #66.
@jflory7 wrote in #54 (comment):
Hopefully not - we won't be moving anything between repositories or changing filenames of source files, so on the translation side it should all stay the same.
@pbokoc The challenge I have noticed is that every Antora module gets its own l10n repo. If we squash all modules down to a single module in the larger component, this might break the l10n pipeline. I was looking at this with a recent Localization Team ticket, localization/tickets#81 (comment), with @rffontenelle.