Skip to content
This repository has been archived by the owner on May 1, 2024. It is now read-only.

FAQ translation? #21

Closed
spacewasabi opened this issue Feb 3, 2023 · 3 comments
Closed

FAQ translation? #21

spacewasabi opened this issue Feb 3, 2023 · 3 comments

Comments

@spacewasabi
Copy link
Contributor

Would it be worth adding translations for this FAQ?

For instance having on this repo a folder "translation" and having the README.md translated in multiple languages, then adding each translation at the top of the main README for easier access.

If you think that would be an interesting idea, I can help with french translation for example (maybe portuguese and spanish too).

@connyduck
Copy link
Contributor

Yes, definitely an interesting idea! The question is how to keep them in sync 🤔
Maybe we should setup Weblate and move the Faqs to the website or something.
But you can definitely get started in this repo as well!

@spacewasabi
Copy link
Contributor Author

Hello @connyduck ! Thanks for showing interest in my idea!
I've never used Weblate and I don't think I will have enough time to dive into it for the next few weeks, but if you ever decide to do it this way (which sounds like a good idea to me!) I'll jump on the opportunity to get accustomed to this tool.
For now I simply translated it by hand and put the french file in a separate folder, if that can temporarily work for you then I'll create a pull request.
Also before pushing any commit, I would like to know if you have any naming preferences for files &/or any wish for the structure of the "translated" folder.

For example :

  • translated folder with all the files named "language_name.md"
  • or translated folder with multiple folders named "language_name" containing a unique README.md file

@connyduck
Copy link
Contributor

translated folder with all the files named "language_name.md"

this sounds good!

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

No branches or pull requests

2 participants