Skip to content
This repository has been archived by the owner on Jul 20, 2023. It is now read-only.

Add i18n support #62

Open
gaecoli opened this issue Jun 20, 2023 · 6 comments
Open

Add i18n support #62

gaecoli opened this issue Jun 20, 2023 · 6 comments
Assignees

Comments

@gaecoli
Copy link
Member

gaecoli commented Jun 20, 2023

I think we need to add multilingual support so that everyone can use this product better

@justinclift
Copy link
Member

Yeah, that's a good idea. Most of the multilingual stuff I've seen before uses some form of token and look up table to achieve it.

That doesn't always work out well for languages that are right-to-left (eg Arabic, Hebrew), or those which are vertical (Chinese, Korean, Japanese). Doing a quick search online now, it seems like at least Chinese, Korean, and Japanese are ok to be written horizontally these days, so that might not be all that much of a problem.

For our needs, we probably only need to do the web interface stuff. So, a javascript only based system (rather than needing to include Python) should be fine.

Thoughts? 😄

@Avey777
Copy link

Avey777 commented Jun 20, 2023

recommend this:
https://github.com/tolgee/tolgee-platform

@gaecoli
Copy link
Member Author

gaecoli commented Jun 20, 2023

Yes. Just javascript.

@justinclift
Copy link
Member

Hmmm, to me that looks like the wrong end of it.

Shouldn't we use Launchpad or an existing online service for the actual translation?

I was more thinking about using a library for doing the text lookup and string display in our web interface.

@gaecoli gaecoli self-assigned this Jun 21, 2023
@gaecoli
Copy link
Member Author

gaecoli commented Jun 21, 2023

Hmmm, to me that looks like the wrong end of it.

Shouldn't we use Launchpad or an existing online service for the actual translation?

I was more thinking about using a library for doing the text lookup and string display in our web interface.

You are right!

@justinclift
Copy link
Member

Cool. As a data point, my mention of Launchpad above is only because I used to use it for translation strings many years ago.

I haven't touched it since then though, so it's completely possible there are much better options around. 😄

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

No branches or pull requests

3 participants