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

Add multilingual support / i18n #124

Closed
aseprite-bot opened this issue Aug 20, 2014 · 9 comments
Closed

Add multilingual support / i18n #124

aseprite-bot opened this issue Aug 20, 2014 · 9 comments

Comments

@aseprite-bot
Copy link

@aseprite-bot aseprite-bot commented Aug 20, 2014

From davidcapello on June 30, 2012 18:34:31

Create an easy way (maintainable) to integrate translations into gui.xml and widgets (without duplicating those files, e.g. we don't want to maintain gui-es.xml as a Spanish translation of gui.xml).

Spanish: davidcapello
Russian and Ukraine: https://plus.google.com/b/102156040653649496700/102156040653649496700/posts/iQXUP3m8vef
Russian: https://twitter.com/_frenetic/status/218789216967065601

Original issue: http://code.google.com/p/aseprite/issues/detail?id=124

We have several issues to solve:

  • Add a file with translated strings (data/strings/en.ini)
  • Add a way to indicated strings from en.ini in widgets XML files (ff95e63)
  • Support in the "ui" layer to render Unicode chars with FreeType and HarfBuzz libraries
  • Add support to mix sprite sheet-based fonts with truetype font to draw Unicode chars that are not available in the sprite sheet (867ab89)
  • A way to translate text on gui.xml
@aseprite-bot
Copy link
Author

@aseprite-bot aseprite-bot commented Aug 20, 2014

From cod...@gmail.com on July 01, 2012 13:36:55

I could translate the application to Dutch. I could try to do French and German too, but I'm not fluent in those languages.

@dacap
Copy link
Member

@dacap dacap commented Jan 30, 2016

A lot of people is asking for multi-language support (Japanese and Chinese mainly). So this issue should be reprioritized in some way. (Internal Note: Unicode chars should be rendered using FreeType library with an Unicode font, like Arial Unicode.)

@dacap dacap added this to the v1.2 milestone Jan 30, 2016
@dacap dacap self-assigned this Jan 30, 2016
@NeoKune
Copy link

@NeoKune NeoKune commented Jan 30, 2016

Does linguistic mounting of Japanese and Chinese involve difficulty?

@dacap
Copy link
Member

@dacap dacap commented Jan 30, 2016

Hi @NeoKune, the only problem I see at the moment (compared with other languages) is the usage of (Unicode) characters that are not in the pixel-art font. That means that we will need a bigger (TrueType) font (e.g. Arial Unicode). Doing so we will need bigger user interface (menus/buttons/etc) to fit the new font size.

@dacap dacap modified the milestones: v1.1, v1.3 Mar 7, 2016
@dacap
Copy link
Member

@dacap dacap commented Mar 7, 2016

I've started working on this issue (mainly the part to render Unicode characters so we can see file names correctly)

@NeoKune
Copy link

@NeoKune NeoKune commented Mar 11, 2016

Hooray!!
I'm already looking forward to it. :D

@dacap dacap modified the milestones: v1.2, v1.1 May 23, 2016
@dacap dacap mentioned this issue Feb 3, 2017
4 of 9 tasks complete
dacap added a commit that referenced this issue Feb 6, 2017
@dacap dacap modified the milestones: v1.2, v1.3 Sep 12, 2017
@dacap dacap changed the title Add multilingual support Add multilingual support / i18n Oct 9, 2017
dacap added a commit that referenced this issue Oct 17, 2017
This is the first step for a full i18n (#124).
dacap added a commit that referenced this issue Dec 1, 2017
Related to #124
@xMrVizzy
Copy link

@xMrVizzy xMrVizzy commented Feb 10, 2018

Russian translation already done, waiting to support! :)

dacap added a commit that referenced this issue Mar 19, 2018
@dacap
Copy link
Member

@dacap dacap commented Mar 19, 2018

Next version will have support to create extensions with new languages. Example

@dacap dacap modified the milestones: v1.3, v1.2 Apr 4, 2018
@dacap
Copy link
Member

@dacap dacap commented Apr 4, 2018

I'll close this issue because most of the work is already done in v1.2. The only missing thing is discovering strings that need translation which I think it will be a progressive development (just like finding stuff that is missing in the theme customization).

@dacap dacap closed this Apr 4, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
4 participants