molch.b at googlemail.com
Tue Oct 26 02:28:53 CEST 2010
I think we talking about something which is not as said before,
ppartly due to my own wrong descrition of the problem.
What kind of description are we looking for? A descrition that tells
the user what the package does. Simple.
What do we have?
- descriptions as part of the packages? Yes.
- descriptions visible in rpmdrake? Yes.
Both in English only (with very few exceptions), so here the
translators are needed and a way for them to do their work, to feed
back the translations to whom it concerns, a routine which displays
the description in rpmdrake in the language of the installed system.
If there is no translation in that language it should show the english
What we do not have:
In the individual package selection at system installation all these
descriptions are missing completely.
If somebody wants to pimp his installation and searches for
applications to be installed at system installation time all he sees
is the category (example: office), the package name and version and
then a mere "useful" or "important" or "comfortable.", etc. Nobody
tells him (examples:) what bvi is and how should he know what
"alexandria" does (is it an egyptian font?). This is where the
descriptions are missing completely although they are available in the
So, here the task is to include the descriptions in the installer and
providing the translations as in rpmdrake.
As we can see most parts of the package description issue are not
related to packagers, rather to developpers of rpmdrake and the
installer - and to the translators, of course.
More information about the Mageia-discuss