Setting the correct locale is only one aspect of the user interface. It ensures that you have the correct numbering scheme for time, calendar, etc., though timezone is needed to get the correct time of day. The correct locale will also ensure that you have the correct code set and fonts for using translated text. However, it is the translated text that you are likely missing. I am not sure if antiX has been completely localized in any languages. If it has, I am not aware of them. What you do is that you take the default locale, the"C" locale, and for every message in the system message catalog, you translate these to the language used in your locale and populate the localized messages in the message catalog to see the results, set your locale and then the translations are visible.

thanx Brian, will look into that.
Debian Etch btw has almost complete language support without such contortions.
Ubuntu is well translated in the 'big' desktop environments, if you run a slim version you have to
enable debian lenny repos and install the locales-all package, why that helps I have no idea.

coyotito wrote:thanx Brian, will look into that.
Debian Etch btw has almost complete language support without such contortions.
Ubuntu is well translated in the 'big' desktop environments, if you run a slim version you have to
enable debian lenny repos and install the locales-all package, why that helps I have no idea.

This is a small operation here. There is one primary integrator, anticapitalista. He originally took the code, with permission, from SimplyMEPIS, removed the desktop environment and replaced it with two small window managers. He also replaced several applications with smaller equivalents. The work was so well done and so appreciated that it got a spot on the MEPIS Lovers forum, then other people from the community began to help anti out with artwork, tools, testing, and suggestions.

I am sure that anti is open to feedback and help should you or others want to get involved in localization of antiX.

I am not a language translator, but I was involved in UNIX system localization of the Common Desktop Environment (CDE) in the mid 1990s. The idea of a locale is to provide a code set that supports the language, then include the specific fonts, characters, number tables, and other attributes specific to the language as part of the locale definition. From there, translate the English"C" locale message catalog text files into the specific language, then run the catalog translator on them and store the translated catalogs in the message catalog directory specific to the locale and the application. While I cannot do language translation, I can consult on the techniques used to do localization if needed.

What I was after here was how to successfully insert the code from /etc/init.d/gdm into /etc/init.d/slim
in order to make slim capable of setting locale, see link in first post.

-->needs to be done so that slim starts at boot without syntax error problems.. when I try to do it I get it wrong and the init script
does not work