request support for localization/translation

[luiscarlos2000]

Hi,
Luis carlos here. Testing this addon recently and it has some potential. Could you add translation/localization support? As I see there's no localization support yet. I could collaborate for a spanish translation of the addon.
Best,
Luis

[trssharp]

Subject: ClassicSpeech Spanish translation ready

Hi Luis,

Sorry for the delay. I've been really busy at work lately and just saw this yesterday.

The localization foundation for ClassicSpeech is now on main:

https://github.com/trssharp/classicspeech-nvda

What’s there

• locale/classicspeech.pot — template with all 352 extractable strings
• locale/es/LC_MESSAGES/nvda.po — Spanish catalog with 21 common NVDA terms pre-filled (Cancel, OK, Close, Off, etc.)
• locale/README.md — short translator workflow notes

How to translate

1. Fork the repo
2. Create a branch from main
3. Open locale/es/LC_MESSAGES/nvda.po in Poedit (free; Windows/macOS/Linux)
4. Translate the untranslated entries — Poedit shows context, handles plurals, and can compile the .mo on save
5. Optionally verify with:
   • python scripts/update_translations.py --language es
   • or package the add-on with python scripts/package_addon.py
6. Push your branch and open a PR against main

Notes

• Only user-visible text is translated. Internal config IDs (profile names, token keys, and stored setting values) stay in English so saved settings keep working across languages.
• ClassicSpeech follows NVDA’s interface language automatically; there is no separate language setting.
• Incomplete translations are fine — missing strings fall back to English one by one.

If anything is unclear, or you’d rather use a different workflow (Weblate, direct file edit, etc.), I’m happy to walk through it.

Thanks!

[luiscarlos2000]

Hi trssharp
No worries, just was waiting for an answer. Did a commit. Recquires a workflow approval. Um, pending? interesting. See what I've committed.