[haiku-i18n] Re: One language as fallback/template for another

  • From: Adrien Destugues <pulkomandy@xxxxxxxxxxxxxxxxx>
  • To: haiku-i18n@xxxxxxxxxxxxx
  • Date: Thu, 29 Dec 2011 19:31:58 +0100

Le 28/12/2011 23:18, Rimas Kudelis a écrit :
 I find this a strange feature: you leave something empty and rely on
 another translator not doing something you don't like.
I think he might be right. Inheritance is a good feature, but asking the localizer of ll-CC not to copy-paste a good translation from ll is risky at least. What if ll changes their localization after ll-CC chooses to inherit it? What if the new version doesn't really suit ll-CC anymore?

With proper support in Pootle, this would mark the string as needing validation again in the child language. An alternative would be to generate the common catalog from the common strings in all the childs. But I think this will likely mean duplicate work most of the time...

I guess it depends on the language too. For example, fr_BE is quite close to fr_FR, while pt_PT and pt_BR are different in more ways.

--
Adrien.

Other related posts: