Hey everyone,
I had some discussions about translations with a few people and this is the result:
We have a new epic [1] tracking the initial implementation.
The English pipeline is quite straightforward — it takes the English source and converts it into the English site. That already works today.
Simplified view: `English source -> English site`
The translation pipeline has a few more steps. First, we need to have a script that converts the English sources to POT files [#114] which are used for translations. These POT files need to be stored in a git repository [#110] [#111] and will be consumed by a translation engine which pushes the results back into the repo. To make it consumable for Antora, we need another script that converts the resulting PO files into translated sources [#115] and store them [#112] [#113] somewhere. Before the site can be built, we also need to have a translated UI for each language that also has a language switcher [#116] [#117]. The UI along with the translated sources will be consumed by a build script [#119] that builds the final website.
Simplified view: `English source -> POT files -> PO files -> translated source -> translated site`
Apart from these, we also need to have two new policies. One for adding new content to the docs [#120] which need to ensure that the new content is also being translated properly. The other one will be about introducing a new language [#121] and will make sure that all the repositories are set up and that the UI also supports this new language.
Last thing is the "edit this page" button on translated sites. For that, we probably need to have a page for each language explaining that the content is created and edited in English, and how translations work and how to contribute. And the "edit this page" link (with likely a different wording) will point to that page. There are no cards for this, yet.
So, we need places to store: * POT + PO files for every language [#110] [#111] * translated sources for every language [#112] [#113]
We needs scripts for: * Converting English sources to POT files [#114] * Converting PO files to translated sources for every language [#115] * Converting translated sources + translated UI to the translated site for every language [#119]
And we also need: * Translated UI for every language [#116] [#117] * Policy for adding new content to the docs that ensures adding it also to translations [#120] * Policy for introducing a new language [#121]
As you can see, the implementation will be "translation engine-agnostic" — using POT and PO files. This way we can have some flexibility.
I'll start working on it later this week. If you have any feedback or want to help, let me know!
Cheers! Adam
[1] https://taiga.fedorainfracloud.org/project/asamalik-antora-for-docs/epic/1 [#110] https://taiga.fedorainfracloud.org/project/asamalik-antora-for-docs/us/110 [#111] https://taiga.fedorainfracloud.org/project/asamalik-antora-for-docs/us/111 [#112] https://taiga.fedorainfracloud.org/project/asamalik-antora-for-docs/us/112 [#113] https://taiga.fedorainfracloud.org/project/asamalik-antora-for-docs/us/113 [#114] https://taiga.fedorainfracloud.org/project/asamalik-antora-for-docs/us/114 [#115] https://taiga.fedorainfracloud.org/project/asamalik-antora-for-docs/us/115 [#116] https://taiga.fedorainfracloud.org/project/asamalik-antora-for-docs/us/116 [#117] https://taiga.fedorainfracloud.org/project/asamalik-antora-for-docs/us/117 [#118] https://taiga.fedorainfracloud.org/project/asamalik-antora-for-docs/us/118 [#119] https://taiga.fedorainfracloud.org/project/asamalik-antora-for-docs/us/119 [#120] https://taiga.fedorainfracloud.org/project/asamalik-antora-for-docs/us/120 [#121] https://taiga.fedorainfracloud.org/project/asamalik-antora-for-docs/us/121
Hi, I'm working on this with Adam. It moves fast now :)
Our target is to have a few docs translatable for the f29 release. Probably install-guide, release notes and welcome page.
I'm available on telegram.
Adding trans@lists.fedoraproject.org
On Thu, Sep 27, 2018 at 4:52 PM Adam Samalik asamalik@redhat.com wrote:
Hey everyone,
I had some discussions about translations with a few people and this is the result:
We have a new epic [1] tracking the initial implementation.
The English pipeline is quite straightforward — it takes the English source and converts it into the English site. That already works today.
Simplified view: `English source -> English site`
The translation pipeline has a few more steps. First, we need to have a script that converts the English sources to POT files [#114] which are used for translations. These POT files need to be stored in a git repository [#110] [#111] and will be consumed by a translation engine which pushes the results back into the repo. To make it consumable for Antora, we need another script that converts the resulting PO files into translated sources [#115] and store them [#112] [#113] somewhere. Before the site can be built, we also need to have a translated UI for each language that also has a language switcher [#116] [#117]. The UI along with the translated sources will be consumed by a build script [#119] that builds the final website.
Simplified view: `English source -> POT files -> PO files -> translated source -> translated site`
Apart from these, we also need to have two new policies. One for adding new content to the docs [#120] which need to ensure that the new content is also being translated properly. The other one will be about introducing a new language [#121] and will make sure that all the repositories are set up and that the UI also supports this new language.
Last thing is the "edit this page" button on translated sites. For that, we probably need to have a page for each language explaining that the content is created and edited in English, and how translations work and how to contribute. And the "edit this page" link (with likely a different wording) will point to that page. There are no cards for this, yet.
So, we need places to store:
- POT + PO files for every language [#110] [#111]
- translated sources for every language [#112] [#113]
We needs scripts for:
- Converting English sources to POT files [#114]
- Converting PO files to translated sources for every language [#115]
- Converting translated sources + translated UI to the translated site for
every language [#119]
And we also need:
- Translated UI for every language [#116] [#117]
- Policy for adding new content to the docs that ensures adding it also to
translations [#120]
- Policy for introducing a new language [#121]
As you can see, the implementation will be "translation engine-agnostic" — using POT and PO files. This way we can have some flexibility.
I'll start working on it later this week. If you have any feedback or want to help, let me know!
Cheers! Adam
[1] https://taiga.fedorainfracloud.org/project/asamalik-antora-for-docs/epic/1 [#110] https://taiga.fedorainfracloud.org/project/asamalik-antora-for-docs/us/110 [#111] https://taiga.fedorainfracloud.org/project/asamalik-antora-for-docs/us/111 [#112] https://taiga.fedorainfracloud.org/project/asamalik-antora-for-docs/us/112 [#113] https://taiga.fedorainfracloud.org/project/asamalik-antora-for-docs/us/113 [#114] https://taiga.fedorainfracloud.org/project/asamalik-antora-for-docs/us/114 [#115] https://taiga.fedorainfracloud.org/project/asamalik-antora-for-docs/us/115 [#116] https://taiga.fedorainfracloud.org/project/asamalik-antora-for-docs/us/116 [#117] https://taiga.fedorainfracloud.org/project/asamalik-antora-for-docs/us/117 [#118] https://taiga.fedorainfracloud.org/project/asamalik-antora-for-docs/us/118 [#119] https://taiga.fedorainfracloud.org/project/asamalik-antora-for-docs/us/119 [#120] https://taiga.fedorainfracloud.org/project/asamalik-antora-for-docs/us/120 [#121] https://taiga.fedorainfracloud.org/project/asamalik-antora-for-docs/us/121
--
Adam Šamalík
Software Engineer Red Hat
docs mailing list -- docs@lists.fedoraproject.org To unsubscribe send an email to docs-leave@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/docs@lists.fedoraproject.org
Thanks, Brian.
Adam, Jean-Baptiste, thank you for doing this; I can't wait to see how the system works in practice.
Adam, the proposal looks reasonable. Regarding where to store translated sources: based on the Antora issue for multilang support[0], if I'm reading that right, we should be able to store them in the same repo as the English sources, just in a different directory. We'll just need to move the English version into "en_US/" from the repo root (Antora apparently assumes en_US/ by default) and store other sources in their own directories, but it can all be one repo. I'm just not sure how much of what Dan is talking about in the issue is actually implemented in Antora. Does anyone know what happens if we store the sources in "en_US/modules/<name>/pages" right now - is anything going to break? If not we can just do that right away.
Of course, that requires that someone to periodically in the POs from our translation platform, run the script to apply them to the sources, and push the translated sources in the correct directory. The process was fairly manual before with DocBook/publican, too, so it shouldn't be a huge issue.
Petr
[0] https://gitlab.com/antora/antora/issues/208
On 10/1/18 2:08 PM, Brian (bex) Exelbierd wrote:
Adding trans@lists.fedoraproject.org mailto:trans@lists.fedoraproject.org
On Thu, Sep 27, 2018 at 4:52 PM Adam Samalik <asamalik@redhat.com mailto:asamalik@redhat.com> wrote:
Hey everyone, I had some discussions about translations with a few people and this is the result: We have a new epic [1] tracking the initial implementation. The English pipeline is quite straightforward — it takes the English source and converts it into the English site. That already works today. Simplified view: `English source -> English site` The translation pipeline has a few more steps. First, we need to have a script that converts the English sources to POT files [#114] which are used for translations. These POT files need to be stored in a git repository [#110] [#111] and will be consumed by a translation engine which pushes the results back into the repo. To make it consumable for Antora, we need another script that converts the resulting PO files into translated sources [#115] and store them [#112] [#113] somewhere. Before the site can be built, we also need to have a translated UI for each language that also has a language switcher [#116] [#117]. The UI along with the translated sources will be consumed by a build script [#119] that builds the final website. Simplified view: `English source -> POT files -> PO files -> translated source -> translated site` Apart from these, we also need to have two new policies. One for adding new content to the docs [#120] which need to ensure that the new content is also being translated properly. The other one will be about introducing a new language [#121] and will make sure that all the repositories are set up and that the UI also supports this new language. Last thing is the "edit this page" button on translated sites. For that, we probably need to have a page for each language explaining that the content is created and edited in English, and how translations work and how to contribute. And the "edit this page" link (with likely a different wording) will point to that page. There are no cards for this, yet. So, we need places to store: * POT + PO files for every language [#110] [#111] * translated sources for every language [#112] [#113] We needs scripts for: * Converting English sources to POT files [#114] * Converting PO files to translated sources for every language [#115] * Converting translated sources + translated UI to the translated site for every language [#119] And we also need: * Translated UI for every language [#116] [#117] * Policy for adding new content to the docs that ensures adding it also to translations [#120] * Policy for introducing a new language [#121] As you can see, the implementation will be "translation engine-agnostic" — using POT and PO files. This way we can have some flexibility. I'll start working on it later this week. If you have any feedback or want to help, let me know! Cheers! Adam [1] https://taiga.fedorainfracloud.org/project/asamalik-antora-for-docs/epic/1 [#110] https://taiga.fedorainfracloud.org/project/asamalik-antora-for-docs/us/110 [#111] https://taiga.fedorainfracloud.org/project/asamalik-antora-for-docs/us/111 [#112] https://taiga.fedorainfracloud.org/project/asamalik-antora-for-docs/us/112 [#113] https://taiga.fedorainfracloud.org/project/asamalik-antora-for-docs/us/113 [#114] https://taiga.fedorainfracloud.org/project/asamalik-antora-for-docs/us/114 [#115] https://taiga.fedorainfracloud.org/project/asamalik-antora-for-docs/us/115 [#116] https://taiga.fedorainfracloud.org/project/asamalik-antora-for-docs/us/116 [#117] https://taiga.fedorainfracloud.org/project/asamalik-antora-for-docs/us/117 [#118] https://taiga.fedorainfracloud.org/project/asamalik-antora-for-docs/us/118 [#119] https://taiga.fedorainfracloud.org/project/asamalik-antora-for-docs/us/119 [#120] https://taiga.fedorainfracloud.org/project/asamalik-antora-for-docs/us/120 [#121] https://taiga.fedorainfracloud.org/project/asamalik-antora-for-docs/us/121 -- Adam Šamalík --------------------------- Software Engineer Red Hat _______________________________________________ docs mailing list -- docs@lists.fedoraproject.org <mailto:docs@lists.fedoraproject.org> To unsubscribe send an email to docs-leave@lists.fedoraproject.org <mailto:docs-leave@lists.fedoraproject.org> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/docs@lists.fedoraproject.org-- Brian (bex) Exelbierd | bexelbie@redhat.com mailto:bexelbie@redhat.com | bex@pobox.com mailto:bex@pobox.com Fedora Community Action & Impact Coordinator @bexelbie | http://www.winglemeyer.org
docs mailing list -- docs@lists.fedoraproject.org To unsubscribe send an email to docs-leave@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/docs@lists.fedoraproject.org
Le 2018-10-01 16:20, Petr Bokoc a écrit :
Adam, the proposal looks reasonable. Regarding where to store translated sources: based on the Antora issue for multilang
We decided to have different repositories because Adam think it is more convenient for his CI work and convinced me it will work fine ;) As one repository for all translation file would create multiple issues, we decided to have dedicated repositories to store POT/PO. Please read this page for more details: https://taiga.fedorainfracloud.org/project/asamalik-antora-for-docs/us/110
Of course, that requires that someone to periodically in the POs from our translation platform, run the script to apply them to the sources, and push the translated sources in the correct directory. The process was fairly manual before with DocBook/publican, too, so it shouldn't be a huge issue.
The "fairly manual" process was a real issue in the past. We had a lot of translation that never been published :( What Adam is working on is: automation.
So, we should have something like this:
English source -> POT files -> PO files -> translated source -> translated site
English source => Doc repository ==> (D)
POT files -> PO files => localization repository ==> (L)
translated source => "web" repository ==> (W)
When there is a change in (D), it will call a job, and update pot files in (L) When there is a change in (L), translation platform will know and get updated When there is a change in translation platform, it will update content in (L) every day or night, content from (D) and (L) are used to generate content for (W), and publish it
To be open: I offered to run a test using my own server as translation platform with Weblate and this is a personal choice for the development purpose. What we design is and should be translation platform agnostic.
We have to discuss between translators if we want to use Weblate as a real world test or Zanata for the coming weeks. There is good and bad: Zanata will be stable but will require way more time for automation (I won't go into details here).
On Mon, Oct 1, 2018 at 4:20 PM Petr Bokoc pbokoc@redhat.com wrote:
Thanks, Brian.
Adam, Jean-Baptiste, thank you for doing this; I can't wait to see how the system works in practice.
Adam, the proposal looks reasonable. Regarding where to store translated sources: based on the Antora issue for multilang support[0], if I'm reading that right, we should be able to store them in the same repo as the English sources, just in a different directory. We'll just need to move the English version into "en_US/" from the repo root (Antora apparently assumes en_US/ by default) and store other sources in their own directories, but it can all be one repo. I'm just not sure how much of what Dan is talking about in the issue is actually implemented in Antora. Does anyone know what happens if we store the sources in "en_US/modules/<name>/pages" right now - is anything going to break? If not we can just do that right away.
I'd like to do whatever reasonable automation and side repos we can to keep the English languages sources quick to clone. AIUI our translators will mostly interface (if not exclusively) via tools like Zanata or Weblate and not via raw-uploaded/dowloaded .pot/.po files, so this shouldn't affect them.
regards,
bex
Of course, that requires that someone to periodically in the POs from our translation platform, run the script to apply them to the sources, and push the translated sources in the correct directory. The process was fairly manual before with DocBook/publican, too, so it shouldn't be a huge issue.
Petr
[0] https://gitlab.com/antora/antora/issues/208 On 10/1/18 2:08 PM, Brian (bex) Exelbierd wrote:
Adding trans@lists.fedoraproject.org
On Thu, Sep 27, 2018 at 4:52 PM Adam Samalik asamalik@redhat.com wrote:
Hey everyone,
I had some discussions about translations with a few people and this is the result:
We have a new epic [1] tracking the initial implementation.
The English pipeline is quite straightforward — it takes the English source and converts it into the English site. That already works today.
Simplified view: `English source -> English site`
The translation pipeline has a few more steps. First, we need to have a script that converts the English sources to POT files [#114] which are used for translations. These POT files need to be stored in a git repository [#110] [#111] and will be consumed by a translation engine which pushes the results back into the repo. To make it consumable for Antora, we need another script that converts the resulting PO files into translated sources [#115] and store them [#112] [#113] somewhere. Before the site can be built, we also need to have a translated UI for each language that also has a language switcher [#116] [#117]. The UI along with the translated sources will be consumed by a build script [#119] that builds the final website.
Simplified view: `English source -> POT files -> PO files -> translated source -> translated site`
Apart from these, we also need to have two new policies. One for adding new content to the docs [#120] which need to ensure that the new content is also being translated properly. The other one will be about introducing a new language [#121] and will make sure that all the repositories are set up and that the UI also supports this new language.
Last thing is the "edit this page" button on translated sites. For that, we probably need to have a page for each language explaining that the content is created and edited in English, and how translations work and how to contribute. And the "edit this page" link (with likely a different wording) will point to that page. There are no cards for this, yet.
So, we need places to store:
- POT + PO files for every language [#110] [#111]
- translated sources for every language [#112] [#113]
We needs scripts for:
- Converting English sources to POT files [#114]
- Converting PO files to translated sources for every language [#115]
- Converting translated sources + translated UI to the translated site
for every language [#119]
And we also need:
- Translated UI for every language [#116] [#117]
- Policy for adding new content to the docs that ensures adding it also
to translations [#120]
- Policy for introducing a new language [#121]
As you can see, the implementation will be "translation engine-agnostic" — using POT and PO files. This way we can have some flexibility.
I'll start working on it later this week. If you have any feedback or want to help, let me know!
Cheers! Adam
[1] https://taiga.fedorainfracloud.org/project/asamalik-antora-for-docs/epic/1 [#110] https://taiga.fedorainfracloud.org/project/asamalik-antora-for-docs/us/110 [#111] https://taiga.fedorainfracloud.org/project/asamalik-antora-for-docs/us/111 [#112] https://taiga.fedorainfracloud.org/project/asamalik-antora-for-docs/us/112 [#113] https://taiga.fedorainfracloud.org/project/asamalik-antora-for-docs/us/113 [#114] https://taiga.fedorainfracloud.org/project/asamalik-antora-for-docs/us/114 [#115] https://taiga.fedorainfracloud.org/project/asamalik-antora-for-docs/us/115 [#116] https://taiga.fedorainfracloud.org/project/asamalik-antora-for-docs/us/116 [#117] https://taiga.fedorainfracloud.org/project/asamalik-antora-for-docs/us/117 [#118] https://taiga.fedorainfracloud.org/project/asamalik-antora-for-docs/us/118 [#119] https://taiga.fedorainfracloud.org/project/asamalik-antora-for-docs/us/119 [#120] https://taiga.fedorainfracloud.org/project/asamalik-antora-for-docs/us/120 [#121] https://taiga.fedorainfracloud.org/project/asamalik-antora-for-docs/us/121
--
Adam Šamalík
Software Engineer Red Hat
docs mailing list -- docs@lists.fedoraproject.org To unsubscribe send an email to docs-leave@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/docs@lists.fedoraproject.org
-- Brian (bex) Exelbierd | bexelbie@redhat.com | bex@pobox.com Fedora Community Action & Impact Coordinator @bexelbie | http://www.winglemeyer.org
docs mailing list -- docs@lists.fedoraproject.org To unsubscribe send an email to docs-leave@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/docs@lists.fedoraproject.org
-- Petr Bokoč (pbokoc) Senior Technical Writer Community Platform Engineering
Red Hat Czech, s. r. o. Purkyňova 99 612 45 Brno, Czech Republic
docs mailing list -- docs@lists.fedoraproject.org To unsubscribe send an email to docs-leave@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/docs@lists.fedoraproject.org
On Mon, Oct 1, 2018 at 4:20 PM Petr Bokoc pbokoc@redhat.com wrote:
Thanks, Brian.
Adam, Jean-Baptiste, thank you for doing this; I can't wait to see how the system works in practice.
Adam, the proposal looks reasonable. Regarding where to store translated sources: based on the Antora issue for multilang support[0], if I'm reading that right, we should be able to store them in the same repo as the English sources, just in a different directory. We'll just need to move the English version into "en_US/" from the repo root (Antora apparently assumes en_US/ by default) and store other sources in their own directories, but it can all be one repo. I'm just not sure how much of what Dan is talking about in the issue is actually implemented in Antora. Does anyone know what happens if we store the sources in "en_US/modules/<name>/pages" right now - is anything going to break? If not we can just do that right away.
Of course, that requires that someone to periodically in the POs from our translation platform, run the script to apply them to the sources, and push the translated sources in the correct directory. The process was fairly manual before with DocBook/publican, too, so it shouldn't be a huge issue.
Mixing the original English source with anything else is exactly what we want to avoid. That's mostly for two reasons:
1) We don't always have permissions to modify the source repository. Even though we did, it might be invasive. 2) People are never supposed to edit the translated sources. All work happens in a translation platform that consumes POT files and produces PO files.
That's why we keep the source repos unmodified. We'll convert them to POT, load that to the translation platform which is where human interaction happens, and then we go the PO -> asciidoc -> website in basically one step.
How does that sound?
Petr
[0] https://gitlab.com/antora/antora/issues/208 On 10/1/18 2:08 PM, Brian (bex) Exelbierd wrote:
Adding trans@lists.fedoraproject.org
On Thu, Sep 27, 2018 at 4:52 PM Adam Samalik asamalik@redhat.com wrote:
Hey everyone,
I had some discussions about translations with a few people and this is the result:
We have a new epic [1] tracking the initial implementation.
The English pipeline is quite straightforward — it takes the English source and converts it into the English site. That already works today.
Simplified view: `English source -> English site`
The translation pipeline has a few more steps. First, we need to have a script that converts the English sources to POT files [#114] which are used for translations. These POT files need to be stored in a git repository [#110] [#111] and will be consumed by a translation engine which pushes the results back into the repo. To make it consumable for Antora, we need another script that converts the resulting PO files into translated sources [#115] and store them [#112] [#113] somewhere. Before the site can be built, we also need to have a translated UI for each language that also has a language switcher [#116] [#117]. The UI along with the translated sources will be consumed by a build script [#119] that builds the final website.
Simplified view: `English source -> POT files -> PO files -> translated source -> translated site`
Apart from these, we also need to have two new policies. One for adding new content to the docs [#120] which need to ensure that the new content is also being translated properly. The other one will be about introducing a new language [#121] and will make sure that all the repositories are set up and that the UI also supports this new language.
Last thing is the "edit this page" button on translated sites. For that, we probably need to have a page for each language explaining that the content is created and edited in English, and how translations work and how to contribute. And the "edit this page" link (with likely a different wording) will point to that page. There are no cards for this, yet.
So, we need places to store:
- POT + PO files for every language [#110] [#111]
- translated sources for every language [#112] [#113]
We needs scripts for:
- Converting English sources to POT files [#114]
- Converting PO files to translated sources for every language [#115]
- Converting translated sources + translated UI to the translated site
for every language [#119]
And we also need:
- Translated UI for every language [#116] [#117]
- Policy for adding new content to the docs that ensures adding it also
to translations [#120]
- Policy for introducing a new language [#121]
As you can see, the implementation will be "translation engine-agnostic" — using POT and PO files. This way we can have some flexibility.
I'll start working on it later this week. If you have any feedback or want to help, let me know!
Cheers! Adam
[1] https://taiga.fedorainfracloud.org/project/asamalik-antora-for-docs/epic/1 [#110] https://taiga.fedorainfracloud.org/project/asamalik-antora-for-docs/us/110 [#111] https://taiga.fedorainfracloud.org/project/asamalik-antora-for-docs/us/111 [#112] https://taiga.fedorainfracloud.org/project/asamalik-antora-for-docs/us/112 [#113] https://taiga.fedorainfracloud.org/project/asamalik-antora-for-docs/us/113 [#114] https://taiga.fedorainfracloud.org/project/asamalik-antora-for-docs/us/114 [#115] https://taiga.fedorainfracloud.org/project/asamalik-antora-for-docs/us/115 [#116] https://taiga.fedorainfracloud.org/project/asamalik-antora-for-docs/us/116 [#117] https://taiga.fedorainfracloud.org/project/asamalik-antora-for-docs/us/117 [#118] https://taiga.fedorainfracloud.org/project/asamalik-antora-for-docs/us/118 [#119] https://taiga.fedorainfracloud.org/project/asamalik-antora-for-docs/us/119 [#120] https://taiga.fedorainfracloud.org/project/asamalik-antora-for-docs/us/120 [#121] https://taiga.fedorainfracloud.org/project/asamalik-antora-for-docs/us/121
--
Adam Šamalík
Software Engineer Red Hat
docs mailing list -- docs@lists.fedoraproject.org To unsubscribe send an email to docs-leave@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/docs@lists.fedoraproject.org
-- Brian (bex) Exelbierd | bexelbie@redhat.com | bex@pobox.com Fedora Community Action & Impact Coordinator @bexelbie | http://www.winglemeyer.org
docs mailing list -- docs@lists.fedoraproject.org To unsubscribe send an email to docs-leave@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/docs@lists.fedoraproject.org
-- Petr Bokoč (pbokoc) Senior Technical Writer Community Platform Engineering
Red Hat Czech, s. r. o. Purkyňova 99 612 45 Brno, Czech Republic
docs mailing list -- docs@lists.fedoraproject.org To unsubscribe send an email to docs-leave@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/docs@lists.fedoraproject.org
Hi!
I just wanted to add that currently not everyone is writing with one sentence per line in the docs. We really ought to put some guidelines for docs that this is important, as recommended by the Asciidoctor team. There are plenty of inspiring videos from on how to do this and why it matters. This can help to keep the quality of conversion on a good level. Some languages are prone to long sentences and that has to be dealt with on each language basis itself.
When translating it should be possible to move some "meaning" from one sentence to another because in some languages the structure of text is so different that it doesn't make any sense to translate each one by itself. Maybe we could encourage translators to use the asciidoc comments, this needs to be solved as efficient as possible, any ideas how it could be done?
Cheers Gleb
Le 2018-10-30 09:47, Gleb Vassiljev a écrit :
Maybe we could encourage translators to use the asciidoc comments, this needs to be solved as efficient as possible, any ideas how it could be done?
Hi, can you describe how does it looks like and what could be the translation process of this?
-
Adam Samalik -
Brian (bex) Exelbierd -
Gleb Vassiljev -
Jean-Baptiste -
Jean-Baptiste Holcroft
-
Petr Bokoc