Puppy Linux Discussion Forum

[droope]

Hi people,

I am going to bother you all again on this same issue, only that now in a separate thread.
The intention of this proyect, is, that before version 4.2 is launched, we can have all scripts fetch language files from a directory. (As done here)


Progress done:
Connect wizard (updated droope's corrected version)
Xwin
XorgWizard (Updated to Mu's corrected version)
Remasterpup2
Chooselocale
Bootmanager
Cups Shell
Petget.
Applications directory localized

Outdated
Updated 18/03/09.

[esmourguit]

Bonjour,

I tried to localize xorgwizard how did Mu for a test. But it does not work.
As soon as I brought this:

[droope]

That's interesting, but, i don't think it will be that easy, i mean, you have to create the file first, and modify the Script's text variables to be looked for in the text file,


I GUESS... LOL.

Maybe we can try and do this, what do you think?

Yes!

Check this

Mu's version of some output:

[MU]

[MU]

To compare files:
from Puppy 3:
gtkdiff-0.7.0
But it requires to install also Gtk 1.2 and Glib 1.2.

Maybe someone posted also a pet for a "diff" program, that has less dependencies.

Or use the console:
diff --help

Mark

[droope]

[MU]

mytest is the filename.

simplified:

[droope]

Thank you, this post has helped a lot.

I was thinking of using what you localized so as not to waste effort. So i thought I could compare the version you localized (before localization) and current version, but I need you to tell me exactly which version it is you translated, so as not to make the script any older by accident.

After you and the current developers of scripts answer, I should be able to start working. It shouldn't be a lot of work, i think.

DOn't know if the scripts have changed a lot, tho.

[HairyWill]

to compare files on the command line use
diff file1 file2
puppy 4 contains the graphical diff program xfdiff in the utility menu, I usually start it from the prompt, ie
xfdiff file1 file2

[esmourguit]

Bonjour,

Sorry for the inconvenience, but in fact it was missing the file /usr/share/locale/en/LC_MESSAGES/xorgwizard.mo. But not sure it was the issue.
Then it works.
Attached file xorgwizard4.2-localized and connectwizard-420loc for test and english and french files

Cordialement

[droope]

I am testing it, the only issue until now, it's that in the name of the window, when using EN locales, i get Assistant de conexion, or something similar.

I think the problem is in the .mo, tho.

I will try to localize it in french, and if it works, i'll translate it into spanish. As soon as we have all scripts set up on 4.2.

This should be included on 4.2, do you want me to tell whodo?

We should send him one or a few MP's So as not to lose localizated scripts again.

Edit: It's not working I chose fr_BR, is that correct?
Is it fully localized?

[esmourguit]

Bonjour,
No it is not completely localized. I is just a test.
The french locale is fr_FR
But there is an issue in xorgwizard4.2-loc, line 777.

[MU]

[esmourguit]

Bonjour,
Thank you Mark for your help. Now it works.
Here the dotpet whith the french locale files for test.
Cordialement

[maddox]

Hi all,
Hope I posted this in the correct Topic.

It's really great news to see an effort to localize Puppy scripts.
If I may, I've got a few questions concerning gettext (po files), translation and puppy 4.2.

1: If Puppy is going to be completely translated, i.e. all scripts will use gettext and po files,
Could there be a problem, kernel or other wise, using so many extra variables for translation (a limit to the nber of variables used) and also could this impact Puppy's performance ?
... Some scripts use over a 100 translation variables and might call other scripts with extra translation variables.
performance drop i.e : .. number of translation variables and parsing the po file(s) to find the correct variable entry.

2: Has the community set-up any standard rules/guidelines to localise variables in a script : i.e preset variable names inside scripts or rules to define the variable names for translation.
.. There doesn't seem to be any real consistancy in the variable naming process.
frame -> $frame1 and in a completely different hbox/vbox $frame2 .. I can elaborate a bit more if needed.

3: What do you do about a Title, Label, Button or other forgotten bits that have no translation in a script ?
i.e. <button OK> or button cancel or Title ...dialup modem, MB/KB to Mo/Ko ..
Do we change the english script and submit the english modification.. but then, where to post the proposed change ?

4: Can All the text messages be translated with a po file in any script ? (except of course initrd.gz : language specific manual translation must be done)
i.e... echo "blabla" > /dev/console or echo "blabla" > 2&1
and indirectly, does X have to be running for gettext to work ?

Translation part:
5: Has anybody found an equivalent to yaf-splash ?
As it only correctly displays english characters, no matter what the encoding used.

6: Dialog doesn't seem to like accents -> shutdown/save script and others
The displayed box has holes punched in it using accents (incorrectly displayed) and the right edge is completely distorted.

7: From what I understand, the Puppy 4.2 will keep to UTF-8 encoding for scripts,
but then, we (French Toutou 4.1.2 ) had to encode some scripts into ISO-8859-1 for them to display the accents correctly.
MU kindly gave us a partial solution, his gxmessage and the switch "-encoding UTF-8", thanks MU.

The info I've found about UTF-8 is that english characters are 1 byte encoded and french characters are 2 byte encoded
Using the ISO-8859-1 encoding the french characters are 1 byte encoded.
This makes it difficult for us and probally others : we have to test each script and if necessary modify the script and adapt the encoding accordingly.

Sorry about the mostly questions post and the numerous edits.

Thanks in advance to all the worldwide puppy users.