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

Translating the documentation to french #813

Open
Siltaar opened this issue Oct 4, 2018 · 2 comments
Open

Translating the documentation to french #813

Siltaar opened this issue Oct 4, 2018 · 2 comments

Comments

@Siltaar
Copy link
Contributor

Siltaar commented Oct 4, 2018

I created a pull request with the quick syntax reference translated in .fr.adoc files.

#806

I'm open to discuss about it if needed ^_^

@mojavelinux
Copy link
Member

Thank you for your contribution! This is fantastic.

Now, I have to share some information that hopefully doesn't throw too much of a wrench into this. We are in the process of migrating the documentation to Antora (see https://github.com/asciidoctor/docs.asciidoctor.org). That mostly entails breaking the user manual up into discrete pages and moving the pages out of the asciidoctor.org repository and into the software repositories (e.g., asciidoctor/asciidoctor). (Although I've been making changes to the user manual recently, I've been porting those changes to the migrated site. That's not as easy to do with translation.)

To avoid duplication of effort, what I recommend is waiting until we have the docs migrated, then bring over the French translation as a follow-up step. But we certainly want to keep the branch open since that's what we'll take the files from.

We will need to determine where the French files go in the new structure. But this gives us an opportunity to think about it. The main documentation is going to live in asciidoctor/asciidoctor. Should the French translation live there too? It seems to make sense. Another option is to have a separate repository per translation. That allows the translations to track the upstream, but not get caught up in the release cycles for them.

cc: @graphitefriction

@Jibec
Copy link

Jibec commented Jan 17, 2020

For external readers, I commented directly the pull request with how Fedora community handle this very same subject: #806

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

No branches or pull requests

3 participants