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.
Hi, and thanks for slint project, the
opportunity to participate in
the project. Currently, I get a error 408 when I try to access to slint's page. Does anyone have the problems with accessing to this page?
I didn't see any clue in server's logs either, especially no error 408 reported.
Looking here and there it's not always easy to diagnose that kind of error.
Only thing I can tell is that the server is not overloaded (but it's on a shared hosting so I can't be sure), so it *could* be due to an excessive delay on the network between your computer and the server.
Last edited by Didier Spaier; 08-10-2013 at 04:00 PM.
Reason: Typo corrected
Never, but really never, do not try to translate the Slackware installer in Romanian.
Because, something like of 0,001% computer users use the native language, even on Windows.
No one buy even an Romanian keyboard, in Romania, and no one install, even the frakking Windows (XP/Vista/7/8/*), in Romanian.
In Romania, starting from age 4, you are raised looking at computers who speak English. Technically, an Romanian is (99%) incapable to understand the computer messages WHEN are in Romanian.
As final note, DO NOT TRY to translate Slackware Installer in Romanian! Never! Because nobody will understand something...
Sorry guys, but I hope that you leave the installer in English, speaking of Romanian language. It is the best choice to reach something of RO based computers.
Last edited by Darth Vader; 08-10-2013 at 04:11 PM.
I'm a bit puzzled by your post, especially after our exchanges of PMs about the project. Maybe something made you get to this somehow definitive conclusion since then?
Anyway if you're right nobody will volunteer to do a Romanian translation so that shouldn't be an issue
I know that you contribute to Slackware by other means though and appreciate it: there's more than one way to help the community.
Cheers,
Last edited by Didier Spaier; 08-10-2013 at 04:31 PM.
slint now includes 6 translations - please review them in context
The new slint release includes the 6 translations complete at time of writing:
French
Polish
Portuguese (Brazil)
Russian
Spanish (Latin America)
Ukrainian
It internationalizes installer of Slackware-13.37, Slackware-14.0 or Slackware-current (in its state at time of writing), 32bit and 64bit alike.
The purpose of this release is to make easier to review these 6 translations "in context", not only the installer itself but also Slackware scripts that are also translated, among which:
Script 'slintify.sh' that you will find at the root of unpacked slint tarball can help you.
It produces a full tree of Slackware-current (32bit or 64bit) including slint (that replaces the genuine installer) and aforementioned internationalized scripts (packages that include them are rebuilt), as well as the slackware.mo files for the 6 complete translations, and optionally makes a DVD ISO image of it (but the /source directory, but you can add it if you want in editing the script).
Testers and reviewers could use it that way:
Run it (as root) requesting the DVD ISO image
Use the DVD ISO image to install Slackware internationalized in a virtual machine (qemu, vmplayer, VB, whatever)
Run Slackware (internationalized) in the VM to test and review.
You can also install internationalized Slackware in a hard disk partition, of course.
To avoid wasting a DVD for that you could use one of the USB images of the installer provided for 32bit and 64bit versions, and when running 'setup', choose as 'source' the hard disk partition where lies the internationalized Slackware tree, either pre-mounted or not as you prefer.
Warning: all this stuff is provided for testing purposes only, about that please read carefully files WARNING and TESTING that you will find at the root of internationalized Slackware tree.
Last edited by Didier Spaier; 08-14-2013 at 04:42 AM.
Reason: 6, not 8 translations are complete
The new slint release includes the 8 translations comlete at time of writing:
Thanks for the update, Didier. Well, I wouldn't consider the Polish translation as complete. Everything did get translated but it hasn't been fully reviewed yet. We're working on it and the moment it has been completed, I'll let you know. We'd like to review most of the strings in context within the installer. That, obviously, takes time.
You didn't have a chance of reading most of previous post before answering, because I mistakenly hit the "save" button after writing only the first line, sorry about that.
But now you can see that this release's purpose is helping to do exactly what you stated: review translations in context - not only installer's context but also installed internationalized system's context
Last edited by Didier Spaier; 08-13-2013 at 03:51 PM.
I've updated slint to stay in sync with last batch of updates in genuine Slackware-current (32bit and 64 bit) dated Sat Aug 17 03:30:00 UTC 2013, but I want to test again full installation after updates of setpkg and SeTPKG, then uploading all the stuff again will take a while @ 10 kilobytes per second, so please be very patient.
Also, I forgot to tell this: if you already installed internationalized Slackware using slintify.sh, be aware that using "slackpkg upgrade-all" will replace following internationalized packages by genuine versions:
fontconfig
glibc
gpm
kbd
lilo
mkfontdir
network-scripts
pkgtools
shadow
x11-skel
If you want to avoid that, blacklist these packages editing /etc/slackpkg/blacklist accordingly.
Last thing for now, behavior of "setconsolefont" in internationalized Slackware is bad, this too will be changed in next release.
Last edited by Didier Spaier; 08-17-2013 at 12:57 PM.
Reason: typo corrected
Here are the tarball and its md5 file, in sync with Slackware-current as of Sat Aug 17 03:30:00 UTC 2013.
All ISO and USB installers have been updated in pub's subdirectories.
Now in internationalized Slackware-current and unless a custom console font have been chosen during installation, default console font according to the locale used during installation is set as default (we assume that 'terminus' fonts are installed).
But if you run 'setconsolefont' in installed system you will be offered same choices as in genuine Slackware. Maybe we could think about proposing in this script all fonts available in /usr/share/kbd/consolefonts at time of running it?
Russian and Polish translations have been updated as in Transifex.
script 'slint.sh' is localized in es, fr, id, it, pl, pt, uk. Hopefully ru will follow soon.
Last edited by Didier Spaier; 08-18-2013 at 04:42 AM.
slint-20130820.tar.xz and its md5 file are in sync with Slackware-current as of Mon Aug 19 22:49:15 UTC 2013, to update slintify.sh following lilo's version bump.
slint-20130822 and its associated md5 file are available, in sync with Slackwre-current as of Wed Aug 21 21:26:58 UTC 2013 and includes updated translation for pt_BR in sync with Transifex. Rebuilt installers for Slackware-current (32bit and 64 bit) are available in pub's subdirectories.
Meanwhile the the "new" tarball slint-20130822 just became old and was moved to slint.fr://pub/slint-history (see other post coming in a few minutes). Sorry for the inconvenience.
Now, let's translate man pages of Slackware tools.
I suggest that we localize manual pages of Slackware tools, at least those included in 'pkgtools' and 'slackpkg', respectively:
explodepkg
installpkg
makepkg
pkgtool
removepkg
upgradepkg
slackpkg
slackpkg.conf
This can be done without any modification of genuine man pages in English. thanks to the po4a application that can directly convert a man page from/to a POT file, allowing us to proceed as usual.
I have done that for French and that works. Now it's your turn to play, fellow translators :-)
I realize that translating man pages needs more work, though, and consider that optional. In other words each translation team can set its own priorities.
I just uploaded pkgtools.pot and slackpkg.pot on Transifex.
Also, I uploaded a new slint tarball on our website in http://slint.fr/pub, that serve two purposes:
- modified script slint-20130904/slintify.sh now installs an internationalized Slackware-current whose packages 'pkgtool' and 'slackpkg' include translated man pages (in French at time of writing)
- provide means of testing your translations of man pages in context.
I won't go into the gory details here, just run slint-20130904/scripts/gen_man_pages.sh to get instructions how-to fulfill the prerequisites, then test your translations of man pages in context when there are complete or near complete.
I generated one POT file per package, so that you can share work between translators inside a translation team.
I'd be pleased to get suggestions from all readers (not only translators) about which other Slackware tools include man pages that should be translated (network-scripts, that ship man pages for rc.inet1 and rc.inet1.conf come to my mind, but maybe there are others).
FYI, modified packages 'pkgtools' and 'slackpkg' that you get running slintify.sh can be used even on a _not_otherwise_internationalized_ Slackware-current (and Slackware 14.0 as well). Just grab them from the internationalized Slackare tree output of that script. To read the translated man pages, prepend the 'man' command with "GROFF_ENCODING=utf8" or append "export GROFF_ENCODING=utf8" to ~/.bashrc, and have LANG set to an UTF-8 encoded locale, e.g. LANG=fr_FR.utf8.
Last edited by Didier Spaier; 09-04-2013 at 07:28 AM.
Reason: Last sentence modified
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.