Learn more about these different git repos.
Other Git URLs
hi, what is the status of F25 content? Where/when can we translate it?
thanks for your help
Is there a specific document that you are looking for?
The current plan, as I understand it, is to have the content transformed from DocBook to AsciiDoc by F25. It sounds like we should start a conversation with translation about this to ensure it won't break their processes or come as a shock.
@jibecfed if we did a sample transformation for you to experiment on, which guide would be the best to start with?
@immanetize is this still the goal?
hi,
to answer @pmkovar: we use Zanata's "docs" group to know what is to translate for the documentation group: https://fedora.zanata.org/version-group/view/docs/languages/fr in this group, we can't find any documentation related to F25, with exception of Release notes.
In addition, when we go to https://docs.fedoraproject.org, we notice an F25 group with a subgroup "Untranslated", containing:
I would assume to find a F25 branch in Zanata for those groups.
In consequence, we do not know what is to be translated. To correct this, write an email to me or localization mailing list writting what "zanata projects" and "branches" we should set in this group to translate the right documentations. Zanata admin will clean the group content.
To answer @bex, I would be glad to be part of this discussion, I tried my best to answer and talk with docs group the whole year 2016.
In terms of docs, the most important and translated one is Release notes. It also is a not too big/technical to work with. I happy to say I'm available to experiment and would suggest to start by this guide. Would you like to have another language team for this? Should I write to L10N mailing list or would like to do it?
To answer @bex, I would be glad to be part of this discussion, I tried my best to answer and talk with docs group the whole year 2016. In terms of docs, the most important and translated one is Release notes. It also is a not too big/technical to work with. I happy to say I'm available to experiment and would suggest to start by this guide.
Ok, it sounds like Release Notes is a good one to start with.
Would you like to have another language team for this? Should I write to L10N mailing list or would like to do it?
Pending @immanetize's feedback, lets work on a joint email to the list. I'd like to see several languages take a look at the content as I understand that each language has slightly different processes and procedures.
I personally think it would be a good idea to have translations for the last edition of these books in their current format. We hope that the translations would be reusable in the new format, but we would still publish the material and it may also be useful for folks like the CentOS docs team.
That said, we don't have a proof of concept to show how compatible the docbook-sourced POs will be with AsciiDoc sources yet. If they don't line up nicely, translators may feel that their time would have been better spent waiting until we finish our conversion. They may appreciate the value and be happy to translate both. I think this is something the translators need to decide.
thanks for your answer @immanetize I would like to tell people to do so, but it's impossible until you do the minimum administrative tasks.
So, the request I would like to do is to ask Zanata admins to list Fedora 25 branch of those books in Zanata's docs group.
Here are the concerned books:
in consequences, here is your administrative todo list:
by the way, you said something about "show how compatible the docbook-sourced POs will be with AsciiDoc sources yet". You may build your system without taking care of this. Zanata is not the best tool ever, I often argue about the lack of community management tool, but it has a great translation memory. It makes really good suggestions when strings are close or the same. With the appropriate keyboards shortcut, we, translators, may do the work manually. If you're lucky, Zanata development team may have some automatism to help you. This is to be tested, but I'm confident.
thanks for your answer @immanetize I would like to tell people to do so, but it's impossible until you do the minimum administrative tasks. So, the request I would like to do is to ask Zanata admins to list Fedora 25 branch of those books in Zanata's docs group. Here are the concerned books: Installation Guide Networking Guide Release Notes SELinux Users and Administrators Guide System Administrators Guide Virtualization Getting Started Guide in consequences, here is your administrative todo list: Installation Guide https://fedora.zanata.org/project/view/fedora-installation-guide add f25 branch
thanks for your answer @immanetize I would like to tell people to do so, but it's impossible until you do the minimum administrative tasks. So, the request I would like to do is to ask Zanata admins to list Fedora 25 branch of those books in Zanata's docs group. Here are the concerned books:
Installation Guide Networking Guide Release Notes SELinux Users and Administrators Guide System Administrators Guide Virtualization Getting Started Guide
Installation Guide https://fedora.zanata.org/project/view/fedora-installation-guide add f25 branch
Done.
Networking Guide https://fedora.zanata.org/project/view/networking-guide add f24 and f25 branches remove master branch ( or at least deactivate it, we do not translate master, it's your work-in-progress directory and it's non relevant for translation)
Done. I think it makes sense to retain the master branch and lock it so that it is perhaps less confusing.
Release Notes https://fedora.zanata.org/project/view/fedora-release-notes remove master branch (or at least deactivate it)
SELinux Users and Administrators Guide add it to Zanata by creating the project with f25 branch (and if possible, the last branch with translation so we benefit translation memory)
System Administrators Guide https://fedora.zanata.org/project/view/system-administrators-guide add f25 branch remove master branch (or at least deactivate it)
Virtualization Getting Started Guide https://fedora.zanata.org/project/view/virtualization-getting-started-guide add f25 branch remove master branch (or at least deactivate it)
This is a good point. Even if the underlying format will change for docs, translation memory should make the transition a lot easier.
When creating new branches, I've also used zanata's copy translations feature to pre-populate untranslated strings with entries from the zanata translation memory. @jibecfed Let me know if you spot any issues with it, like translations that are completely off, etc.
@jibecfed Also, I can't update the guide listings in https://fedora.zanata.org/version-group/view/docs/. Can you do that?
Thank you doc team!
Not yet (i'm not Zanata Admin), but I know a great contributor who can do this!
@piotrdrag @raven can you please update the docs list in Zanta, with these five projects with F25 branch? I'll produce an announce for the fedora localization project to inform about latest news. Piotr, please let me know if you want to contribute this.
The docs group should be up to date now. Thanks for letting me know - please keep me in the loop in the future.
thank you @raven, but I understood the other documentation are not up-to-date and should not be in the main group.
The only exception I see is "Publican - Fedora brand" used for the 1st page of fedora documentation.
doc team: am I wrong?
@jibecfed I'm not aware of any up-to-date list of Fedora guides that are being actively worked on. You might want to check the git repos listed in https://pagure.io/group/fedora-docs to see if there are any recent commits and update that zanata list accordingly.
Metadata Update from @jibecfed: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.