@Didier Spaier,
seems to me, SLINT's /sbin/lilocinfig has cosmetic bug at line 374:Variable DEFAULT is set at line 111 to value This is the dialog parameter to select list item MBR, but it goes into dialog tiltle as:instead of dialog option.

This may be as

That's right indeed, thanks for noticing this bug Serg. It will be fixed in next update this week.

I will also announce this week the plans for version 14.2, and publish a POT file for the few additional messages to be translated in that version.

Updated stuff:

• slint packages are available at:
  http://slint.fr/packages/
  for versions 13.37, 14.0 and 14.1
• "small" slint installers are available at:
  http://slint.fr/installers
  or versions 13.37, 14.0 and 14.1
• "big" installers are available at:
  http://sourceforge.net/projects/slint/files/14.1/
  for version 14.1.4 (32 and 64-bit)

All updated packages and installers supersede previously released ones of the same version and architecture.

Al updates include:

• Bug fixes (including that found by Serg Bormant)
• Norwegian translations and man pages carefully reviewed by Dan-Simon Myrland himself (peer review still wished)
• Persian man pages and associated documentation (thanks to Hosein Sadeqzade)

Also, the repository http://slint.fr/packages/ has been restructured:

Thanks to giogio aka Giovanni Sora, our website now speaks Interlingua, see http://slint.fr/ia/slint.html

Other news coming soon.

Preparation for 14.2
 

I have uploaded a new resource on Transifex: slint-14.2.

Tomorrow I will upload PO files for all currently available complete translations, already edited to minimize the work to be done by our translators. This way only a few messages will need your attention, be they added or to be reviewed: this shouldn't need more than one hour or so per locale.

Of course the POT file will be updated if/when Pat decides to make changes before the release of Slackware 14.2.

One noticeable change (already made in the PO files) in 14.2 is that he word Slackware won't appear anywhere but where it should, i.e. in the relevant copyright notices, the Slackware tools themselves and in the expression "Slackware package" to mean the structure, not the content.

This change is made to avoid any trademark infringement, as discussed previously.

By the way, I am calling for artists to propose a Slint logo that will replace the Slackware logo shown in lilo's greeting screen.

So, Slint 14.2 will officially be a distribution on its own, of course based on and as close as possible to Slackware.

We will ship in the distribution only a few additional packages mainly in the aim to make it accessible as much as we can: first and foremost to folks who are not at ease with the English language, but also to disabled people, for instance.

Yet another Slackware derivative is not what I dreamed of, but I don't want that the hard work of our volunteers be lost.

I am hoping that some derivatives can make use of our products, and more generally want to encourage exchanges and cooperation in Slackland.

In that aim we will try to ease adding to Slint systems by their users software provided by trusted individuals and other distributions based on Slackware, under the condition that these software be fully compatible with Slackware 14.2 with a minimum of added dependencies beyond what will be shipped in a full Slackware installation (or maybe with these dependencies also provided in a bundle or module). Ideas to do that are welcome, I intend to consult on this topic with other distributions maintainers and packages providers.

To get all that done we probably will need some time after the official release of Slackware 14.2 to release Slint 14.2, but we will follow the Slackware path releasing it "when it will be ready".

Thanks to all for your cooperation, have fun.

So the PO files are uploaded. Thanks to Eric and Ingemar who already did the job.

Caveat: for an unknown reason I couldn't get to upload the Polish PO file as Polish (Poland). Out of ideas I uploaded it as Chinese. So please Polish translators kindly go there or download it from there. I will request support from Transifex but meanwhile you can go ahead.

Also, Darren 'Tadgy' Austin kindly accepted to mirror us and already created a 'slint' storage area and directory in slackware.uk. This will serve from Slint current onward, the older files remaining where they are currently.

There is nothing there yet, I will need some days to set up the tree.

Will do, Didier.

I am going to update the POT file for slint-14.2 in a few minutes.

