translation / i18n / l10n

Razish commented 4 years ago

tasks

[x] amalgamate language directories in strings/ to a mega translation file -- done
[ ] sweep string literals/hardcoded messages for stringed candidates. keep this in mind for future code.
[ ] think about using a new file format (json ftw?)
[ ] tool to check translation coverage (build/package step?) a tool exists (in the aether) to cross-check strings that have been translated to specific language. a special token is used to indicate "same as original language". we can write our own equivalent, easier with a new format.

targeted languages

We only target a small amount of languages due to both human resource availability and code complexity.

English (main)
French (TL: @Yberion)
German (TL: @admafi)
Russian (TL: @Exmirai, @TrayHard)
Spanish: (TL: @TriForceX?)
???

TriForceX commented 4 years ago

Spanish 👍

ensiform commented 4 years ago

What about switching to utf8 support?

TriForceX commented 4 years ago

Since encoding problems can be weird and difficult to deal with, utf-8 should be the default for any library/application nowadays because it allows you to display all characters for all languages

Exmirai commented 4 years ago

ready to translate to russian

admafi commented 4 years ago

I could translate to German if needed

ensiform commented 4 years ago

There's services for that if you use a more standard format

TrayHard commented 4 years ago

Ready to translate everything in Russian 👌

CleanJK / cleanjk

translation / i18n / l10n #42

tasks

targeted languages