How to simplify the process of adding multilingual %descriptions to rpm spec?

[Miloslav Trmac]

Toshio Kuratomi wrote:
> On Tue, 2005-11-15 at 18:36 +0100, Miloslav Trmac wrote:
> 
>>Toshio Kuratomi wrote:
>>
>>>Translator Goals:
>>>1) Notification of package string changes.
>>>2) Ability to own a package-translation similar to how other packagers
>>>own a package.
>>

>>2) No, I certainly don't want to handle 1237 separate "translation
>>   packages" in 1237 separate files.you don't want me
>>The specspo model of a single file actually suits translators quite well
>>(e.g. it allows automated translation matching on package renames).
>>Maybe we could split the large .po file to allow better collaboration,
>>e.g. to 26 .po files, selecting packages by the first letter of their name.
> 
> #2 doesn't specify the backend.  #2 specifies that if you are
> translating package foo for language hungarian, then you don't want me
> to come in and retranslate it.  Do you disagree with this?
The general idea of "owning" the translation is correct, but separating
work per-package is really too much overhead.  "Owning" a block of
packages (on the order of 100 packages, or even more) would be OK.
	Mirek