This is because I forgot to include the messages from the script SeTPROMPThelp that internationalizes the text displayed when you choose "Help" in the dialog to select the installation mode (full, terse, expert, newbie etc.).

For the 100% complete translations (fr_FR, nl_NL, sv_SE) this will result in a tentative loss of this script's translations but don't worry: I have saved them and will restore them myself as soon as the merge will occur.

EDIT: All done.
___

I have also restructured the stuff that I use to manage the translations, build the packages and the installers.

I make this public for those interested and also because translators can use that to make themselves an installer including their work, to see it as displayed "live". This stuff is available here: http://www.slint.fr/testing/slint-current

Of course this is just the beginning of the transition, stay tuned.

I always dreamt in having a Linux distro completely translated to Latin!

I would tend to say: if you volunteer to translate to Latin, welcome.

But there is a hurdle: the way we manage translations in Slint we need a locale for each language with an UTF-8 encoding. But unfortunately glibc ships no locale for the Latin language, so you'd have to first write the needed definitions (as those found in /usr/share/i18n/<locale>) then make them accepted by GNU libc. We had a similar issue for Cheyenne IIRC.

I take this opportunity to update the information about upcoming Slint 14.2, that will be a wholly distribution.

• In the ISOs we will ship all Slackware packages, a very few of them modified for internationalization or to ship other versions or builds (like packages including internationalized scripts and translated man pages), and strongly encourage a full installation.
• We will also include a few additional packages, like for xorriso that we use to write the ISOs and stuff consistent with our aim of accessibility. We will also ship spkg, that will be used in the installer to speed-up a bit the installation (only in Full and Terse modes).
• Our repository will store all modified and additional packages and of course their source files. Our packages (modified from Slackware's ones or additional) will include dependency information to be usable by other distributions. We will also include an update notifier, to ease handle updates showing in Slackware's Changelogs, for instance.
• To ease installation of packages coming from fully compatible distributions, we will include slapt-get/gslapt with a pre-configured slapt-getrc (I have still to check netpkg, though). Roughly, the default priorities will be set to 1) Slint, 2) Slackware, 3) Other fully compatible distributions/repositories that include dependency information usable by slapt-get. This includes at least some of Eric Hameleers' repositories IIRC.
• We will also try to ease building and/or installation of packages for which SlackBuilds are available @ SBo or elsewhere. I have yet to compare features of some tools (sbopkg vs slapt-src/sourcery mostly).
• Of course Slint will include a polyglot installer, but we are not alone: probably two other distributions based on Slackware will get one. The final decision has to be made by their respective maintainers but at least there is no technical hurdle, and I am confident that most of the work done by the Slint translators (huge thanks to them!) can be reused considering the results of preliminary tests on prototypes.

Comments are welcome.

Please complete your translations for upcoming Slint-14.2
 

I have just uploaded on Transifex a "tentatively definitive" POT file for slint-14.2, after having replaced all mentions of slackware, Slackware, slack and SLACKWARE where applicable in the scripts from which the messages to be translated are gathered.

I have also taken care of doing the corresponding replacement in the PO files, also uploaded on Transifex:
https://www.transifex.com/didier_spa...int/slint-142/

Some translations still lack the translations or revision of a very few new messages: Polish, Portuguese (Brazil), Russian, Spanish (Latin America), Turkish, Ukrainian.

Please dear translators complete them as soon as possible, so that I can publish a first Slint-14.2-alpha ISO, and thanks to those who already did that (you know who you are).

Italian being meanwhile reviewed, I will do the aforementioned changes in its PO file being currently under review when its revision will be completed, no need to fully review again instead the file that I just uploaded.

Thanks in advance and have fun.

To avoid misunderstandings.
 

An email I received as a reaction to post #371 leads me to clarify my intentions concerning Slint.

I am sorry to rehash previous statements, but this post will inform readers who just came across this thread and didn't read my previous posts.

The fact that I removed most mentions of Slackware in the scripts and translations is in no way a mean to deny Slint's roots. I will continue to publicly acknowledge Slint as a distribution based on Slackware. Simply put, if there were no Slackware there would be no Slint.

