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

Add support for a Translation file to extend another language (eg. Spanish Argentina extends spanish) #4983

Open
mattab opened this issue Apr 12, 2014 · 1 comment
Labels
Task Indicates an issue is neither a feature nor a bug and it's purely a "technical" change.

Comments

@mattab
Copy link
Member

mattab commented Apr 12, 2014

How do we make it easy to add support for language locales such as es_AR or any other?

Maybe best way would be to implement a new mechanism where the es-ar would "inherit" the spanish, so that you would only modify the strings that are different. Otherwise it will lead to a lot of duplication of strings which in the long run will cause more work to translators.

think of future different locales for one single language, i.e., en-AU, en-GB, en-IN, en-US, en-ZA, or es-AR, es-CL, es-ES, es-MX. I mean, if you could implement a mechanism where an already fully completed locale could share its strings with other locales in the same language, it'd save a lot of work for everybody and locale releases would be much quickly available for everyone.

Goal:

  • Limit work to be done by translators so they automatically reuse existing translations for their language
  • Let translators of a locale override only the strings that change in their locale

Questions

  • how do we inherit a language from another?
  • How would it work with oTrance?
@mattab
Copy link
Member Author

mattab commented Apr 12, 2014

Could you explain why we should add the es-ar ? what are the differences between spanish and spanish argentina?

So this is the story: if one would be somebody that doesn't understand a bit about Spanish language stuff, I'd begin telling that buddy there's basically 2 different Spanish "branches", let's say The Spaniard and the Latin American one. Spanish (Spain) has a different treatment, as in speech as in texts. This different treatment is bigger in informal ways, as in formal modes differences are less. So, I'm assuming you ask people to localize Piwik in an informal/familiar way, not pure slang nor totally serious & polite, right? If that's correct, so, yes, differences between Europe's Spanish & Latin America's Spanish are big. That's not the end of story though.

Now let's zoom in Spanish speaker Latin America only. There's a few differences between Mexico's Spanish and all the way down till Bolivia. However when you are in Argentina, all the Spanish you have learned is less than useless. Spanish (Argentina) has a different way of conjugating verbs and subject pronouns change as well [t & vosotros are Spanish (Spain) for you second person, singular & plural pronouns respectively, while vos & ustedes are Spanish (Argentina) for you second person, singular & plural pronouns respectively. From that point on everything changes, as actions have a different spelling. For instance: You think is Tu piensas in Spain & most Latin American countries, but in Argentina it's Vos penss. This is just a silly example diffs are deeper: Spanish (Argentina) has a lot of slang within itself. And this is something inescapable, it's part of the Argentine Spanish and its own roots. You will want to have a look at Che, boludo! book if interested to know more about Argentina's Spanish.

@mattab mattab added this to the 2.x - The Great Piwik 2.x Backlog milestone Jul 8, 2014
@mattab mattab modified the milestones: Mid term, Long term Oct 11, 2014
@mattab mattab modified the milestones: Long term, Mid term Dec 23, 2015
@mattab mattab modified the milestones: Long term, Mid term Dec 5, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Task Indicates an issue is neither a feature nor a bug and it's purely a "technical" change.
Projects
None yet
Development

No branches or pull requests

1 participant