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

[Miloslav Trmac]

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.
As a translator, I don't think this is what I want.
1) We already have infrastructure to show translation status, without
   explicit notification.  Explicit notification would just result in
   a lot of daily emails.
All that is necessary is regular (daily/weekly) rebuild of the list of
strings to translate, and a regular incorrporation of translated
messages to the repository (in whatever form).

2) No, I certainly don't want to handle 1237 separate "translation
   packages" in 1237 separate files.
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.
	Mirek