Tiny Core Linux
Tiny Core Extensions => TCE Q&A Forum => Topic started by: emninger on November 05, 2015, 04:27:58 PM
-
How does getlocale exactly work. I startet the script and activated the 3 locale which im interested in, ie.
de_DE.UTF-8
de_DE/ISO-8859-1
de_DE@euro/ISO-8859-15
In extlinux i set lang=de_DE
Now, i see, not for all extensions there are also locales.tcz. But for those, which exist, shouldn't it work automatically? Is it presumed to put the locales.tcz in the bootlist? Or, for those ondemand in /tce/ondemand/ ?
I rebooted several times, but not one program with an existing locale is shown up in german ... (??)
-
Correct. A *-locale.tcz will be loaded automatically if present in /etc/sysconfig/tcedir/optional and if the lang= boot code was used (or if $LANG was set another way).
if [ "$LANG" != "C" ]; then
LOCALEEXT="${1%.tcz}-locale.tcz"
[ -f "$LOCALEEXT" ] && install "$LOCALEEXT"
fi
It depends on the extension if German translation is actually provided though.
I know it works for Xfe.
-
Thanks for the explanation; the script you provided, should i put it in /sda1/opt (where .filelist and .xfilelist sit) or start it from within bootlocal.sh ?
-
No. That's already part of tce-load.
Which extensions did you test and did you download their respective *-locale.tcz?
-
It continues to not work for me: To be completely coherent, i changed getlocale.sh and chose only one option (de_DE/ISO-8859-1) and set lang=de_DE in the bootcode.
I tried the existing locales for:
XFE
Viewnior
lxrandr
vlc
nano
-
To check it's working, type "locale". There should be no errors.
-
That's what i get:
locale: Cannot set LC_CTYPE to default locale: No such file or directory
locale: Cannot set LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory
LANG=de
LC_CTYPE="de"
LC_NUMERIC="de"
LC_TIME="de"
LC_COLLATE="de"
LC_MONETARY="de"
LC_MESSAGES="de"
LC_PAPER="de"
LC_NAME="de"
LC_ADDRESS="de"
LC_TELEPHONE="de"
LC_MEASUREMENT="de"
LC_IDENTIFICATION="de"
LC_ALL=
-
Then something is wrong. "locale -a" will list valid options, "de" is not a valid one.
-
Then something is wrong. "locale -a" will list valid options, "de" is not a valid one.
I restarted getlocale.sh, chose de_DE, de_DE.UTF-8, de_DE@euro, set lang=de_DE@euro in the bootcodes, but the result remains the same.
May be, there is some config file which is not covered by my backup setup? What does getlocale.sh exactly do?
-
getlocale.sh generates the locale archive extension, containing those locales you chose. The bootcode then activates one of them.
If locale claims it is "de", then you have two lang= bootcodes, with one being wrong perhaps?
-
This is my extlinux.conf:
DEFAULT core
LABEL core
KERNEL /tce/boot/vmlinuz
APPEND initrd=/tce/boot/core.gz quiet lang=de_DE@euro waitusb=10:UUID="3b305a3c-d95b-4f80-b1fa-b7baaf7db06f" tce=UUID="3b305a3c-d95b-4f80-b1fa-b7baaf7db06f" restore=UUID="3b305a3c-d95b-4f80-b1fa-b7baaf7db06f" swapfile=UUID="3b305a3c-d95b-4f80-b1fa-b7baaf7db06f" home=UUID="3b305a3c-d95b-4f80-b1fa-b7baaf7db06f" opt=UUID="3b305a3c-d95b-4f80-b1fa-b7baaf7db06f" local=UUID="3b305a3c-d95b-4f80-b1fa-b7baaf7db06f" tz=CET-1CEST,M3.5.0,M10.5.0/3 showapps blacklist=b43,ssb,bcma noautologin
(I even left out kmap=de to not create eventual confusion; which, otoh, in any case seem to not have any effect on the console, which despite that setting still uses english/us keymap. Aterm uses the lower 128 ascii of the german keyboard, but i think, aterm is an X application and therefore controlled by the keyboard setting of X).
-
Looking through the list of valid lang settings i didn't see this
lang=de_DE@euro
also I don't believe the "local=" boot code is valid either..
I think we said earlier that showapps is only for diagnostic purposes as it delays the boot process a little
corrected boot code
DEFAULT core
LABEL core
KERNEL /tce/boot/vmlinuz
APPEND initrd=/tce/boot/core.gz quiet lang=de_DE waitusb=10:UUID="3b305a3c-d95b-4f80-b1fa-b7baaf7db06f" tce=UUID="3b305a3c-d95b-4f80-b1fa-b7baaf7db06f" swapfile=UUID="3b305a3c-d95b-4f80-b1fa-b7baaf7db06f" home=UUID="3b305a3c-d95b-4f80-b1fa-b7baaf7db06f" opt=UUID="3b305a3c-d95b-4f80-b1fa-b7baaf7db06f" tz=CET-1CEST,M3.5.0,M10.5.0/3 blacklist=b43,ssb,bcma noautologin
:)
-
But getlocale.sh says:
Now processing... /
Locales installed. Creating extension... |
Done. The extension is at /mnt/sda1/tce/optional/mylocale.tcz and in onboot.lst
Reboot with lang=xyz (for example lang=de_DE@euro) to start using this.
Press enter to quit.
In any case, i tried all, but to no extent. The result of ~$ locale is:
locale: Cannot set LC_CTYPE to default locale: No such file or directory
locale: Cannot set LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory
LANG=de
LC_CTYPE="de"
LC_NUMERIC="de"
LC_TIME="de"
LC_COLLATE="de"
LC_MONETARY="de"
LC_MESSAGES="de"
LC_PAPER="de"
LC_NAME="de"
LC_ADDRESS="de"
LC_TELEPHONE="de"
LC_MEASUREMENT="de"
LC_IDENTIFICATION="de"
LC_ALL=
I suspect there might be somewhere a rest of the previous (default) Xvesa setup, because at the end of the boot process i get the - obviously harmless - prompt: xset: unable to open display ""
-
Some additional info. When i do APPS > Maintainance > Check for Updates i see there this error msg:
Error Could not verify mylocale.tcz
. Why? And what does that mean?
-
mylocale is the local extension created by running the script from the getlocale extension.
mylocale doesn't exist in the repo, hence the error message.
-
I understand. Thanks! :)
-
Something in your system is causing LANG to be "de". If it's not your bootloader, then it must be something in your backup or home dir.
-
Something in your system is causing LANG to be "de". If it's not your bootloader, then it must be something in your backup or home dir.
But what? Do you have, by chance, an idea, where i could look?
Thanks a lot in advance.
-
If you're using a backup, then you can use the "norestore" boot code to boot without restoring your backup and check if the problem disappears.
-
Make sure you do not have etc in your .filetool.lst.
-
Hi emninger
In my comments about the results of the showbootcodes command here:
http://forum.tinycorelinux.net/index.php/topic,19088.msg117402.html#msg117402
I stated:
home=UUID="3b305a3c-d95b-4f80-b1fa-b7baaf7db06f" opt=UUID="3b305a3c-d95b-4f80-b1fa-b7baaf7db06f"These two items specify that you have persistant /home and /opt directories, so they don't need to be included in
your backup. Open your filetool.lst file, remove any lines beginning with home or opt, then run a backup.
Did you correct your filetool.lst file?
-
I believed i did, but effectively, i did not. Now it's corrected ;)
-
But nevertheless the error msg after
# locale persists ... :-(
-
It's funny: Abiword (although there is no locale extension) shows up in german skin?
PS. But apparently there is missing some functionality (?)