Skip to content
This repository has been archived by the owner on May 16, 2019. It is now read-only.

Suggestion: Country and currency names in separate translation file? #1763

Open
pryds opened this issue Aug 11, 2016 · 4 comments
Open

Suggestion: Country and currency names in separate translation file? #1763

pryds opened this issue Aug 11, 2016 · 4 comments

Comments

@pryds
Copy link
Contributor

pryds commented Aug 11, 2016

Just a suggestion that might ease things a bit for new translators.

Country and currency names take up a lot of strings and might "drown" other strings and make translating OpenBazaar into a new language seem like an overwhelming job, while these strings probably have slightly less priority to get done.

So, would it be an idea to funnel country and currency names into a separate file and thereby a separate project resource on Transifex?

@rmisio
Copy link
Collaborator

rmisio commented Aug 11, 2016

This is something that we did want to do, but didn't think it was possible in Transifex to have multiple files per language.

Are we wrong and it is indeed do-able?

@jjeffryes
Copy link
Contributor

I think we can make multiple resources in Transifex, each would have it's own translations.

Then we could extend polyglot with all the files for each language, instead of just one.

We'd have to change some things and it'd take some work to set up, but I think it would be possible.

@pryds
Copy link
Contributor Author

pryds commented Aug 11, 2016

Using Transifex terms, each organisation may have several projects (which I think is not necessary for OpenBazaar at this moment -- maybe if something like a mobile app is introduced), and each project may have several resources (aka files).

Projects (and maybecresources too?) may have each their translation team, or they may share a common translation team -- a translation team consisting of all languages that the team in question may translate into. Each translator may be a part of one or more languages in one or more teams.

One thing I'm not sure about, though, is whether moving existing strings to another resource (file) will preserve existing translations of those strings, and if not, how easy it would be to transfer those translations to a new resource.

@jjeffryes
Copy link
Contributor

I believe we can upload pre-made translations, my guess is if we cut out sections of the main file and upload them as individual license files, transifex will recognize the translations.

So as long as everything in the json files matches, in theory the tranlations will carry over to the new resource.

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