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.
Im all in for helping gabrielmagno and Marcelo_Belfalas on the pt_br translation, should I pm gabriel for instructions ?
Yes please, through LQ and/or register to Transifex (it's free), then go to this page and click the "Join team" button. Thanks for offering to help, we still need translators and reviewers.
By the way, though French translation be already included in slint it would certainly benefit of a review, so volunteers are welcome as well.
Last edited by Didier Spaier; 05-04-2013 at 10:28 PM.
Maybe we could end up with two Spanish locales:
es_ES
es_<Latin America>
I agree. Transifex has Spanish (Latin America) (es_419) language listed. It seems to me that we should use it instead of es_CR and leave es_ES for Castilian Spanish.
I created a GPT partition in a VirtualBox hard disk (see attached image) and tried to do some testing. The fist thing I noticed is that the setup script is displaying a fdisk error:
Code:
WARNING: GPT (GUID Partition Table) detected on '/dev/sda'! The util fdisk doesn't support GPT. Use GNU Parted.
WARNING: GPT (GUID Partition Table) detected on '/dev/sda'! The util fdisk doesn't support GPT. Use GNU Parted.
Like that, twice. The second thing I noticed is that the GPT partitions are not detected at all. Just to be sure, I booted the same machine with the Slackware 14 DVD, and yes, it works. GPT partitions are detected alright.
I think (I might be complety wrong though) that the duplicate probe command is causing the fdisk error message (there's also duplicated message in /tmp/SeTfdisk, but I'm not sure if it's related), and the number 83 is causing the problem with GPT, since it uses 8300 for Linux partitions and 8200 for swap partitions.
I agree. Transifex has Spanish (Latin America) (es_419) language listed. It seems to me that we should use it instead of es_CR and leave es_ES for Castilian Spanish.
"es-419" represents Spanish ('es') appropriate to the UN-defined Latin America and Caribbean region ('419').
so it seems logical to use it.
But at the same time, 'strace' shows that gettext needs to access /usr/lib/<locale> directory, but neither /usr/locale/es-419 nor the fallback /usr/locale/es are shipped in glibc-i18n package.
For that reason I propose that we keep the idea but implement it that way:
(1) keep the value es_CR.utf8 as default locale for all territories in the Latin America and Caribbean region (in isolinux.cfg)
(2) in the f3.txt and f4.txt screens, mention only language [(region)], not the <locale> code. For instance:
Code:
Choose your language for installation
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
Code Language
01 Deutsch
02 Greek
03 English (USA)
04 Español (América Latina)
05 Español
06 Français
07 Italiano
08 Nederlands
09 Polski
10 Português (Brasil)
11 Russian
Please type the code at the prompt below to choice your locale.
Examples:
boot: 06 <=== Français
boot: 04 <=== Español (América Latina)
I created a GPT partition in a VirtualBox hard disk (see attached image) and tried to do some testing. The fist thing I noticed is that the setup script is displaying a fdisk error:
Code:
WARNING: GPT (GUID Partition Table) detected on '/dev/sda'! The util fdisk doesn't support GPT. Use GNU Parted.
WARNING: GPT (GUID Partition Table) detected on '/dev/sda'! The util fdisk doesn't support GPT. Use GNU Parted.
Like that, twice. The second thing I noticed is that the GPT partitions are not detected at all. Just to be sure, I booted the same machine with the Slackware 14 DVD, and yes, it works. GPT partitions are detected alright.
I think (I might be complety wrong though) that the duplicate probe command is causing the fdisk error message (there's also duplicated message in /tmp/SeTfdisk, but I'm not sure if it's related), and the number 83 is causing the problem with GPT, since it uses 8300 for Linux partitions and 8200 for swap partitions.
You are absolutely right about 83 vs 8300, thanks! I didn't thought I could have tested the GPT case through VirtualBox, my bad.
About duplicate lines I am not sure and will investigate. Long story short, what setup does with "probe" here is search a Linux partition. If it finds any it writes a list of it, else complains to the user.
I will release a new edition with a fix asap.
Last edited by Didier Spaier; 05-07-2013 at 04:02 PM.
For that reason I propose that we keep the idea but implement it that way:
(1) keep the value es_CR.utf8 as default locale for all territories in the Latin America and Caribbean region (in isolinux.cfg)
(2) in the f3.txt and f4.txt screens, mention only language [(region)], not the <locale> code.
Yes, I think it would work that way. Unless there's a real need for another spanish localization, one would serve just fine.
Except for es_ES, which I consider it's different from Latin American Spanish. My concern is that the current es_ES translation is not a Castilian Spanish translation, it's a copy of es_CR. The changes that AlvaroG did in it, are already merged into es_CR.
My concern is that the current es_ES translation is not a Castilian Spanish translation, it's a copy of es_CR. The changes that AlvaroG did in it, are already merged into es_CR.
Then I think we should just wait for es_ES to be fully "Castilanized" before we include it in slint.
Till then, users who whould have preferred it will use Español (América Latina) or English (USA) if they prefer, fully knowing what they get for their money
Last edited by Didier Spaier; 05-05-2013 at 03:01 PM.
Why do we still have Gnome in the list of software series to choose?
Accurate answer should come from Pat, but my guess is that's just in case Gnome makes a comeback.
This doesn't hurt anyway as the test:
Code:
if [ -d $DS/gnome -o "$DS" = "" ]
fails if there is no gnome directory under slackware or slackware64 in the installation media (see /usr/lib/SeTPKG and /isolinux/setpkg) so in that case the user won't be proposed to install it. But on the other hand it can help to install it as a third party series.
Also, xinitrc.gnome is listed in xwmconfig. That helps people wanting to use gdm (available @ slackbuilds.org) as thanks to this no configuration post installation is needed.
Why do we still have Gnome in the list of software series to choose?
Usually the setpkg script comes from the install media in the isolinux directory, but in the case of a network install I believe there is a bug there due to the strange mounting location.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.