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

Create a translation dictionary guideline file for consistent localization #191

Open
G3mha opened this issue Dec 3, 2024 · 3 comments
Open

Comments

@G3mha
Copy link
Contributor

G3mha commented Dec 3, 2024

I noticed while doing some of the translations that we could benefit from having a standardized dictionary for terms that should or should not be translated across different languages.

I propose we create a new file to help maintainers and contributors with consistent translations.

Motivation

  • Some technical terms and names should remain in English (e.g. RetroAchievements, RA, DevJam, hardcore, leaderboard, ...)
  • Certain terms require specific translations to maintain consistency (e.g. Achievement -> "Conquista" in Portuguese)
  • This will help avoid confusion and maintain quality across translations

Proposed Solution

Create a new file translation-dictionary.md in the docs root with the following structure:

# Translation Dictionary Guidelines

## Portuguese (pt-BR)

### Do Not Translate
- RetroAchievements
- DevJam 
- DevQuest
- RANews
- Softcore
- Hardcore
- RAM
- ROM
- API
- ID

### Standard Translations
| English | Portuguese |
|---------|------------|
| Achievement | Conquista |
| Leaderboard | Tabela de Classificação |
| Badge | Emblema |
| Set | Conjunto |
| Points | Pontos |
| Developer | Desenvolvedor |
| Game | Jogo |
| System | Console |

Implementation Steps

  1. Create the initial dictionary file with Portuguese terms
  2. Review current translations to align with the new guidelines

Future Considerations

  • Expand to include spanish (ES) translations
  • Create automated checks for consistent term usage

@wescopeland Can I start working on it?

@wescopeland
Copy link
Member

Hi @G3mha!

I agree this is a problem, but I feel mixed about the proposed solution.

RAWeb has recently started moving all translations to Crowdin: https://crowdin.com/project/retroachievements
This does support an automated translation dictionary.

I would be curious if VitePress pages could also be translated using Crowdin.

@wescopeland
Copy link
Member

Looks like there are other VitePress sites out there also using Crowdin: https://element-plus.org/en-US/guide/translation.html

@wescopeland
Copy link
Member

Speaking of Crowdin, there are a few missing pt-BR strings in RAWeb we could use help with 😅
They can be found by visiting the Crowdin link above and navigating to the untranslated strings for pt-BR: https://crowdin.com/editor/retroachievements/14/enus-ptbr?view=side-by-side&filter=basic&value=2

This may give you a sense of what translating something in Crowdin might look like if we were to adopt it here.

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

2 participants