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

i18n #20

Open
ianmcorvidae opened this issue Jan 31, 2012 · 3 comments
Open

i18n #20

ianmcorvidae opened this issue Jan 31, 2012 · 3 comments
Assignees
Labels

Comments

@ianmcorvidae
Copy link

Riker should be totally i18n-friendly from the beginning. Wherever possible, assuming musicbrainz-server is ever satisfactorily internationalized, translations should be aligned with other MB tools such as Picard and the server.

@ghost ghost assigned kepstin Jan 31, 2012
@kepstin
Copy link
Owner

kepstin commented Jan 31, 2012

This will consist of several parts:

  1. Translation of player user interface strings.
  2. Translation of database fields like languages, countries, gender, AR names, etc.
  3. (optional) ability to use localized aliases for artists, works.

@leftmostcat
Copy link

Depending on the UI toolkit, interface strings should generally be easily internationalized. Both gtk and Qt have solid i18n through gettext. There are also standardized i18n packages for ISO-639, ISO-3166, and ISO-15924 that can and should be used. Idly wondering if it would be possible to have MBS use gettext so we could create a similar package for AR names.

@ianmcorvidae
Copy link
Author

MBS uses gettext already, for what limited translations we have. I may be doing i18n for MBS for SoC next summer; that's a good idea for that project.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants