Page 2 of 4
Posted: Sun 03 Oct 2010, 01:01
by shinobar
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.
Posted: Sun 03 Oct 2010, 14:24
by L18L
Code: Select all
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
Code: Select all
#
#[ "$F" != "" ] || F="/usr/share/doc/index.html"
F="$HELPDIR/${LANG:0:5}/index.html" # pt_BR
[ ! -f "$F" ] && F="$HELPDIR/${LANG:0:2}/index.html"
[ ! -f "$F" ] && F="/usr/share/doc/index.html"
exec $BROWSER "file://$F" &
or even better:
Code: Select all
#
#[ "$F" != "" ] || F="/usr/share/doc/index.html"
F="$HELPDIR/${LANG:0:5}/index.html" # pt_BR
[ ! -f "$F" ] && F="$HELPDIR/`echo $LANG | cut -d '_' -f1`/index.html"
[ ! -f "$F" ] && F="/usr/share/doc/index.html"
exec $BROWSER "file://$F" &
will support 3-letters-languages, too.
Portuguese support available
Posted: Mon 04 Oct 2010, 23:10
by shinobar
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 support available
Posted: Mon 04 Oct 2010, 23:36
by shinobar
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.
Posted: Sun 10 Oct 2010, 10:04
by adXok
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.
Posted: Sun 10 Oct 2010, 12:10
by shinobar
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.
Posted: Sun 10 Oct 2010, 14:46
by L18L
Hello adXok,
adXok wrote:
I cannot use russian (although it is simmilar in writing to bulgarian) or any other cyrillic language script.
Posted: Sun 10 Oct 2010, 19:38
by adXok
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.
Re: Portuguese support available
Posted: Tue 16 Nov 2010, 13:10
by rpp
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
Congratulação o projeto
Posted: Tue 16 Nov 2010, 23:47
by shinobar
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!
Posted: Wed 17 Nov 2010, 10:35
by Bert
rpp wrote: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.
Same problem here
I tried to understand the tools made available by Shinobar, wanting to contribute more translations for Dutch, but I failed.
From my point of view (
amateur translator), developer skills are needed to use the LupQ translation tools.
Which is a pity, because most people volunteering to help with the translations have linguistic talents, but have a hard time understanding devx, gettext, po, mo, pot and how these might be inter-related .;
It is already hard to find enough people willing to do translations. But with the added complexity, most of the potential translators will say "No thanks, not for me".
Posted: Wed 17 Nov 2010, 10:35
by Bert
Double post. Sorry.
poedit
Posted: Wed 17 Nov 2010, 14:17
by shinobar
Bert wrote:most people volunteering to help with the translations have linguistic talents, but have a hard time understanding devx, gettext, po, mo, pot and how these might be inter-related .;
Humm..
You can copy the .pot file to yourlang.po and edit it using text editor, but i recommend to use the
poedit or some tools.
I put the
poedit-1.4.2-3-i686.pet here. You need not devx.
Maybe we need proper documents, but it is easy once you run the poedit.
Re: Congratulação o projeto
Posted: Wed 17 Nov 2010, 18:16
by rpp
Thanks for your reply and support.
Now I am starting to glimpse the complexity of the translation process of Puppy. I was hoping to set up a translation system similar to the way ubuntu is translated. However there are only a few strings that can be translated using gettext, thus using Transifex or other tool won't necessarily help that much. Scripts must be translated individually withing its code, with manual version control and little automation. It that correct???
I have one suggestion:
Why not create a general "template" for translation that contain only the files that needs translation in its directory structure? Help from someone who has already been gone trough this trouble is greatly appreciated. Something like lang_template_pack_XX-lupq-xxx.tar.gz. This might motivate more people to start translating Puppy to other languages.
Each release of LupQ could be accompanied by such a file. How about that?
Thanks,
Rafael
Re: Congratulação o projeto
Posted: Thu 18 Nov 2010, 23:50
by shinobar
rpp wrote:there are only a few strings that can be translated using gettext,
Yes, you found the translation of Puppy is so complex that i need to describe long story on the top post of this topic.
We need to do translate the existing NLS and to make the scripts getting NLS. It may need long term effort.
As for the recent gettext'ed scripts, the .pot files are at /usr/share/doc/nls in LupQ.
Keep it up!
Hungarian language package
Posted: Thu 25 Nov 2010, 09:13
by gojko
Get Hungarian (Magyar) new language package from here:
lang_pack_hu-lupq-0.3.pet
Re: Hungarian language package
Posted: Thu 25 Nov 2010, 11:11
by shinobar
Re: Hungarian language package & two small problems
Posted: Thu 25 Nov 2010, 18:29
by gojko
shinobar wrote:Köszönöm
Én köszönöm!
I found two small problems:
- 1. Pmount start up, all right. Press the 'FRISS
Re: Hungarian language package & two small problems
Posted: Fri 26 Nov 2010, 08:50
by shinobar
- 1. Pmount start up, all right. Press the 'FRISS
Simple localization scripts
Posted: Fri 03 Dec 2010, 11:48
by gojko
Kon'nichiwa Shinobar!
3 small scripts, they are modified with your script. So they are to simple localization scripts:
glipper_shell, gparted_shell, mtpaintsnapshot.sh
Things are not great, but perhaps also can be used of other translators.
-gojko-