@TobiSGD: In my opinion localizing the installer in one the highest priorities.
The reason is that for people who can't read English and with no outside help, the obstacle of not understanding what is displayed on the screen is near impossible to overcome, so probably they won't try Slackware, let alone adopt it.
Having said that, I understand your objections and will try to address it.
Let's keep in mind that if we use the 'gettext' method & tools for internationalization and localization, which is the most widely used, the language used to display the messages will depend on the value of $LANG.
(a) If set to en_US or en_US.utf8 the messages will be displayed in American English.
(b) if set to another supported locale and a translation in the corresponding language exist for some message, it will be displayed in that language.
(c) in any other case the 'original' message (in American English) will be displayed as a fall back.
You can check that with the tiny 'working example' I wrote to further present the internationalization and localization processes (see the PS I added at the end of the first post of this thread).
So if you want to help someone and need to see a message in English for that, just ask the OP to provisionally set $LANG to en_US then post the message in English.
The quality of translations will all depend on the rules we will set up and enforce. We will just need to be exacting and refuse incomplete or badly reviewed translations.
About the work involved for PV and the core team, I can't but agree that it should be lessen to a minimum.
It is very possible that the Slackware maintainer & contributors be only involved, if it is their wish:
(1) concerning initial internationalization, in reviewing for acceptation changes in scripts proposed by trusted individuals to ease further localization work and spot or mark the messages to be translated
(2) concerning localization, in including or updating the messages catalogs in the distribution
(3) concerning maintenance (mainly whilst cooking current) in writing the new scripts or changes in existing ones in an 'internationalized' way or delegating that task; then making aware the translation team that they should update the message catalogs.
They won't have to be involved in the translation work in any other way if that is not their will.
The scripts themselves will *not* be translated if we use the 'gettext' method & tools.
This stands as well for the main Slackware tools. For instance 'pkgtool', 'installpkg' and 'removepkg' are included in the installer so at least for that reason they will need to be localized.
In the same vein, 'setconsolefont' should be localized, though not included in the installer, because it will be executed during configuration after packages' installation.
As a side not some other files of the distribution could be localized using another method, for instance with one package par language as in the /kdei series.
About the translations in SlackDocs: hopefully they are under way. We could even get some synergy between the two projects if some editors of documentation in foreign languages would like to participate to the localization effort of Slackware too, and conversely in the future.
Oh, and I almost forgot: I hope it's not to late to congratulate you for beeing recently introduced to the 10k club
@Feyfre: Thanks for the link, I downloaded an iso of 'deepstyle'.
The installer is based on Slackware's with some files added. I noticed that the installation scripts are internationalized using an alternate method (not using 'gettext').
@all about UTF-8: we seem to agree that generalization of its usage is really needed, so it deserves a dedicated effort. Possibly as a sub-project?