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

Request for Help creating tests for ALL locales #1

Open
deankarn opened this issue Feb 16, 2016 · 4 comments
Open

Request for Help creating tests for ALL locales #1

deankarn opened this issue Feb 16, 2016 · 4 comments

Comments

@deankarn
Copy link
Contributor

deankarn commented Feb 16, 2016

UPDATE: universal-translator's locales + rules have been split into another repo locales

please see here for helping with locale tests.

@joeblew99
Copy link

I have an idea

Just ask one of the many translation companies for test date that is for al languages. They would have some for sure.

There are many companies out there to choose from.

Also, you going to want to do some basic integration with there Transaltion companies Or one of the standard translation file formats / schemas, so you can kill two birds with one stone here maybe.

This is something i was working on last week, and i am very keen to get a good workflow and tooling for localisation. So happy to help if i can .

Can you also explain why you want to embed the translation files ? It can be done in golang by using a virtual file system also i think. Here is an advanced one, that may work for you:
https://github.com/shurcooL/vfsgen
The guy that wrote it is very open to feedback too.

@deankarn
Copy link
Contributor Author

deankarn commented Jul 21, 2016

Hello @joeblew99 I am very open to any help or suggestions that you could provide 👍

I have been so pressed for time lately...

If you could get the Date & Time, Number and Currency formatting for all language, that would be a huge step forward as that is what I'm missing.

as for a standard translation file format, I convert all data within this lib from CLDR project, which should be pretty standard, the resource generator is here

As for embedding the translation files, I have been doing that with another project for quite some time before creating this library, and has been nothing but a pain during the build process. I see no real benefit in not having the translations inline, and since that's what would happen after using tools like vfsgen why not program the translations inline. I have no problem adding support for loading from files in the future.

@deankarn
Copy link
Contributor Author

UPDATE: universal-translator's locales + rules have been split into another repo locales

please see here for helping with locale tests.

@joeblew99
Copy link

i added my comment over in the new repo.

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

2 participants