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

[Nicolas Mailhot]

I honestly think the only scalable solution is in-package translation. It
does not have to be in the spec file, could be in another set of files in
the package, but it can not be pushed out of the package.

All the solutions that push this info out of packages rely on some central
authority, either at the distribution level (specspo) or at the repository
level (yum metadata). These approaches try very hard to ignore the
reality. The reality is people download and assemble packages by all the
ways imaginable, burn them on CDs, create package archive/mirrors, rebuild
tweaked SRPMS, sometimes index them with createrepo at last but the basic
unit is the package and anything not included in the package itself is
bound to be lost.

I know it's an unpalatable reality since life would be so much easier for
translators if they could ignore the distribution problem. Ignore it
however and you'll hit the same dead-end as specspo

What would be possible for example would be to attach a translation to an
existing package like you do for signatures. However great care should be
taken so when you rebuild the package the translation is not lost (ie rpm
-Uvh x.src.rpm adds the translation to SOURCES). This would permit
incremental translation, without breaking the package unit distribution
paradigm.

Regards,

-- 
Nicolas Mailhot