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

Update spanish translation #4697

Merged
merged 1 commit into from Oct 12, 2016

Conversation

Projects
None yet
2 participants
@federicobond
Contributor

federicobond commented Oct 9, 2016

No description provided.

@benfry benfry merged commit a613509 into processing:master Oct 12, 2016

@benfry

This comment has been minimized.

Show comment
Hide comment
@benfry

benfry Oct 12, 2016

Member

Thanks for the updates; much appreciated.

Member

benfry commented Oct 12, 2016

Thanks for the updates; much appreciated.

@federicobond

This comment has been minimized.

Show comment
Hide comment
@federicobond

federicobond Oct 12, 2016

Contributor

@benfry You can direct any translators to this script I made a couple of years ago to find missing translations for their language. It's not without its flaws but ended up being very useful for this kind of work.

https://gist.github.com/federicobond/741d5c7df61191e13408

If you call it like this:

./missing.sh

It will show strings that are missing from the default English properties file (indented lines are those found in the .properties file but not in the codebase)

If you call it with a language code as an argument:

./missing.sh es

It will compare the keys for that language against the keys in the default language .properties file. Again, the behavior with regards to indented lines is similar: those lines appear in the corresponding language file but were removed from the default one.

Contributor

federicobond commented Oct 12, 2016

@benfry You can direct any translators to this script I made a couple of years ago to find missing translations for their language. It's not without its flaws but ended up being very useful for this kind of work.

https://gist.github.com/federicobond/741d5c7df61191e13408

If you call it like this:

./missing.sh

It will show strings that are missing from the default English properties file (indented lines are those found in the .properties file but not in the codebase)

If you call it with a language code as an argument:

./missing.sh es

It will compare the keys for that language against the keys in the default language .properties file. Again, the behavior with regards to indented lines is similar: those lines appear in the corresponding language file but were removed from the default one.

@federicobond federicobond deleted the federicobond:es-translation branch Oct 12, 2016

@benfry

This comment has been minimized.

Show comment
Hide comment
@benfry

benfry Oct 12, 2016

Member

That's awesome! Actually, would you be interested in writing up a wiki page to introduce people to how to do the translations? And you could provide a link (or simply include) this as well. You've really been spearheading the translation process for us, and folks would benefit from your explanation.

Member

benfry commented Oct 12, 2016

That's awesome! Actually, would you be interested in writing up a wiki page to introduce people to how to do the translations? And you could provide a link (or simply include) this as well. You've really been spearheading the translation process for us, and folks would benefit from your explanation.

@federicobond

This comment has been minimized.

Show comment
Hide comment
@federicobond

federicobond Oct 12, 2016

Contributor

Sure! I could expand this one.

Contributor

federicobond commented Oct 12, 2016

Sure! I could expand this one.

@benfry

This comment has been minimized.

Show comment
Hide comment
@benfry

benfry Oct 13, 2016

Member

Yes, please!

Member

benfry commented Oct 13, 2016

Yes, please!

@federicobond

This comment has been minimized.

Show comment
Hide comment
@federicobond

federicobond Oct 13, 2016

Contributor

Done. I don't have more time to elaborate on it, but I am happy to respond to any feedback.

Contributor

federicobond commented Oct 13, 2016

Done. I don't have more time to elaborate on it, but I am happy to respond to any feedback.

@benfry

This comment has been minimized.

Show comment
Hide comment
@benfry

benfry Oct 18, 2016

Member

Excellent! Thanks once again for your help.

Member

benfry commented Oct 18, 2016

Excellent! Thanks once again for your help.

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