Quote:
Regards, |
Quote:
Code:
$ msgfmt -c <lang>.po |
Quote:
Thank you for the command! |
New slint version coming soon
Hey folks, new slint version coming soon (possibly tomorrow) will include:
(1) A bug correction in slint.sh (wrong -m option in a cpio command which prevented to repack the initrd, making the DVD ISO image unusable). I'm a little worried that nobody noticed that... Did anybody try the internationalized installer?? (2) Codes for more locales in /isolinux.f4.txt and isolinux/isolinux.cfg so that translators can see how translated messages are displayed in the installer. Caveat: even if a locale is listed hitting 'F4' it will be actually available only if file <locale>.po has been copied in directory /path/to/slint-<date>/po before running /path/to/slint-<date>/slint.sh (3) What is needed to display Cyrillic characters (Russian variant) in the installer. Otherwise bormant would have been *very* angry ;) @bormant: in that version the default console font for locale ru_RU will be koi8r-8x16.gz (with an unicode mapping). Would you prefer another one, just ask: it is easy to change. EDIT. I just saw this in this thread what bormant said: "terminus in utf8 (ter-v*) can show most of unicode chars in plain console, so it is a good choice for default." So I will try that one, which can be used for Polish as well. Stay tuned. |
Quote:
I did notice it but didn't have time to look into it or report it here. I am only 11% done with my translation but it would be good to start doing it in a context. |
Quote:
EDIT I will try a ter-v* font which can be used for Russian as well as Polish. |
Quote:
|
Didier,
Could you please give diantre access to the es_ES translation (or give me access to es_CR)? I noticed that I can modify the es_ES and he can modify the es_CR, so we can't collaborate as we should. diantre, I have read the translation, changed a few things, would like to know what you think about it. (next message like this one will go thru transifex, I promise ;) ) |
Quote:
https://www.transifex.com/projects/p...ge/es_ES/edit/ To add members and/or reviewers. I'll pull the translation right now, and I'll let you know, thanks! |
AlavaroG, Diantre, I see that you are translators for each other's team, good.
Yes, this kind of communication can go through Transifex in the future. While we are at it, I encourage every translator to hire reviewers (I could have made an announce on Transifex about that as well). Oh, and if someone is eager to review French translation, please let me know. I am still unsure that it be wise to propose several locales per language in the installer though. But well, as as long we don't don't pay for overweight (excess baggage as we literally say in French), we can afford it. By the bye, would it be useful to allow users to choose which locale, or locales, include in the installer when making the DVD ISO? Please everyone let me know what you think. |
2 Attachment(s)
Quote:
ter-k* has no this disadvantage because uses 256 glyphs, it can be used for ru_RU.utf8 but needs another decision for Polish. |
Quote:
So to use ter-v* one needs to provide a mapping to include only part of these glyphs, which should be equivalent to using one of the other fonts. For instance if I write: Code:
setfont -m koi8-r.txt ter-v16n.psf.gz Code:
setfont ter-k16n.psf.gz Anyway this deserves attention, so I will make tests, and maybe provide a mean to choose between two or three fonts for ru_RU when making the DVD ISO image (in slint.sh) so you can test as well if you wish. That could be a choice between ter-k, ter-v and another font, maybe koi8r.8x16.gz? If available, please upload in Transifex a .po file with more messages translated, to increase the scope of tests. Thanks in advance. |
Quote:
Code:
LC_CTYPE=fr_FR.utf8 Most upstream translations that made it into Slackware originate from the Debian folks, I suppose. Their translators never read an IT magazine or IT newspaper a foreign language, so they invent their own IT-lingo, which nobody (including native speakers) understands. That's the main reason, why I reject using it. Quote:
*) Or worse: "I have detected it from your IP address." It's fine for me if I don't get bothered with it. KISS principle: make everything completely optional. Quote:
Digging through .po files isn't going to do this. Especially in a installer you have to make sure, that all translations in every place are 100 % correct (not by wordbook, by sense) or people start to destroy their data by accident. *) To answer the question: No, I don't speak English well enough to qualify for this job. |
Quote:
Quote:
Quote:
gettext rely on LANG and I don't intend/need/am able to reinvent it. It's not perfect, but it works well enough in our use case. Quote:
Quote:
(1) You can use slint and keep the en_US locale. That is the default. (2) Slint doesn't try to guess anything. It will use during installation the locale you tell it to use, period. (3) Slint associates a default keyboard map to each locale, but you can of course change it in 'setup'. (4) Slint proposes you to keep in the being installed system the last locale settings (LANG and keymap) that you used during installation, but you can of course refuse that: just click "cancel" or leave the features you don't want unchecked. Quote:
(2) In slint all internationalized scripts are copied in a source/ directory for each internationalized Slackware edition, so that the translator keeps the context at hand. (3) Translators are recommended not to use Transifex' web editor, as if they do they loose the context. Instead, usage of a specialized PO editor, which displays it, is requested. (4) Translators are requested to be able to read a script and understand the messages they have to translate (see post #14 in this thread). (5) Also, all translations should be reviewed (6) The toolbox includes recommendations for translators in the same vein. Even so, accuracy of translation is not 100% guaranteed, but we do our best. In a few case the translation may even be more accurate than the original (no offense to Pat intended :-) |
Kernel panic booting slint dvd image in VirtualBox
1 Attachment(s)
I'm trying to boot the slint dvd in VirtualBox to test my translation. Everything looks good and the slint.sh script doesn't complain:
Code:
bash-4.2# ./slint.sh 64-14.0 The DVD used to create the slint DVD is the Slackware64 14.0 DVD, the same I used to install my desktop machine, so I'm sure the DVD is fine. The slint log file in /tmp/slint-64-14.0/log.txt shows no errors (as far as I can tell). Am I doing something wrong? :confused: Any help is appreciated. |
All times are GMT -5. The time now is 11:11 PM. |