I had to do these removals not to infringe Slackware's trademark, as I am not authorized to use the name Slackware in Slint that is another distribution.

I should have thought about that earlier but waited until I be sure that Slint products would not be incorporated in Slackware. I became really conscious of the issue after having read the posts #342 and #344 of this thread.

I am not the first to make such a move: for similar reasons Jean-Philippe Guillemin renamed Minislack as Zenwalk, and Paul Sherman renamed Absolute Slackware as Absolute.

But if anyone, and especially a Slint contributor, has any concern with this move please let me know either in this thread or by email.

It is also highly probable that at least part of the translations will also be used by other distributions based on Slackware. Again if that is a concern, let me know.

I see Slint as a complement to Slackware, nor as a competitor (which would be overly pretentious anyway): I hope that we can bring more synergy among Slackware and derivatives, and will continue to encourage Slint users to financially support Slackware.

Have fun,

Could you please elaborate a little bit more on that?

What distributions? How does that affects us (the translators)? Is my translation going to be "forked"? Does this "used by other distributions" means they will continue with their own translation based on our work, or do we simply continue contributing to Slint and they copy over whatever they need? When will this happen? I think the "why" of it is the only thing I understand right now.

Please excuse the questioning, I just want to understand what's going on.

Of course.

Salix, Slackel and probably Zenwalk.

For Salix, this has just been announced by George Vlahavas, aka gapan in this post. Slackel uses basically the same installer, the only difference being that Salix does not set a root user by default but uses sudo (incidentally both George and Dimitris Tzemos contributed to the Greek Slint translation).

About Zenwalk, Jean-Philippe Guillemin has yet to make a final decision.

It depends.

For Zenwalk, that has basically the same installer as Slackware, a few "sed s/Slint/Zenwalk/" in the scripts and PO files will do the trick. So in this case basically the Slint PO file could be used, just post-processed with sed.

Salix has a specific installer, that I already internationalized, "importing" some Slint scripts, internationalizing specific Salix scripts. I just built a POT file for the scripts included in it and merged the slint PO files against this POT file. For your translation (thanks for having completed it, by the way) and minus a lot of messages not needed in the Salix installer this leads to 254 messages translated, 62 fuzzy translations and 46 untranslated messages in the generated MO file. I think that George will set up a Transifex resource for this set of messages to have the translations completed (and possibly extended to more languages). Now that you make me think more closely about that, I see that even though this POT file includes messages extracted from scripts near identical in Slint and Salix, Salix and Slackel installers will probably need a "fork".

Some admin scripts are not modified by Salix so an extraction of relevant messages from the Slint PO files could suffice.

In other cases the scripts differ significantly. For instance "liloconfig" is different in Salix, thus George just a few hours ago "forked" the Slint PO files (actually extracting the messages from liloconfig) and set up a Transifex resource from it here: https://www.transifex.com/gapan/salix/liloconfig

In cases where the script is identical (but the changes Slint => Salix) this shouldn't be necessary.

My main concern with the "forks" is to avoid duplication of efforts from the translators. How to do that is something to which I still have to find solutions. Of course all ideas are welcome.

I hope that this post will have given you at least partial answers.

No excuse needed, your questions are of course perfectly legitimate and help to shed some light on the issues that still need to be worked out, so thanks Diantre for your message.

Yes, indeed. Thanks for the explanation.

This is my concern as well. I think that a new translation effort will be needed for the other distros, there's no other way. More translators are needed.

This is what I mean. I would like to help the Salix guys (and Slackel and probably Zenwalk), but that means that I have to take the time and review 62 fuzzy translations, then translate 46 new messages for them (or even more for the others, I don't know). Additionally, I'm not able to test my translations by running the different systems, there's only Slackware in my computers. Maybe I could do it next weekend, maybe not. It's a matter of time and availability, but also of goals and intent.

I certainly would like to know what the other translators think about this.