Hi all,
I wish all users be able to install and use Slackware in their native languages.
I believe that could help in expanding Slackware's user base, as do the Slackware Documentation Project
Some people did try to translate Slackware in their native language already.
But in my opinion it would be better not to build a Babel tower again.
In other words I would prefer to have one Slackware usable everywhere than derivatives or versions specifics to one country or language.
That would mean three steps:
(A) Internationalize (part of) Slackware, at least the installer, that is to say modify it in such a way that all the texts it displays could easily be translated in several languages (localized).
(B) Localize it in as many languages as teams of volunteers to do that will appear.
(C) Provide maintenance to follow any changes in Slackware.
For this to succeed, I think following requirements should be set up and (hopefully) met.
(1) The project should be acceptable by Patrick J. Volkerding and if possible by other authors or maintainers of tools written specifically for Slackware. This will require at least that:
(a) It will not require from PV an amount of additional work that he {c,w}ouldn't accept.
(b) We can credibly guarantee that the internationalization then localization do not introduce bugs and do not result in any significant inconvenience for present users, in other words that the level of quality and stability provided by Slackware will not decrease as a consequence of the project.
(2) The ultimate scope of the project will be: "everything specific to Slackware and visible by an end-user". For instance this would include what the user sees on the screen at time of installation or using Slackware tools afterwards, but probably not comments in Slackware scripts. This scope will have to be be filled progressively, so steps and milestones will have to be set up.
(3) Internationalization of (parts of) the scope should be completed before any localization effort in the same (part of the) scope begins.
(4) Internationalization & Localization of upstream software not specific to Slackware will not be included in the scope, in the spirit of shipping as less modified software as possible, in Slackware's tradition. This do not preclude an effort to provide users help and guidance to find, install and configure anything that could help them use their preferred language in as many applications as possible.
(5) The work to be done will be organized, coordinated, allocated and verified in such a way that previous requirements be fulfilled, whilst encouraging people to participate. In particular specific knowledge or know-how will be required depending on the kind of task to be performed and progress tracking in both internationalization and localization will be provided.
Internationalizing then localizing software is not new. There are existing tools to help us doing that, for instance 'gettext', 'poedit" and 'lokalize' already included in Slackware, which can be used to internationalize and localize shell scripts.
And we can benefit or experience of others, for instance about setting up an organization and associated processes and teams, defining the roles and responsibilities.
So are we ready to launch the Slackware Internationalization Project?
If I get enough positive feedback I will first set up a mailing list and maybe other tools so we can share ideas and experiences.
I already began to study the feasibility of internationalizing then localizing the installer, the goal being to have something practical and constructive to propose.
I am eager to hear from all interested Slackers.
PS To help clarify a bit the vocabulary and illustrate the process of internationalization then localization I wrote a small demo.
To run it, download in your home directory following files:
example.sh
example.po
Just read example.sh and run the demo typing 'sh example.sh'.