Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

French complete, update and proofread version of the asciidoc-syntax-quick-reference #806

Open
wants to merge 7 commits into
base: main
Choose a base branch
from

Conversation

Siltaar
Copy link
Contributor

@Siltaar Siltaar commented Sep 20, 2018

Every files are named in .fr.adoc.

@papilip
Copy link

papilip commented Jan 10, 2019

Hello all,
Why this PR is not merged ?
Thanks team to make a response @mojavelinux ...
Papilip, french asciidoc user and advocate for non it people

@mojavelinux
Copy link
Member

mojavelinux commented Jan 10, 2019

The reason this is not merged is because the whole documentation is being moved to a different location and reworked. I mentioned this in a related thread on the mailinglist, but I have not yet followed up here.

We're in the final stages of moving the documentation. Once that move is complete, we'll look in setting up the structure for the French translation. Note, however, that will require support from Antora.

You can find the work in progress here: https://github.com/asciidoctor/docs.asciidoctor.org

For the record, I'm a huge supporter of translations too. We just have two different changes going on right now and we need to reconcile the efforts.

@Siltaar
Copy link
Contributor Author

Siltaar commented Aug 2, 2019

Hi,

A bit before celebrating the 1st year of this work, I published it here : https://framagit.org/Siltaar/asciidoctor-docs-fr

To let interested people read it already, and maybe improving its up-to-dateness.

Looking forward to hearing from this merge request.

@mojavelinux
Copy link
Member

I do apologize for the delay. Unfortunately, the effort to migrate the docs to their new home is still ongoing, which is holding up getting this integrated. We do plan to maintain the translation in a dedicated repository, so you've actually taken an important step in that direction. I'll definitely circle back once the foundation docs are in place so we can begin integrating the content into the new site.

@Jibec
Copy link

Jibec commented Jan 17, 2020

Hi there, could I recommend not handle localization this way?

As a Fedora translator, with help of Adam Samalik, we created a set of strings to automate the translation of our documentation.

This may contain some Antora specifics, but you'll find more information there: https://fedoraproject.org/wiki/User:Jibecfed/fedoradoc-antora-localization

Example:
This page https://docs.stg.fedoraproject.org/en-US/council/contact/
it's asciidoc is here: https://pagure.io/Fedora-Council/council-docs/tree/master
we'll convert it into gettext here: https://pagure.io/fedora-docs-l10n/council
the translator works here: https://translate.stg.fedoraproject.org/projects/fedora-l10ncouncil/
translated adoc files are published there: https://pagure.io/fedora-docs/translated-sources/

The scripts we are using: https://pagure.io/fedora-docs/translations-scripts/
All of this is using the great https://po4a.org/

I'll be please to provide my help to automate this.

What is the benefit?
Docs writer don't get any commit for translations.
Translators know each time a content requires update and don't have to play with Git.
Automation glue this so that website is always up to date (no translation = English content published).

As Fedora localization administrator, as long as the license is open, I'll be pleased to host the translation of your project in our translation platform.

@mojavelinux
Copy link
Member

@Jibec Yes, I would very much like to explore that approach and I welcome your offer. I yield to your experience. Fortunately, the Asciidoctor docs are in the process of being migrated to Antora. Once that is complete, we can follow the same model you're already using. And it will be easier to manage since the topics will split out into separate pages. Here's the WIP starting point: https://github.com/asciidoctor/docs.asciidoctor.org

I'll be pleased to host the translation of your project in our translation platform.

I'd be very interested. Can you open an issue at https://github.com/asciidoctor/docs.asciidoctor.org so we can track and coordinate that? (better than talking at the bottom of a PR).

@mojavelinux
Copy link
Member

cc: @graphitefriction

@mojavelinux
Copy link
Member

the Asciidoctor docs are in the process of being migrated to Antora.

FYI, the migration is now complete. See https://docs.asciidoctor.org/asciidoc/latest/syntax-quick-reference/

@Jibec
Copy link

Jibec commented Apr 9, 2021 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants