🤖AI-generated documentation☐ curatedAI Generated
About content generation types
(e.g., docs generated from codebase analysis)
(e.g., livestream → blog post, meeting notes → docs)
(e.g., hand-written tutorial)
Translating SkellyCam
We use community translations to make motion capture accessible worldwide. No coding required — just edit a JSON file and open a PR.
Browse translation files on GitHub
Current Status
All non-English translations are AI-generated and unreviewed — they almost certainly contain errors. Even fixing a few strings helps!
Translation Files
All UI strings live in skellycam-ui/src/i18n/locales/. English (en-english.json) is the source of truth. All other languages are AI-generated and waiting for community review.
Currently supported: English, Spanish, French, German, Italian, Portuguese (Brazil), Catalan, Dutch, Swedish, Polish, Czech, Romanian, Hungarian, Greek, Croatian, Serbian, Ukrainian, Russian, Georgian, Turkish, Arabic, Farsi, Urdu, Hindi, Bengali, Tamil, Nepali, Sinhala, Chinese (Simplified), Japanese, Korean, Thai, Vietnamese, Indonesian, Malay, Tagalog, Myanmar, Swahili, and Amharic.
How to Contribute
- Click any language file above (or find it in
skellycam-ui/src/i18n/locales/) - Click the pencil icon to edit directly on GitHub
- Fix any translations you see that are wrong or awkward
- Submit a pull request
Strings use i18next format — preserve {{variables}} exactly as-is and keep _one/_other suffixes for plurals.
Backend strings (camera names, log messages, codecs, file paths) don't need translation - that would be too much work to handle in a way that didn't risk the functionality of the core application.
Questions?
Open an issue on GitHub or reach out on the FreeMoCap Discord.