7 Feb
2014
7 Feb
'14
5:09 p.m.
Hello
Although I foresee the counterarguments that will be provided in this regard, I want to
make the following comment.
The general response of any non-English-speaking low/medium level user, but usually
unwelcome in English-speaking dev lists, is that translations should be in the main
package or be a one of its dependences or at least a "recommend" (in the Debian
package system jargon), because non-English-speaking novices find very frustrating to want
to install a software (p. eg. k3b or kaffeine), find and install the package, and find it
only in English - however much we may seem very normal to have to look for a additional
package xxx-i18n or xxx-l10n or xxx-i18n-es or xxx-l10n-es (as Spanish example).
As I comment and report as many bugs, should be given much more importance to translations
in TDE. The 1232 bug is an example of how the lack of translation can make a desktop
environment as unusable for non-English-speaking users.
Cheer and thanks for all
--------------------------------------------------------------------------------
Miscelánea Natural http://miscelaneanatural.org
Anfibios de Asturias http://anfibiosdeasturias.org
Actividades de informática con software libre
http://eventoslibresasturias.drupalgardens.com
________________________________
De: Darrell Anderson <darrella(a)hushmail.com>
Para: Trinity Dev List <trinity-devel(a)lists.pearsoncomputing.net>
Enviado: Jueves 6 de febrero de 2014 21:36
Asunto: [trinity-devel] i18n locale packages
All,
We have an inconsistent mixed delivery of i18n files. Many locales
are packaged with tde-i18n; some are packaged in a smaller i18n
package, such as gwenview, k3b, and koffice; while others are
packages as part of the parent app. That last group includes the
following:
amarok
digikam
filelight
kbiff
kdbg
kdiff3
kile
kipi-plugins
kmplayer
knights
knutclient
konversation
krecipes
krusader
kshowmail
kshutdown
ksquirrel
kvpnc
rosegarden
showfoto
tdepowersave
tdesvn
tellico
Of this latter group, only a few locales are supported in each of
the packages.
With the three packages that include all i18n files: gwenview, k3b,
and koffice, a challenge is gwenview and k3b is an all or nothing
installation. Conversely, like tde-18n, koffice-i18n can be
compiled as separate locale packages.
tde-i18n has become a monster module, just too large to deal with.
That module should be split into smaller locale modules. Then the
packages listed above, as well as gwenview, k3b, and koffice, could
be merged into each respective locale module.
Comments appreciated.
Darrell
---------------------------------------------------------------------
To unsubscribe, e-mail: trinity-devel-unsubscribe(a)lists.pearsoncomputing.net
For additional commands, e-mail: trinity-devel-help(a)lists.pearsoncomputing.net
Read list messages on the web archive: http://trinity-devel.pearsoncomputing.net/
Please remember not to top-post:
http://trinity.pearsoncomputing.net/mailing_lists/#top-posting