| 1 | | I agree with @cvedovini. It's a sad situation for software development if you can't accept a new feature because it doesn't solve ''every'' situation, such as the case of ug_CN -> zh_CN. It should be understood that a language file with no sub-domain (regional variant) specification is to be used as the most neutral, generic translation. So that language-domain-es.mo is good for Colombian, Peninsular or Rioplatense Spanish. So that we don't need t |
| | 1 | I agree with @cvedovini. It's a sad situation for software development if you can't accept a new feature because it doesn't solve ''every'' situation, such as the case of ug_CN -> zh_CN. It should be understood that a language file with no sub-domain (regional variant) specification is to be used as the most neutral, generic translation. So that language-domain-es.mo is good for Colombian, Peninsular or Rioplatense Spanish. So that we don't need two copies of language-domain-sv for Swedish from Sweden and Swedish from Finland. So that people who are upset by an unfamiliar term in the generic translation are welcome to contribute their own regional variant. So that we can offer the users an understandable, communicable experience in a familiar language, instead of falling back to English when the user is Swiss-German and not German-German. |