Translation guidelines

[OriolAbril]

We should write some guidelines (or maybe simply link to some existing ones that we like) on translations, have a glossary of specific terms (e.g. mentee->aprendiz in spanish) to ensure coherence and some other conventions. cc @Anavelyz

[Mishra-Pratik]

I’m interested in contributing to this project and would love to work on this issue. Could you please provide more details or guidance on how I can get started?
Looking forward to your response.

Thanks!
Pratik

[Anavelyz]

I’m interested in contributing to this project and would love to work on this issue. Could you please provide more details or guidance on how I can get started? Looking forward to your response.

Thanks! Pratik

Hi @Mishra-Pratik, nice!

At the 2023 unconference we started with a document in drive, you can check it out here.
Do you want to create a style guide for a specific language?

[sanchalitorpe-source]

Draft translation guidelines (initial version)

General

• Keep translations clear and simple.
• Prefer commonly used terms over literal translations.
• Be consistent across files.

Terminology

• Use a shared glossary for key terms (e.g. mentee, mentor).
• If unsure about a term, leave a comment in the PR.

Style

• Use inclusive and respectful language.
• Keep the same tone as the original text.

Workflow

• Translations are submitted via GitHub pull requests.
• Small, incremental contributions are welcome.

This is a starting point suggestions and language-specific additions are welcome.