(old)Puppy Linux Discussion Forum

po files available for
ca de es fr hu id it nl no_NO pl pt_BR ru sv_SE
in directory po of source at
http://freecode.com/projects/xdialog

Or to translate yourself
mkdir -p /usr/share/doc/nls/Xdialog
and copy the following Xdialog.pot to /usr/share/doc/nls/Xdialog/Xdialog.pot

Ready to use translations exist for the languges:
de en_GB es fr hi nl pt_BR sv

at http://ayttm.sourceforge.net/files.php
download Source .bz2 tarball
click and extract directory po
copy: for other languages
make directory:
and download attached ayttm.pot to /usr/share/doc/nls/ayttm/
Then use momanger for translation of ayttm

use chat program (launch from desktop icon) in your language.
Have fun

That's great L18L,

It's always nice to get a translation ready-made, like was the case for nl.

However, there was lots of Fuzzy and the translation was not complete.
Now corrected

Thanks.

Hi all,

I translated PupSnap from the pot file (because impossible to translate in Momanager)...no luck.. PupScan remains in English.

I then looked at the actual script files (version 2.2.1) and it looks like nothing is internationalized.

Am I missing the obvious again
Thanks for any pointers!

Bert

Bert wrote:Hi all,

I translated PupSnap from the pot file (because impossible to translate in Momanager)...no luck.. PupScan remains in English.

I then looked at the actual script files (version 2.2.1) and it looks like nothing is internationalized.

Am I missing the obvious again
Thanks for any pointers!

Bert

Where did you get a pot file from if nothing is internationalized?

Obviously radky is staying with "english only"

At [url=http://www.murga-linux.com/puppy/viewtopic.php?t=65235&start=3]puppy localization solved [/url] 01micko wrote:I suppose what we need to do is apply the standards, that is, everyone who scripts should learn to use gettext and where the locale file should be stored. It's not difficult. Even I roughly learnt some of it!

Where did you get a pot file from if nothing is internationalized? Rolling Eyes

Hi L18L,

In this very thread, page one!

http://murga-linux.com/puppy/viewtopic. ... 738#684738

It also has a pot file for PupControl, which I would like to translate.

I searched in the Spanish forum and downloaded the Spanish version, made by Victor, and discovered he translated it directly in situ. (no gettext)

Pupsnap shows up in MoManager, but when clicked, it exits with an error.

So I opened the pot file in Poedit and made a .po and .mo.

Bert wrote:...Pupsnap shows up in MoManager, but when clicked, it exits with an error....

Can you upload this version please?
I'd like to see this error.

.... and maybe you can convince radky to use internationalized versions

Attached is the pot file.

Here are gettext versions of PupSnap, PupShutdown and PupClockset:
http://www.puppylinuxstuff.meownplanet.net/vicmz
Rodin.s gettexted an older version of PupControl for Slacko, but right now I'm posting from mobile so I'll look for it later.
Radky says the GUI of his apps gets too expanded when translated, that's why he usually offers separate gettext versions when available.
See also:
http://www.murga-linux.com/puppy/viewtopic.php?t=87264

vicmz wrote:...Radky says the GUI of his apps gets too expanded when translated, that's why he usually offers separate gettext versions when available.

...looks like radky has not really understood puppy's internationisation and gettext


..or maybe he just does not want his apps making the way into woof

At some point he is right. The GUI does expand -- when it's shown in a non-English language. At some places text doesn't fit the buttons (see pictures below), that's why PupClockset has abbreviations in the button labels, there are tooltips anyway.

I uploaded the PupControl gettexted by rodin.s (.pot included in the PET) to the same link above, along with a pupcontrol_pinstall.pot to translate the pinstall. There are also the PETs for DeskSetup 0.8 and WM Switcher 0.19 gettexted by rodin.s and L18L some time ago.

Thank you very much vicmz! Much appreciated.

Wouldn't it make sense a developer creates the GUI in such a way that it can accommodate the language strings from any language, no matter how long?
I confess that I have no idea how difficult this would be But some scripts/programs miraculously adopt to the length of my dutch translations, while others force me to write in almost shorthand to get everything fit in.

Something else now: wouldn't it be useful to create a new repository, containing a collection of ALL gettexted scripts/programs?
I can imagine the task of pup builders willing to internationalize not being very easy, as they have to find the gettexted versions.

As an example I discovered gettexted Psync in your repo, downloaded it and now my translation works again. The Psync version in Precise 5.7.1 is not internationalized.

So if we would have one place as "The Gettext Repo" things would likely be much easier for all involved.
It doesn't look like an impossible task to me...and I'm willing to help in its creation. What do you think?

Anyway, Victor, thanks again.!

vicmz wrote:At some point he is right. The GUI does expand -- when it's shown in a non-English language.

..and nothing is bad if/when it expands. It is good!

vicmz wrote:At some places text doesn't fit the buttons (see pictures below), that's why PupClockset has abbreviations in the button labels, there are tooltips anyway.

A good example how the translator can makes it fit (if he can)!
Good buttons are expandable: [img]http://murga-linux.com/puppy/viewtopic. ... h&id=71365[/img]

Bert wrote:...Wouldn't it make sense a developer creates the GUI in such a way that it can accommodate the language strings from any language, no matter how long?

That is how IT works these days.

Bert wrote:I confess that I have no idea how difficult this would be But some scripts/programs miraculously adopt to the length of my dutch translations, while others force me to write in almost shorthand to get everything fit in.

There will always be good ones and better ones.

Bert wrote:Something else now: wouldn't it be useful to create a new repository, containing a collection of ALL gettexted scripts/programs?
I can imagine the task of pup builders willing to internationalize not being very easy, as they have to find the gettexted versions.

All scripts should be internationalized (except developer's and translator's tools) in an international operating system.
That is: no white list.
But a black list would make more sense: all script that lack internationalization.

Bert wrote:Anyway, Victor, thanks again.!

Same from me

Puppy as an international operating system, that has been my goal since I have been around here and it is reached now.

Thus it does really make no sense (it is nonsense) to keep an internationized version additionally to a non-internationalized (US of America only) version.
I think it is better to treat the not yet internationalized apps as exception

edit
Argolance BarryK don570 mcevanw rcrsn51 SFS shinobar zigbert.... they all and others internationalize their apps...so there is hope that radky will follow

edit2
Programs and scripts that are not yet internationalized