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.

Sign up for GitHub

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

Jump to bottom

translation / i18n / l10n #42

Open
1 of 4 tasks
Razish opened this issue Apr 19, 2020 · 7 comments
Open
1 of 4 tasks

translation / i18n / l10n #42

Razish opened this issue Apr 19, 2020 · 7 comments
Labels
C: usability category: usability M: assets module: assets M: client module: client P: help wanted priority: help wanted P: medium priority: medium S: open status: open T: tracking type: tracking (meta)

Comments

@Razish
Copy link
Contributor

Razish commented Apr 19, 2020 •
edited

tasks

  • 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.
@Razish Razish added P: help wanted priority: help wanted M: assets module: assets M: client module: client P: medium priority: medium S: open status: open T: tracking type: tracking (meta) labels Apr 19, 2020
@TriForceX
Copy link

Spanish 👍

@Razish Razish changed the title string translations + coverage translation / i18n Apr 19, 2020
@Razish Razish changed the title translation / i18n translation / i18n / l10n Apr 19, 2020
@ensiform
Copy link
Contributor

What about switching to utf8 support?

@Razish Razish added the C: usability category: usability label Apr 19, 2020
@TriForceX
Copy link

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
Copy link

Exmirai commented Apr 20, 2020

ready to translate to russian

@admafi
Copy link

admafi commented Apr 20, 2020

I could translate to German if needed

@ensiform
Copy link
Contributor

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

@TrayHard
Copy link

TrayHard commented May 1, 2020

Ready to translate everything in Russian 👌

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
C: usability category: usability M: assets module: assets M: client module: client P: help wanted priority: help wanted P: medium priority: medium S: open status: open T: tracking type: tracking (meta)
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
6 participants
@Razish @ensiform @admafi @Exmirai @TrayHard @TriForceX