LinuxQuestions.org
Welcome to the most active Linux Forum on the web.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 05-04-2013, 05:30 PM   #91
Didier Spaier
LQ Addict
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slint64-15.0
Posts: 11,077

Original Poster
Rep: Reputation: Disabled
Locales settings


Maybe we could end up with two Spanish locales:
es_ES
es_<Latin America>

I noticed that for Spanish the XkbLayout option of xorg.conf can take either value "es" or "latam" (found in evdev.lst), hence that suggestion.

In the same vein, I noticed that we have a value "br" for Portuguese (Brazil), so I assume that "br" should be the default for pt_BR?

What do you think?

To make things clearer, I am speaking about X keyboard layout, not kernel keymap.
 
Old 05-04-2013, 06:34 PM   #92
Skaperen
Senior Member
 
Registered: May 2009
Location: center of singularity
Distribution: Xubuntu, Ubuntu, Slackware, Amazon Linux, OpenBSD, LFS (on Sparc_32 and i386)
Posts: 2,689
Blog Entries: 31

Rep: Reputation: 176Reputation: 176
Quote:
Originally Posted by Diantre View Post
There are significant differences between the Spanish language as spoken (and written) in Spain and Latin America.
And this is why we often need a difference between en_UK and en_US.
 
Old 05-04-2013, 07:31 PM   #93
Iuz
LQ Newbie
 
Registered: Sep 2012
Location: Brazil
Distribution: Slackware
Posts: 22

Rep: Reputation: Disabled
Im all in for helping gabrielmagno and Marcelo_Belfalas on the pt_br translation, should I pm gabriel for instructions ?
 
Old 05-04-2013, 10:17 PM   #94
Didier Spaier
LQ Addict
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slint64-15.0
Posts: 11,077

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by Iuz View Post
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.
 
Old 05-05-2013, 01:11 AM   #95
Diantre
Member
 
Registered: Jun 2011
Distribution: Slackware
Posts: 515

Rep: Reputation: 234Reputation: 234Reputation: 234
Quote:
Originally Posted by Didier Spaier View Post
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.
 
Old 05-05-2013, 04:31 AM   #96
Diantre
Member
 
Registered: Jun 2011
Distribution: Slackware
Posts: 515

Rep: Reputation: 234Reputation: 234Reputation: 234
GPT Disks

Hello!

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.

So I had a look at the setup script:

Code:
if probe -l 2> /dev/null | probe -l|awk '/^\/dev\// {if ((($2 != "*") && ($5 == "83")) || (($2 == "*"
) && ($6 == "83"))) print $1}' 1> /dev/null 2> /dev/null ; then
 probe -l 2> /dev/null | probe -l|awk '/^\/dev\// {if ((($2 != "*") && ($5 == "83")) || (($2 == "*")
&& ($6 == "83"))) print $0}' | sort | uniq 1> $TMP/SeTplist 2> /dev/null
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.
Attached Thumbnails
Click image for larger version

Name:	slint-gptdisk.png
Views:	28
Size:	20.7 KB
ID:	12454  
 
1 members found this post helpful.
Old 05-05-2013, 04:58 AM   #97
Diantre
Member
 
Registered: Jun 2011
Distribution: Slackware
Posts: 515

Rep: Reputation: 234Reputation: 234Reputation: 234
Quote:
Originally Posted by Skaperen View Post
And this is why we often need a difference between en_UK and en_US.
Precisely. Like Spanish and English, the same thing happens in the Portuguese language, hence pt_BR and pt_PT.
 
Old 05-05-2013, 04:59 AM   #98
Didier Spaier
LQ Addict
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slint64-15.0
Posts: 11,077

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by Diantre View Post
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 is defined this way in RFC 5646:
Quote:
"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)
What do you think?
 
Old 05-05-2013, 05:41 AM   #99
Didier Spaier
LQ Addict
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slint64-15.0
Posts: 11,077

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by Diantre View Post
Hello!

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.

So I had a look at the setup script:

Code:
if probe -l 2> /dev/null | probe -l|awk '/^\/dev\// {if ((($2 != "*") && ($5 == "83")) || (($2 == "*"
) && ($6 == "83"))) print $1}' 1> /dev/null 2> /dev/null ; then
 probe -l 2> /dev/null | probe -l|awk '/^\/dev\// {if ((($2 != "*") && ($5 == "83")) || (($2 == "*")
&& ($6 == "83"))) print $0}' | sort | uniq 1> $TMP/SeTplist 2> /dev/null
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.
 
Old 05-05-2013, 01:26 PM   #100
Diantre
Member
 
Registered: Jun 2011
Distribution: Slackware
Posts: 515

Rep: Reputation: 234Reputation: 234Reputation: 234
Quote:
Originally Posted by Didier Spaier View Post
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.
 
Old 05-05-2013, 02:42 PM   #101
Didier Spaier
LQ Addict
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slint64-15.0
Posts: 11,077

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by Diantre View Post
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.
 
Old 05-14-2013, 03:11 PM   #102
sycamorex
LQ Veteran
 
Registered: Nov 2005
Location: London
Distribution: Slackware64-current
Posts: 5,836
Blog Entries: 1

Rep: Reputation: 1251Reputation: 1251Reputation: 1251Reputation: 1251Reputation: 1251Reputation: 1251Reputation: 1251Reputation: 1251Reputation: 1251
Why do we still have Gnome in the list of software series to choose?
 
Old 05-14-2013, 03:39 PM   #103
Didier Spaier
LQ Addict
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slint64-15.0
Posts: 11,077

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by sycamorex View Post
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.
 
Old 05-14-2013, 03:43 PM   #104
volkerdi
Slackware Maintainer
 
Registered: Dec 2002
Location: Minnesota
Distribution: Slackware! :-)
Posts: 2,548

Rep: Reputation: 8556Reputation: 8556Reputation: 8556Reputation: 8556Reputation: 8556Reputation: 8556Reputation: 8556Reputation: 8556Reputation: 8556Reputation: 8556Reputation: 8556
Quote:
Originally Posted by sycamorex View Post
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.
 
Old 05-14-2013, 04:54 PM   #105
sycamorex
LQ Veteran
 
Registered: Nov 2005
Location: London
Distribution: Slackware64-current
Posts: 5,836
Blog Entries: 1

Rep: Reputation: 1251Reputation: 1251Reputation: 1251Reputation: 1251Reputation: 1251Reputation: 1251Reputation: 1251Reputation: 1251Reputation: 1251
Thank you both. I got slightly puzzled when I was testing my translation in virtualbox and was presented with the choice of installing gnome.
 
  


Reply

Tags
accessibility, blind, installation, internationalization, slackware



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] Questions about fbterm's usage in Slint or Slackware installer Didier Spaier Slackware 2 03-05-2014 05:09 PM
[SOLVED] [TESTERS WANTED] Slint installers for Slackware 14.1 => LAST CALL Didier Spaier Slackware 11 11-22-2013 06:22 AM
[ANN] slint (Slackware Internationalized) 14.1 beta is ready: please test Didier Spaier Slackware 0 09-19-2013 03:44 PM
The Slackware Internationalization Project Didier Spaier Slackware 62 04-26-2013 05:07 AM
Slackware, and internationalization t_maggot Slackware 2 12-06-2006 10:27 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 10:33 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration