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

"Community reporting" : French translation of the tutorial #1763

Closed
mathieubossaert opened this issue Mar 25, 2024 · 11 comments
Closed

"Community reporting" : French translation of the tutorial #1763

mathieubossaert opened this issue Mar 25, 2024 · 11 comments

Comments

@mathieubossaert
Copy link
Contributor

I will animate a small workshop about entities on Friday 6 April.
Instead of creating my own content, would you be interested by a french translation of the tutorial (docs/tutorial-community-reporting.rst ), the text, not the video ;-) ?

@mathieubossaert mathieubossaert changed the title "Community reportin" French translation of the tutorial "Community reporting" : French translation of the tutorial Mar 25, 2024
@lognaturel
Copy link
Member

That would be wonderful! Happy to collaborate with you on that however is most helpful and then we can find a good way to add it to the docs themselves as a "community translation." That will be very exciting.

As you're going through it, also happy to have suggestions on the base English content if you see opportunities to add clarity or generally make the examples more helpful.

@mathieubossaert
Copy link
Contributor Author

The work in progress :
https://github.com/mathieubossaert/odk_docs/blob/main/tutorial-community-reporting.rst

I think tonight the first translation will be ok and ready to review and I'll still have to translate the forms.

@mathieubossaert
Copy link
Contributor Author

@lognaturel I translated the forms (a copy of the forms on my own googledrive, for both question and labels
I need to test it now and to read it again and again to track mistakes.
And also to make screenshots from a french Central instance.

@lognaturel
Copy link
Member

Je viens de lire le texte et c'est très bien réussi.

For including the document in the repository, I propose that we start with an ad-hoc approach. How about you create translations/fr directories in both docs/ and docs/img to put your new files?

You'll need a unique name for the document, something like tutoriel-signalement-problemes, even in that new directory.

The images and section names (e.g. .. _tutorial-entities-capture-problem:) will also need to be unique so you could translate them.

I see a few issues with the RST formatting. I propose you put in a PR and I can help with that part.

@mathieubossaert
Copy link
Contributor Author

mathieubossaert commented Mar 28, 2024

Thanks a lot Hélène 🙂
I'll try tomorrow morning but it will be difficult.
Tuesday morning for sure.

@lognaturel
Copy link
Member

Absolutely no rush on my end! If you want to keep it in your repo for now, no problem, it's up to you how you want to share it!

@mathieubossaert
Copy link
Contributor Author

No rush for me neither.
I just want it finished for our workshop next friday. It will be a good test.
We have plenty of time to share it widely

@mathieubossaert
Copy link
Contributor Author

And in fact I found some time to fork the repo and start the work 🙂 https://github.com/mathieubossaert/getodk_docs

@mathieubossaert
Copy link
Contributor Author

mathieubossaert commented Apr 1, 2024

Everything seems to be fine on my side :-)
With french screenshots from working forms, with unique names, as for the section.

What about translating this image : https://docs.getodk.org/_static/img/tutorial-community-reporting.png

@lognaturel
Copy link
Member

What about translating this image

I'll work on it with @alyblenkin!

@lognaturel
Copy link
Member

Now published at https://docs.getodk.org/language/fr/tutoriel-signalement-problemes/

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 a pull request may close this issue.

2 participants