Hi Hans-Günter,
> Meanwhile I succeeded in transfering this package to tank.slitaz.org.
Yes, people.slitaz.org is good place for your packages.
> All messages files in SliTaz 5 seem to be contained in packages locale-language.
No, not all, of course. locale-* contains translations only for selected packages - packages installed on the LiveCD. You can find a list here: http://cook.slitaz.org/next/slitaz-i18n/stuff/locale-pack.conf (AFAIK it's identical to that from SliTaz Cooking).
> But consider, that these language packages may become very large and for most users contain many useless languages.
Yes, I know, I know. These's no good solution yet. As far as we use package manager [to manage our packages] we should use packages. These packages may contain no translations (to be smaller), or all available translations (big, I see no point in it), or selected set of translations (maybe the best solution). Look the link again - SliTaz provides support for 32 locales/languages, and only these locales will be packed into packages "*-lang" in the SliTaz Next (since now).
Packing each translation into its own package isn't the solution at all.
Another sort of solution is to make tool which will download translations from the cook.slitaz.org for you based on your locale and on your packages list. I created this tool few years ago and it is called tramis (tramys, tramys-client, tramys-server) but development is discontinued. And one small "cons" for this solution: package manager don't know anything about these external files...
> This might be contrary to the SliTaz principle: keep it small and simple.
All things in this world are relative :-)
> ... and found it marvellous ... you were no developer ...
Thank you!
And I still don't learned any programmatical language other than Shell script :-)
Am I a developer at all? :-) Well, maybe.
By the way, found something interesting about SliTaz a hour ago: click.