I think that:
- you can use this topic for communications in place of a forum and a mailing list (seems to me like an overhead);
- for the wiki, a page on docs.slackware.com (seems to me like the proper place, most of the people working on this stuff already have an account there).

as I'm already doing this post, for this time if it's ok for you I'll avoid sending you a pm or an email for confirming my partecipation (for the italian translation).

I would love to help, but if the timeline is very tight I might not be up to it.

I could do/help with Greek - el_GR (gr.map), but since nobody has volunteered for Spanish yet (that I'm pretty fluent in) and it's a much more widely spoken language than my native tongue, I could volunteer to do/help with es_ES instead

OK, let's begin so.

Why not if slackdocs's admins agree. I'll write them about that.

That's OK with me, thanks in advance for your participation. Check next post for how to proceed.

Let's start - Testers and translators wanted.
 

OK, the bar is now open.

Just go there.

Anyone is welcome to try and test.

ponce will do Italian translation, I'm waiting (confirmation from) volunteers for other languages.

Translators, please check the requirements in post #14

If you have specific (personal) questions, my email is in the README.

For all other questions, please post in this thread.

PS we have now a domain name: slint.fr

First, thanks. There is no timeline. In the pure Slackware tradition, each translation will be included in the installer when it will be ready.

That being said, work can be shared among several translators, provided they all agree (see post # 14).

Either one, as you prefer.
If there are other volunteers for one of these languages, you could consult with them.
Maybe wait a few days before you decide and during that time familiarize yourself with the stuff here.

The slint project has got a home page
 

It's here :cool:

I volunteer for the Brazilian Portuguese translation.

Locale: pt_BR
Kernel keymap: br-abnt2
X keyboard layout: br

Thanks gabrielmagno. And thanks to sycamorex (pl_PL) and franzen (de_DE).

Also, I intend to list the translators on slint's home page.

So please each translator let me know how you want to be listed (with a pseudo or your full name).

This will also serve to indicate for which languages there is no translator yet.

Reminder: seeing that there is already a translator for a given language do not prevent other folks to volunteer for it. We will need reviewers, and work can be shared. The only thing I wouldn't want to end up with is receive more than one po file per language, so if there are several translators I demand that they work as a team. ;)

Hmm...
edit:
And even if I edit the .md5 file to delete "home/didier/", the checksum doesn't match.

Thanks for noticing. I made an error in the script which pack the tarball and write the md5 file, which should be corrected now.

As stated earlier, I will do the nl_NL translation (nl.map console keymap). What do you intend to do with partial translations? There are over 1000 text strings to translate, that will take a long while to complete. Do you want to publish partial translations so that others can work on them too (to be coordinated by the "lead translator" for a language)?

Eric

Thanks. In addition, please tell which X keyboard layout (and X keyboard variant, if any) you use. I ask that question because at end of 'setup' the internationalized installer proposes the user to keep in the installed system not only the LANG and kbd settings used during installation, but also to make these X settings (if the X server has been installed, of course).

I really don't know.
I think of three possibilities:
(1) Let translators for a given language organize themselves to share the PO file and the work.
(2) Use a web platform like transifex (used by Salix) or Pootle (already suggested by Willy). This would be only to exchange files among the teams, tough, as the translation should be done using a specialized PO editor.
(3) Host the files on slint.fr (or elsewhere ?), allowing translators to upload them themselves.

I'd tend to favor solution (3), which seems me simpler than (2) and has the advantage over (1) to give everyone some visibility on the work in progress, but all remarks and suggestions are welcome.

In any case, translation teams will have to work as teams.

I don't use an X.Org configuration, I let my Desktop Environment handle the keyboard layout. But if you need it, I guess this will do it:
Option "XkbLayout" "nl"
Option "XkbVariant ""

If a team of translators has to email partially translated PO files back and forth, that will be hell. You'll probably lose your translators in no time. You need to think about setting up a project for this in Pootle or Transifex, and not depend on translators to do that independently.

Eric

This sounds like fun :)
I'm a native Spanish speaker, so I can help with that.
I use es_UY.utf8 as locale, with "es" as keyboard layout for both console and desktop.

Thanks. Out of curiosity, are there many differences between es_ES and es_UY?

@Alien BOB: I will investigate further theses tools (transifex and pootle) and other possibilities.

Both are python/django based and I'll check if I can install that (I have shared hosting), or if we would need to have PO files hosted on the transifex platform or elsewhere.