official (momanager) language packs

For efforts in internationalising Puppy and solving problems in this area
Post Reply
Message
Author
User avatar
L18L
Posts: 3479
Joined: Sat 19 Jun 2010, 18:56
Location: www.eussenheim.de/

urxvt

#106 Post by L18L »

Bert wrote:Here's a screenie.

Top of it is also top of my screen.

Btw, the Alt + left mouse key pressed does not work here. It works for all other windows, but not for the Momanager search result window.
Thanks for describing this...

...I could reproduce it having changed in urxvtset

Code: Select all

Borderless=On
That is why there is no top bar to right click or X :lol:

I will fix this soon.

User avatar
L18L
Posts: 3479
Joined: Sat 19 Jun 2010, 18:56
Location: www.eussenheim.de/

Re: urxvt

#107 Post by L18L »

L18L wrote:...I will fix this soon.
fixed

Search result window is always opened "Borderless=Off"
(..and switched back if it had been "On")

edit
momanager-20130620.pet deleted
please use recent pet at http://www.murga-linux.com/puppy/viewto ... &start=137
Attachments
momanager_tooltip_search.png
search something to get a search result in console
(6.87 KiB) Downloaded 728 times
Last edited by L18L on Wed 16 Oct 2013, 16:07, edited 2 times in total.

User avatar
Bert
Posts: 1103
Joined: Fri 30 Jun 2006, 20:09

#108 Post by Bert »

Hosla IT rocks!

Image

Thanks!
[url=http://pupsearch.weebly.com/][img]http://pupsearch.weebly.com/uploads/7/4/6/4/7464374/125791.gif[/img][/url]
[url=https://startpage.com/do/search?q=host%3Awww.murga-linux.com%2F][img]http://i.imgur.com/XJ9Tqc7.png[/img][/url]

User avatar
don570
Posts: 5528
Joined: Wed 10 Mar 2010, 19:58
Location: Ontario

#109 Post by don570 »

I have been using the forked momanager and I like it :lol:

I put the following lines in the front section of script and this gives
the version number and a crude help screen if the script is run from
the terminal. It would be worthwhile to insert.

Code: Select all

APPVERSION="130625"
while [ $# != 0 ]; do # check options added to momanager
	I=1
	while [ $I -le `echo $# | wc -c` ]; do 
		case $1 in	
		    -r|--run) shift; shift; break; break;;
   		    -v|--version) echo momanager $APPVERSION; exit;;
			*) echo '
Usage: momanager [Options]

Options 
  -r | --run        Run option
  -h | --help       Display this help message
  -v | --version    Display momanager version'; exit;;
		esac
		shift
		I=$[$I+1]
	done
done


User avatar
don570
Posts: 5528
Joined: Wed 10 Mar 2010, 19:58
Location: Ontario

#110 Post by don570 »

I modified the recent fork of L18L



Image
Attachments
momanager-20130626.pet
modified for terminal help
(29.37 KiB) Downloaded 525 times

User avatar
L18L
Posts: 3479
Joined: Sat 19 Jun 2010, 18:56
Location: www.eussenheim.de/

FFMM

#111 Post by L18L »

I have decided to wait until Barry will have continued further development of momanager just because I do not like ever lasting forks. 8)

One thing that everybody should do right now is insert a sync command in momanager, see post 8 at http://www.murga-linux.com/puppy/viewtopic.php?t=87801 :wink:

... and maybe publish some langpacks?
Don't wait until it is finished, Puppy will always be quicker changing than one can follow translating.

What I'd like to do next?
A Belge edition containing the three official languages of this country.
and quick change of language without restart of X-Server.... :idea:

User avatar
L18L
Posts: 3479
Joined: Sat 19 Jun 2010, 18:56
Location: www.eussenheim.de/

FFMM

#112 Post by L18L »

Code: Select all

