SLINT - The Slackware Internationalization Project
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I would enjoy a version called Slackware Whatever. Anyways, thanks for the clarification. I will wait for the next release and next clean install to try slint.
Suggestion: create a slint-latest symlink pointing to the latest-release (or something like that). It is easier to download.
wget gave me an error while trying the official procedure (free translation: wget doesn't support * wildcard)
Code:
Simplicity does not precede complexity, but follows it.
root@slack:~# wget http://slint.fr/packages/slint-14.1*
Aviso: Não há suporte para caracteres coringa no HTTP.
--2014-11-30 20:10:15-- http://slint.fr/packages/slint-14.1*
Resolvendo slint.fr (slint.fr)... 109.234.160.36
Conectando-se a slint.fr (slint.fr)|109.234.160.36|:80... conectado.
A requisição HTTP foi enviada, aguardando resposta... 200 OK
Tamanho: 2719 (2,7K) [text/html]
Salvando em: “slint-14.1*”
100%[===========================================>] 2.719 --.-K/s em 0s
2014-11-30 20:10:16 (115 MB/s) - “slint-14.1*” salvo [2719/2719]
PS: Included the fortune quote because it is beautiful
EDIT: Something is wrong with the character encoding (my system's LANG is set to pt_BR.UTF-8
Last edited by moisespedro; 11-30-2014 at 04:16 PM.
The official procedure is wrong, yes, I should fix it. Sorry about that.
To get a proper display write:
Code:
GROFF_ENCODING=utf8 man slackpkg
See also this. Admittedly I should have wrote that directly in http://slint.fr/package.html instead. But please note that a link to these instructions is provided there, though
About the fortune quote: yes, that's exactly the disease of which I am afflicted, alas
Last edited by Didier Spaier; 12-01-2014 at 05:19 AM.
Reason: pic added
Attn: Translators: new modalities for Slint's website's translation
Hi fellow translators,
We will now translate the web pages (files currently ending in .txt in Transifex) from PO files instead of text files, thanks to the asciidoc plugin of po4a.
This will make the translation easier and less error prone:
The translation off-line using lokalize (that I recommend) or poedit will be allowed.
Only the messages to translate, not the markup, will be included in the text strings to be translated.
The full paragraphs/tables will be presented at once, instead of isolated lines.
In the PO files, the messages will be generally presented in the same order as in the displayed web page and their asciidoc source files.
Instructions for translators will be provided in the PO file as need be.
I have made local tests on the web pages to be translated with no issue.
To ease the transition I've set up in Transifex a new project SlintWebsite that will host the PO files. Don't be fooled by the word "project" used in Transifex, in this case that just means a separate set of files.
All languages available in Slint are automatically set in SlintWebsite, and all existing translation teams can work on both projects.
In the coming days I will upload the resources (POT files) corresponding to the pages slint, installer, package,changelog and translators and also the existing 100% complete translations (in the form of PO files) of these pages. Fortunately po4a allows to convert an asciidoc text file to a PO file automagically.
Meanwhile, please update the pages in the old format .txt as need be. This will be useful to minimize conversion hassle. I will contact individually each team in concern.
When all pages in concern will have been converted I will delete the "old" resources to complete the migration.
Thank you for reading, fortunately the migration itself will be less convoluted than its description
Last edited by Didier Spaier; 12-03-2014 at 06:47 AM.
As you can see on this page, we have completed the migration to PO files for the 5 web pages intended for end users in 12 languages and variants, and of the already translated web pages to 3 more languages. On the occasion translations to Polish were updated, thanks to Marcin aka sycamorex. Thanks also to the folks who reviewed their translations before or just after the migration.
A few messages in a few PO files are not yet translated (Indonesian), and I have updated some files manually (Brazilian Portuguese, Indonesian). These will need to be updated & reviewed by their translation teams.
From now on we will only accept new or updated translations of web pages in the PO format.
I have removed the "old" resources in .txt format from the website, as well as those corresponding to web pages intended for translators, who are expected to understand English. If some folk want the keep some of these for any reason, just drop me a line and I will send send them to you as soon as I receive the email. Another possibility is to just click on the link "Page Source" on the left menu of that we page and download it. By the way this feature will remain, as the PO files will be converted to Asciidoc text files then converted to xhtml format.
Now the website http://slint.fr is in sync with the new PO files. Thanks to Alien BOB who reviewed all translations to Dutch.
Oh, and I have uploaded in http://slint.fr/testing a Slint installer that should be usable connected to a braille terminal thanks to brltty. It's α and I don't have such a device. All I know is that the brltty daemon is started, and that brltty, installed in the new system, is started from rc.S after creation of the devices but before file systems checking. I have a volunteer to test, but more are welcome.
Last edited by Didier Spaier; 12-09-2014 at 08:01 AM.
Slint 14.1 is blind friendly, quarterly update of full installers
Updated installers (small for 13.37, 14.0 14.1, full for 14.1 that bear the version number 14.1.1) are available.
For all versions, several translations of files in the installers, man pages and administrative tools have been added, reviewed and corrected, and the Slint packages have been rebuilt accordingly.
Changes for version 14.1 only:
Blind people owning a Braille terminal can now install Slackware without help from sighted people, thanks to Philippe Delavalade for testing and suggesting enhancements.
The software brltty that allows to use a Braille terminal during installation is also shipped and configured in the installed system, that can thus be fully run and managed from a Braille terminal.
dialog program's configuration file and dialog commands that display a menu or check-list have been modified, mostly to ease usage of a Braille terminal and also to customize the look of the dialog boxes.
Packages brltty-5.2 (the same as installed by the new Slint installers for 14.1) are also available.
At the beginning of installation, as soon as they hear the "beep" coming from the greeting screen, blind users just have to type a command line with "n" for nomedeset appended to the locale code[1], then brltty=<driver code>,<device>,<text table> (see example in attached pic). After that all text displayed on the console will also be displayed on the Braille terminal as soon as the device will be created by udev.
There is a limitation though: in EFI mode the user needs to be assisted by a sighted person to edit the command line. Maybe I'll also ship USB installers using syslinux 6 for both BIOS and EFI machines to avoid that. Then the greeting screen is the same in both cases.
Also considered before the next quarterly release of the full Slint installers is a possible usage of Speakup during installation, if I can find testers.
But for now, documentation is the most urgent task, I think.
[1]to get lines of at most 80 characters, easier to read with a Braille terminal.
Last edited by Didier Spaier; 12-19-2014 at 03:37 PM.
All (small and full) Slint installers for Slackware version 14.1 have been updated, the full ones now bear the version #14.1.2
Only change: in case brltty is found in the command line, /dev/tty[1-4] are created and a command like this run on each before an user input be expected:
Code:
stty -F /dev/tty1 cols 80 rows 25
This way the terminal will have a size of 80x25 even in case of a frame buffer.
Last edited by Didier Spaier; 12-24-2014 at 03:27 AM.
I have slightly edited three webpages and uploaded new POT files to Transifex accordingly.
The aim is to mention Swedish, give a hint to users of Braille terminals in providing a link to http://slint.fr/docs/README_BRLTTY and allow translating last entry in the Changelog.
About the latter, I find Transifex difficult to use in that case as all entries in the Changelog are considered a single paragraph. For that reason I suggest translating it locally with lokalize of poedit. If you do so I remind you that you can type
then translate file_renamed that will have wrapped lines, making easier to work on it, and when you are done just upload that file to Transifex.
Also regarding the Changelog, in the update + conversion process it seems that we lost the translation of the first entry in Transifex. If you didn't have a backup, as a workaround you can copy the relevant part of the source text file of the existing translation from the website and paste it in the PO file.
Now I will update the Contribute page to reflect the changes on webpages' translation handling. As a reminder you won't have to translate it and I will remove the existing translations of that page and Tools from the website. If you want to keep them translated in your language though, just drop me a line and we will treat them as we do for the other web pages.
Last edited by Didier Spaier; 12-27-2014 at 05:39 PM.
Also regarding the Changelog, in the update + conversion process it seems that we lost the translation of the first entry in Transifex. If you didn't have a backup, as a workaround you can copy the relevant part of the source text file of the existing translation from the website and paste it in the PO file.
Disregard that. The cure was to just insert a blank line between entries in the source text file. Oh well...
Last edited by Didier Spaier; 12-28-2014 at 12:00 PM.
I have updated the pages Contribute and Tools so that they be in sync with the current way of dealing with translation files, especially usage of the PO format for web pages' translations and moving all corresponding files to the slintwebsite "project" on Transifex, leaving only in the slint project the translation files for the installers, administration tools and man pages.
I'll wait a few days before updating the PO files corresponding to these two pages and accepting again translation for them. Meanwhile please review them and tell me all corrections and enhancements that you find useful in the English text, either using the slint-translators mailing list or sending me emails.
Eventually we will keep all localized web pages, with at most 20% of the text strings in English. I think that the "100% translated or we don't use it" rule should stay strictly enforced for the files in the installer, the admin scripts and the man page as then, however unwillingly we engage somehow Slackware's reputation, but can be softened for the web pages as in the latter case "provide an up to date information" should have priority over "provide a translated information". Still, translating the Contribute and Tools page will stay optional.
You can already update your translations of all other web pages.
Oh and I would be very grateful if someone could complete the translations to Italian and Indonesian as most of the job is already done
PS I just uploaded a new tarball. Only docs cleaning, make sure the files referred to in Tools are there and update of a reviewed PO file just to stay in sync with Transifex.
Last edited by Didier Spaier; 12-30-2014 at 03:13 PM.
Reason: PS added.
I wish a Happy New Year to all Slint and Slackware contributors and users!
The Irish team was recently created by gezley, and Симон Болоканов (sbolokanov @ LQ) joined the Bulgarian team and already began translating. Welcome on board Gerard and Simon!
Last edited by Didier Spaier; 01-02-2015 at 03:48 AM.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.