(old)Puppy Linux Discussion Forum

LupQ has mtpaint-3.34.55 but some translations(.mo) are outdated.
Attached new mtpaint.pot. Call for the translations updated.

EDIT: Do not translate the lines '? ??% zoom'. Keep them blank because the character '%' makes trouble with gettext.

Thanks L18L.
There were 2 '>' characters in the de.po, fails xorgwizard.
Fixed and update lang_pack_de-0.2.pet.

Bonjour shinobar,

shinobar wrote:LupQ has mtpaint-3.34.55 but some translations(.mo) are outdated.
Attached new mtpaint.pot. Call for the translations updated.

I wonder if the translation work already done on version 3.31 (already present in mtpaint-3.31.mo) could be re-used just to save time and energy?
In other words, is the mtpaint-3.31.pot available somewhere?
Cheers, Charlie

charlie6 wrote:Bonjour shinobar,I wonder if the translation work already done on version 3.31 (already present in mtpaint-3.31.mo) could be re-used just to save time and energy?
In other words, is the mtpaint-3.31.pot available somewhere?

Thanks charlie.
There are .po files already for many langages.
But some are old. They can be updated with the new .pot file using tools like poedit.
Attached all .po files available and the new .pot file.

Hi Shinobar
thank you very much.
but now there is a failure in lupq509 in the menu
calcul is french, was Kalkulation?
(now posting from a tiny linux distro, being localized)
Cheers

L18L wrote:but now there is a failure in lupq509 in the menu
calcul is french, was Kalkulation?

Danke. Will be fixed.

Chinese and Korean now supported on LupQ!
Get lang_pack_cjk-lupq-0.1.sfs from here.
It is a combination of CJK languages, Chinese, Korean and Japanese.

It is provided as a SFS file because it is so large, maybe takes 110MB of RAM space if it was installed with PET.
Next link is a help how to apply SFS's: Add SFS File to Bootup(Puppy Linux FAQ)



Japanese users can use this SFS instead of the PET, lang_pack_ja-lupq-*.pet.
To switch from PET to SFS (if your system already installed lang_pack_ja-lupq-*.pet), follow next step:

1. Change the locale to en_US.
2. Unistall lang_pack_ja-lupq-*.pet.
3. Apply lang_pack_cjk-lupq-*.sfs
4. Change back the locale to ja_JP.UTF-8.

Russian language support on LupQ is now available.
Install lang_pack_ru-lupq-0.1.pet available from here.
Translation of browsers are not included in this PET.
Install localized browsers.

CONGRATULATIONS, now more than 10 languages

revised markup of help files
puppyhelp now uses default browser

edit
fixed a bug (mine) in puppyhelp
(see lupq quickset)

L18L wrote:puppyhelp now uses default browser

Thanks L18L. Using default browser is good.
'L=${LANG:0:2}' is not sufficient, for example for pt_PT and pt_BR.

yes, you are right.
delete above line and take this as the last lines of puppyhelp edited
or even better: will support 3-letters-languages, too.

Portuguese language(pt_PT and pt_BR) support now available.
Install lang_pack_pt-lupq-0.1.pet available from here.
Restart X to enable ROX-Filer translation.
Translation of browsers are not included in this PET.
Install localized browsers.

Desktop translations are not yet available. Calling for your contribution.

Italian language support now available.
Install lang_pack_it-lupq-0.1.pet available from here.
Restart X to enable ROX-Filer translation.
Translation of browsers are not included in this PET.
Install localized browsers.

Desktop translations are not yet available. Calling for your contribution.

Where can I find 'the original' package in English to start translate it into Bulgarian? I cannot use russian (although it is simmilar in writing to bulgarian) or any other cyrillic language script. I can use the spanish also but I'd like the original english. Thanks in advance.

adXok wrote:Where can I find 'the original' package in English to start translate it into Bulgarian? I cannot use russian (although it is simmilar in writing to bulgarian) or any other cyrillic language script. I can use the spanish also but I'd like the original english. Thanks in advance.

Thanks for the cooperation.
Please look through the top post of this topic.
As for the desktop and the gettext'ed scripts, the .pot files are at /usr/share/doc/nls.
For the menus, /usr/share/desktop-directories, /usr/share/applications, and etc.

Hello adXok,

adXok wrote:

I cannot use russian (although it is simmilar in writing to bulgarian) or any other cyrillic language script.

Yes, the first is bulgarian (the cyrillic script) and Google has done really good job there although it is a simple sentance.

shinobar, thank you I'll see what can be translated by me.

shinobar wrote:Portuguese language(pt_PT and pt_BR) support now available.
Install lang_pack_pt-lupq-0.1.pet available from here.
Restart X to enable ROX-Filer translation.
Translation of browsers are not included in this PET.
Install localized browsers.
Desktop translations are not yet available. Calling for your contribution.

Shinobar,

There is a group of Brazilian translators willing to port puppy to Brazilian Portuguese (including scripts, documentation...). We would like to see our efforts included to the official Puppy Distribution. We are afraid of putting all our efforts in a fork of the original project that may eventually be discontinued.

1) Are there any plans or efforts to merge Lucid Puppy and Lucid Puppy Quickset Edition in the future?

2) Why is Quickset Edition easier to translate than the main project?

3) Finally, if we decide to translate the quickset edition, where can we find pragmatic instructions on how our team should proceed? Perhaps we should make the instructions, but then we need to understand how to deal with the .pot, .po and .mo files - it is not clear for us. (we are considering using Transifex as a translation management platform).

Thanks,
RPP

www.puppybrasil.org

Olá, rpp!
Primeiro de tudo, nós comemoramos o início do projeto que você, e gostaria de expressar nossos sentimentos de acolhida e apoio.

1) Are there any plans or efforts to merge Lucid Puppy and Lucid Puppy Quickset Edition in the future?

Depends on your activity.
For example. you know the LupQ-511 supports brazilian 'br' keyboards but Lupu-511 does not.
Next Lupu-5.2 may support 'br' by the 'Personalize Settings, but it is broken when you go through the xorgwizard.
Barry and Playdayz have open mind, but they may not know what the things are going at the opposite side of the globe.
You need to claim what you need at the development stage, like wary-098 or luci-23x.

2) Why is Quickset Edition easier to translate than the main project?

The lang_pack_pt-lupq-0.1.pet is applicable both with LupQ and with Lupu. Try Lupu-511 with lang_pack_pt-lupq-0.1.pet installed.
You need not wonder which should you choice for the project between LupQ or Lupu. Your target shall be adding more stuff on the lang_pack_pt-lupq.
As for the desktop and menu, LupQ has its original mechanism but does not harm the Lupu.
If you are content with the mechanism LupQ takes, you can make a movement for the future Puppy to take the same or similar mechanism.

3) Finally, if we decide to translate the quickset edition, where can we find pragmatic instructions on how our team should proceed?Perhaps we should make the instructions, but then we need to understand how to deal with the .pot, .po and .mo files - it is not clear for us.

I have no instructions how you drive your project. The LupQ itself has no plan to move to the Transifix, but you can use it with your project.
I hope someone take care to make a snapshot of the files and to package as lang_pack_pt-lupq-xxx.pet, and to post it here.
Again, the pet is applicable for the both users running LupQ or Lupu.

Abraço!