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

Use an existing translation library instead of writing our own? #198

Open
josefnpat opened this issue Apr 12, 2015 · 3 comments
Open

Use an existing translation library instead of writing our own? #198

josefnpat opened this issue Apr 12, 2015 · 3 comments

Comments

@josefnpat
Copy link
Owner

@positive07 mentioned this on IRC that we should consider using a translation project instead of trying to write our own for vapor-core. I'm thinking this is a very good idea, as the old "library" was simply a table of strings with a marked index.

@pablomayobre
Copy link

i18n.lua from Kikito is a good option, but there is also a whole project with translations that has many languages in already

@EntranceJew
Copy link

@positive07 I prefer i18n, personally, and I think we can find a way to make those project translations usable by i18n. Finding a way to make them usable without forking the sheet or reformatting it might be a little more complicated.

@pablomayobre
Copy link

I thought the same thing haha, yeah that is the best way!

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

No branches or pull requests

3 participants