#130806 L18L sync added
#131001 L18L transLANG added to output of search (ex: mo files under transLANG=fr not fr_BE)
#131002 L18L last edited mo file at top of list # Bert's old wish for edit_mo
edit
momanager-20131002.pet deleted
please use recent pet at http://www.murga-linux.com/puppy/viewto ... &start=137
Attachments
ffmm.png
(180.93 KiB) Downloaded 540 times
Last edited by L18L on Wed 16 Oct 2013, 16:09, edited 1 time in total.

User avatar
Bert
Posts: 1103
Joined: Fri 30 Jun 2006, 20:09

#113 Post by Bert »

Great, a momanager update after all these months!

What's more, it seems to work just fine. 8)

Good to see the version date in the popup!

I will continue to send L18L nagging PM's about details in FFMM, until he accepts his fate to develop it to near-perfection. :twisted:

Momanager is a wonderful tool, but it sure has a temperament of its own. Yesterday and today, after editing and saving a file in the left .mo column, the top drop-down menu on the left side displayed "empty"... That is a bit nerve wracking after several months of translation work :lol: Luckily, closing and restarting MoManager restores the left translated scripts column.

What I would like to see, if possible, is the Momanager-dump not being spread all over /root, but simply being collected in a folder e.g.' /root/momanager-files'
That would make handling those copies so much easier and would keep /root clean and easier to manage.

I'm getting close to releasing a new Dutch langpack and wonder what to do: just publish it somewhere in the cloud, or send it to Barry? Barry wrote he would continue to do Woof-maintenance, but does that also include langpacks? I got the impression he only wants to concentrate on the essential system-stuff...

