[translations] Empty Strings

[Gabor Hojtsy]

Martin Stadler wrote:
>> IMHO you should never import contrib translations in "override" mode.
> I try to avoid it, too, but wouldn't that mean you can't update any  
> contrib module's translation ever? That doesn't appear acceptable to  
> me...
> 
>> The autoimport feature built into Drupal 6 also always imports in  
>> "keep"
>> mode, but it still does delete stuff in your database if you  
>> "override"
>> it with an empty string. I am not sure overriding with an empty string
>> is a good idea, and with Drupal 6, it also means deletion of the
>> database entry.
> Is there any reason why empty strings can override existing strings?  
> I can imagine the rare case that I decide to not translate a certain  
> string in a later version of my translation and want to update my old  
> one. In this special case I could translate this string just with the  
> English original to avoid conflicts.
> How can I maintain a translation file (.po)? There will be empty  
> string until the translation is perfect which is not a usual case in  
> an open source community. And still, I wanr people to be able to  
> update the translation to the latest version without deleting other's  
> translations.

Last time I checked Gerhard Killesreiter was strongly against removing 
this "feature" to delete stuff when you import empty translations for 
it. I am not sure this is a good "feature", so I'll try to hook up with 
him and discuss.

Gabor