A Big Thank You, L18L!!
Very grateful for your ongoing work!
[url=http://pupsearch.weebly.com/][img]http://pupsearch.weebly.com/uploads/7/4/6/4/7464374/125791.gif[/img][/url]
[url=https://startpage.com/do/search?q=host%3Awww.murga-linux.com%2F][img]http://i.imgur.com/XJ9Tqc7.png[/img][/url]

User avatar
L18L
Posts: 3479
Joined: Sat 19 Jun 2010, 18:56
Location: www.eussenheim.de/

momanager

#114 Post by L18L »

Bert, thank you for your continous feedback.
Bert wrote:...Yesterday and today, after editing and saving a file in the left .mo column, the top drop-down menu on the left side displayed "empty"... That is a bit nerve wracking after several months of translation work :lol: Luckily, closing and restarting MoManager restores the left translated scripts column.
That is the disadvantage of the "Fast" component.
Fast but False if you should accidently (root can do it) delete the file /tmp/momanager/YESMO_XML.
Bert wrote:What I would like to see, if possible, is the Momanager-dump not being spread all over /root, but simply being collected in a folder e.g.' /root/momanager-files'
That would make handling those copies so much easier and would keep /root clean and easier to manage.
These files are for translators who are not maintainer of a language pack. Ex: You translate something of zigbert's or rcsnr51' scripts and send just this to him.
Will be in next version so you can safely delete all all of them in one click. :lol:
Bert wrote:I'm getting close to releasing a new Dutch langpack and wonder what to do: just publish it somewhere in the cloud, or send it to Barry? Barry wrote he would continue to do Woof-maintenance, but does that also include langpacks? I got the impression he only wants to concentrate on the essential system-stuff...
Language packs are essential for woof in my humble opinion :wink:

A language pack should add a language to a puppy system
and not replace English or another language by a language.
Therefore we will have to change something with the help files.....

Other ideas see somewhere at Barry's blog....
:)

User avatar
vicmz
Posts: 1262
Joined: Sun 15 Jan 2012, 22:47

latest ffmm

#115 Post by vicmz »

Thank you L18L. Fast and Furious Marilyn Monroe is more and more sexy. :lol:
Only detail to report: marks for up-to-date and needs-check scripts are confusing to me - round darts are meant to be for scripts that need a revision, but I open them and most of the time they are up to date, while three dots are for up to date scripts but sometimes a check is actually required. Apart from that it works really well to me. :D
[url=http://murga-linux.com/puppy/viewtopic.php?t=76948]Puppy Linux en español[/url]

User avatar
L18L
Posts: 3479
Joined: Sat 19 Jun 2010, 18:56
Location: www.eussenheim.de/

Re: latest ffmm

#116 Post by L18L »

vicmz wrote:Thank you L18L. Fast and Furious Marilyn Monroe is more and more sexy. :lol:
Only detail to report: marks for up-to-date and needs-check scripts are confusing to me - round darts are meant to be for scripts that need a revision, but I open them and most of the time they are up to date, while three dots are for up to date scripts but sometimes a check is actually required. Apart from that it works really well to me. :D
need a revision: this is just a decision made frm date of script and date of mo file.
When I found one and checked and everything was ok
then I edited the date and said OK to "create mo file"
its state changed has been changed to up-to-date then.
If you cancel because you have not made changes then it will continue to be shown as "need a revision".

up-to-date-scripts that require a check: nobody is perfect, so also the last translator and FFMM. My thougts are:
- users can and will contribute such things.
- if the pot file is in the system then this file is used and not the one automatically created from the script. Then you never will get an actual translation. Only alsaconf.pot is necessary, no other pot file for script.
Sorry I cannot list these because I have deleted them.
Maybe you find them and report to Barry: these files must not stay in devx.

Thank you for reporting and have a nice day :D

User avatar
Bert
Posts: 1103
Joined: Fri 30 Jun 2006, 20:09

#117 Post by Bert »

L18L wrote:Sorry I cannot list these because I have deleted them.
I haven't :wink:
I think we discussed this before...I remember not daring to delete it all, because there could be binaries in them. (scripts, binaries: it all looks the same to me :oops: )
Attachments
image-1.png
/usr/share/doc/nls
(51.55 KiB) Downloaded 450 times
[url=http://pupsearch.weebly.com/][img]http://pupsearch.weebly.com/uploads/7/4/6/4/7464374/125791.gif[/img][/url]
[url=https://startpage.com/do/search?q=host%3Awww.murga-linux.com%2F][img]http://i.imgur.com/XJ9Tqc7.png[/img][/url]

User avatar
L18L
Posts: 3479
Joined: Sat 19 Jun 2010, 18:56
Location: www.eussenheim.de/

pot files in devx

#118 Post by L18L »

Bert wrote:I think we discussed this before...I remember not daring to delete it all, because there could be binaries in them. (scripts, binaries: it all looks the same to me :oops: )
Thank you, Bert
I have checked them now.
What looks different?

in aqualung/aqualung.pot:

Code: Select all

#: src/about.c:97 src/gui_main.c:2783
msgid "About"
msgstr ""
references to *.c source
:arrow: must stay because MoManager cannot create pot file for c source

in alsaconf/alsaconf.pot:

Code: Select all

#: alsaconf:54
msgid "Yes"
msgstr ""
:arrow: script
(alsaconf must stay because MoManager cannot create pot file, see README.txt)

What is wrong?
MoManager had been advised to use a pot or a po file if found in the file system
if not then try to create a pot file from the actual script.
So if we have a pot file for a script from which this automatic creation is successful then we must not have a pot file stored.

I have posted the following list to Barry so that in future builds of devx these would be no more included.

You can safely delete them pasting the following

Code: Select all

cd /usr/share/doc/nls
for d in  ffconvert freememapplet_tray get_libreoffice grub4dosconfig peasyscan pmusic pupmd5sum.sh welcome1stboot.sh; do
    rm -r $d
done
cd -
to a console and press ENTER key.

edit
I should include this into next version of momanager :idea:

User avatar
vicmz
Posts: 1262
Joined: Sun 15 Jan 2012, 22:47

Re: latest ffmm

#119 Post by vicmz »

L18L wrote:if the pot file is in the system then this file is used and not the one automatically created from the script. Then you never will get an actual translation. Only alsaconf.pot is necessary, no other pot file for script.
Sorry I cannot list these because I have deleted them.
Maybe you find them and report to Barry: these files must not stay in devx.
They aren't in the devx, they're in langpack_es. :oops: So I have to remove everything but the POT files for scripts that actually need them. I'll do it for the next langpack version. Vielen Dank! :D

**Edit**
Woooah wait! I have only a few of those. Many of the scripts I checked don't even have a .pot file at /usr/share/doc/nls/ ! :shock:
Allright, never mind, :lol: it's not that important, for FFMM actually works.
[url=http://murga-linux.com/puppy/viewtopic.php?t=76948]Puppy Linux en español[/url]

User avatar
vicmz
Posts: 1262
Joined: Sun 15 Jan 2012, 22:47

FFMM

#120 Post by vicmz »

rerwin wrote:I have uploaded a set of 4 ISO files [of Lucid Puppy 2013] labeled as 20131004. They are available at the link at the original download posting, which explains the updates:
http://www.murga-linux.com/puppy/viewto ... 108#726108

The main improvements are:
  • - standardization of the mounted drive icons to provide the "X box" for unmounting (yay!)
    - addition of momanager for internationalization support.

Please tell me if I need to add more to assist translation. Although it is not practical to internationalize everything in lupu, I am willing to add packages of internationalized versions of specific applications, if they are not dependent on kernels later than 2.6.33. Just request them.
Richard

User avatar
L18L
Posts: 3479
Joined: Sat 19 Jun 2010, 18:56
Location: www.eussenheim.de/

Re: latest ffmm

#121 Post by L18L »

vicmz wrote:... I have only a few of those. Many of the scripts I checked don't even have a .pot file at /usr/share/doc/nls/ ! :shock:
Allright, never mind, :lol: it's not that important...
For me it is important for understanding (original!) MoManager:
- creates actual pot file from actual script (xgettext)
- creates po file from pot file (msginit)
- merges existing translations in mo file (msgmerge)

Just because a alsaconf.pot could not be created automatically the rule was introduced:
if a pot file exists in /usr/share/doc/nls/<app>/ then it will be used.

... and there is the danger that the pot file is not actual any more.

So the important rule (for developer) simply is:
If momanager can create the pot file (the developer or the first translator will you see it running momanager) then do NOT store a pot file for this script.

They are in devx :wink:

Code: Select all

# pwd
/mnt/+mnt+home+devx_precise_5.7.1.sfs/usr/share/doc/nls
# 
# ls
alsaconf            grub4dosconfig  notecase          proxy-setup     xarchive
ffconvert           gtkam           parted            pwallpaper
freememapplet_tray  hardinfo        pdiag             retrovol
gecko-mediaplayer   jwm             peasyscan         ROX-Filer
gphoto2             network_tray    powerapplet_tray  welcome1stboot
# 
..and you may have additionaly others, too.

Thanks for the feedback which was good for clearing this issue. :)

akarui.tenshi
Posts: 4
Joined: Tue 30 Oct 2012, 01:22

translation confusion...

#122 Post by akarui.tenshi »

Good morning,
I found a serious error when using MoManager (maybe is not an error)... I tried to create a language pack for the language "Català" (ca_ES) and everything was alright, then i found a language pack in Portuguese. However this language pack is in the Portuguese of Brazil (pt_BR) and not in Portuguese of Portugal (pt_PT), so I tried to modify it, but translations pt_BR and pt_PT can not cohabitate in the same language pack, because MoManager recognizes both languages ​​just as 'pt'

User avatar
Bert
Posts: 1103
Joined: Fri 30 Jun 2006, 20:09

Re: translation confusion...

#123 Post by Bert »

akarui.tenshi wrote:Good morning, However this language pack is in the Portuguese of Brazil (pt_BR) and not in Portuguese of Portugal (pt_PT), so I tried to modify it, but translations pt_BR and pt_PT can not cohabitate in the same language pack, because MoManager recognizes both languages ​​just as 'pt'
Good morning akarui.tenshi,

I think it's a good thing pt_BR and pt_PT cannot cohabitate in the same language pack...
You can make the choice what the target language has to look like : 'pt', or pt.BR' or 'pt_PT'. This choice is made in "Preferences" (bottom of momanager window. ("transLANG=...")

Hope this helps.
[url=http://pupsearch.weebly.com/][img]http://pupsearch.weebly.com/uploads/7/4/6/4/7464374/125791.gif[/img][/url]
[url=https://startpage.com/do/search?q=host%3Awww.murga-linux.com%2F][img]http://i.imgur.com/XJ9Tqc7.png[/img][/url]

User avatar
L18L
Posts: 3479
Joined: Sat 19 Jun 2010, 18:56
Location: www.eussenheim.de/

Re: translation confusion...

#124 Post by L18L »

Goodday and welcome :D
akarui.tenshi wrote:... i found a language pack in Portuguese. However this language pack is in the Portuguese of Brazil (pt_BR) and not in Portuguese of Portugal (pt_PT), so I tried to modify it, but translations pt_BR and pt_PT can not cohabitate in the same language pack, because MoManager recognizes both languages ​​just as 'pt'
languagepack_pt-2013 located at
http://distro.ibiblio.org/quirky/pet_packages-noarch/
made by forum member vicmz
has both

Code: Select all

# pwd
/initrd/mnt/dev_save/langpack_pt-20130110/usr/share/locale
# 
# ls
pt_BR  pt_PT
#
and just pt, ex: /usr/local/apps/ROX-Filer/Messages/pt/LC_MESSAGES

Thus they do exist (maybe manually created by vicmz [hello vicmz :D ] )
.. and momanager can only, how Bert wrote, create
pt or pt-BR if LANG=pt_BR
pt or pt-PT if LANG=pt_PT

...maybe mismatch between _ and - :?:

The question remains: Can you use them and how?

Theory is:
If your LANG is pt_PT then pt_PT is used else pt
If your LANG is pt_BR then pt_BR is used else pt

I am seeing differences in
/usr/local/apps/ROX-Filer/Messages/pt-PT/LC_MESSAGES/ROX-Filer.mo 78k
/usr/local/apps/ROX-Filer/Messages/pt-BR/LC_MESSAGES/ROX-Filer.mo 102k

( /usr/local/apps/ROX-Filer/Messages/pt-PT/LC_MESSAGES/ROX-Filer.mo could be just a link to ../pt/...)

@akarui.tenshi,
your experience in using with LANG=pt-PT vs. pt-BR?

akarui.tenshi
Posts: 4
Joined: Tue 30 Oct 2012, 01:22

Re: translation confusion...

#125 Post by akarui.tenshi »

L18L wrote:Goodday and welcome :D
hello, I have been here for a while, however, only now I decided to become an active member... :p
L18L wrote:languagepack_pt-2013 located at
http://distro.ibiblio.org/quirky/pet_packages-noarch/
made by forum member vicmz
Yes, it's the pt_Br language pack...

@akarui.tenshi,
your experience in using with LANG=pt-PT vs. pt-BR?[/quote]

My experience? well... for me, the english interface is ok... but for a portuguese users there are differences between the pt_BR and the pt_PT ( an example: "file" in pt_BR is "Arquivo" but in pt_PT is named "Ficheiro")... the same happens to the catalan of spain (language that i also speak) and the catalan spoken in some parts of France...
I know a little bit of programming and i'm trying to understand how MoManager and puppy linux manage the translations...
Bert wrote: I think it's a good thing pt_BR and pt_PT cannot cohabitate in the same language pack...
You can make the choice what the target language has to look like : 'pt', or pt.BR' or 'pt_PT'. This choice is made in "Preferences" (bottom of momanager window. ("transLANG=...")
when i choose pt_PT or pt_BR, the .desktop files work fine, but some translations like the 'sss' doesn't work

Post Reply