(old)Puppy Linux Discussion Forum

Posted: **Tue 21 May 2013, 11:33**

L18L wrote:...Same procedure as with binaries....

Not exactly

find in /usr/sbin/momanager the line:
no_to_yes $CACHE/NOMO_XML "${SCRIPTS}" $CACHE/YESMO_XML # update YESMO_XML NOMO_XML #130520

and append:

for ASCRIPT in $SCRIPTS ; do #130522
sed -i "s#(${ATEXTDOMAIN}#(${ATRANSLANG} ${ATEXTDOMAIN}.mo#" $CACHE/YESMO_XML #130522
done #130522

Hope that helps
not hope I am sure

edit

or simply use new momanager.pet: http://www.murga-linux.com/puppy/viewto ... 9&start=50

edit
or simply use newer momanager.pet: http://www.murga-linux.com/puppy/viewto ... 9&start=57

edit
or simply use newer momanager.pet: http://www.murga-linux.com/puppy/viewto ... 9&start=85

Posted: **Tue 21 May 2013, 14:52**

For your convenience here is now:

fast momanager-20130522

why fast and how fast?

All drop down lists (left: translated, right: not translated) are created just once. Time for this was about 2 minutes on my (1.5GHz) box.

When a translation was being created then the entry is moved from right to left. Time for displaying the main window was about 2 seconds on my (1.5GHz) box.

As fixmenus is run when create/edit menu entries a slightly faster version of fixmenus is also included. It is faster just by using some builtin shell commands instead of echo grep cut (thanks technosaurus

)

edit
attachment (32 times downloaded) deleted
simply use new momanager.pet: http://www.murga-linux.com/puppy/viewto ... 9&start=50
edit
or simply use newer momanager.pet: http://www.murga-linux.com/puppy/viewto ... 9&start=57
edit
or simply use newer momanager.pet: http://www.murga-linux.com/puppy/viewto ... 9&start=85

Posted: **Tue 21 May 2013, 17:05**

I am SO HAPPY I could kiss you!!

Everything just works now and INCREDIBLY fast.

Let the translation fun begin...

Well done L18L (and in record time!)

THANK YOU

Posted: **Tue 21 May 2013, 17:48**

Would not have got it without your help.

Next time I should do more testing before publishing

I am hoping it can make it into woof now.
See http://bkhome.org/blog2/?viewDetailed=00229

Posted: **Tue 21 May 2013, 19:21**

One strange thing about MoManager is: when I choose to edit xorgwizard I got lines from xorgwizard-cli (has different textdomain) in the po-file.

Posted: **Wed 22 May 2013, 12:26**

rodin.s wrote:One strange thing about MoManager is: when I choose to edit xorgwizard I got lines from xorgwizard-cli (has different textdomain) in the po-file.

Really strange.

Why different TEXTDOMAINs

Code: Select all

# for AFILE in `ls xorgwizard*.mo`; do file $AFILE  ;done
xorgwizard-cli.mo: GNU message catalog (little endian), revision 0, 91 messages
xorgwizard.mo: GNU message catalog (little endian), revision 0, 181 messages

56 duplicate message definitions...

Let us make one TEXTDOMAIN=xorg for both xorgizards?

# xgettext -o xorg.pot --language=shell /usr/sbin/xorgwizard /usr/sbin/xorgwizard-cli

merged my already translated po files, edited some fuzzy's and got:

# file xorg.mo
xorg.mo: GNU message catalog (little endian), revision 0, 218 messages

One TEXTDOMAIN would be really better

Posted: **Thu 23 May 2013, 00:00**

Review:

I used the new Momanager to internationalize 'alien2puppy'
and it worked nicely

__________________________________

Posted: **Fri 24 May 2013, 22:00**

Hello everyone

I tried momanager-20130522.tar.gz
in Precise 5.6

I extracted to /

I tried to edit an existing .mo and got an error message

then back to the main GUI all scripts that didn't actually have a .mo file where moved to the list of those that do have

after that I restored the original momanager files

and everything worked as usual

I tried in Racy 5.5 and got the same results

I wonder what did I do wrong since all of you are saying it works nice on your systems

Posted: **Fri 24 May 2013, 22:31**

That's strange vlcmz.

Just to be sure: did you really download and install the latest MoManager (20130522), because your problems are exactly what was wrong in earlier editions.

I'm not doubting your intelligence with this question

Only want to exclude always-possible human errors.

Best regards.

Posted: **Fri 24 May 2013, 23:06**

Yes, I did download that one. But there's something strange: I have another one that instead of 05-22 says 05-29

The latter I didn't test yet, I downloaded 05-22 directly from this thread and used as-is.
OK, too much stress at work, maybe.

I'm already planning some holidays.

Posted: **Fri 24 May 2013, 23:20**

Don't use the 05-29 (the 29 was a typo, should have been 19)

I cannot help you any further. All I can say is version 20130522 is the first one running without errors here. I've used it 3 days now and am as excited as I was after a few hours testing. The weeks before 20130522 were not easy, lots of problems I didn't understand, but do now, because the latest version solved all those problems.

For the record: I'm still running Precise 5.5, That's one difference with your 5.6.
(which I intend to install tomorrow)

I'm sure L18L will come to the rescue shortly...

Good luck!

Posted: **Sat 25 May 2013, 09:26**

vicmz wrote:...I tried to edit an existing .mo and got an error message...

Reveal the name of the .mo file, or better name of the executable and it might become reproducible.

Posted: **Sat 25 May 2013, 17:52**

don570 wrote:Review:

I used the new Momanager to internationalize 'alien2puppy'
and it worked nicely

__________________________________

Thanks for the review

Another issue was edit Xdialog.po in momanager

Find in /usr/sbin/momanager line which contains
Code:
LANG=${ORIGLANG} rxvt -e intltool-update --dist --gettext-package=${ATEXTDOMAIN} --output-file=${ATEXTDOMAIN}.po ${ATEXTDOMAIN}1

put a # at beginning of that line so it looks like:
Code:
#LANG=${ORIGLANG} rxvt -e intltool-update --dist --gettext-package=${ATEXTDOMAIN} --output-file=${ATEXTDOMAIN}.po ${ATEXTDOMAIN}1
and append the following line:
Code:
LANG=${ORIGLANG} rxvt -e msgmerge ${ATEXTDOMAIN}1.po ${ATEXTDOMAIN}.pot --output-file=${ATEXTDOMAIN}.po ; #130525

..and also ROX-Filer can be edited if you apply this change.

edit
or simply use new momanager.pet: http://www.murga-linux.com/puppy/viewto ... 9&start=50
edit
or simply use newer momanager.pet: http://www.murga-linux.com/puppy/viewto ... 9&start=57
edit
or simply use newer momanager.pet: http://www.murga-linux.com/puppy/viewto ... 9&start=85

Posted: **Sat 25 May 2013, 21:11**

I just noticed a little oddity:

The latest edited new (right-side) files no longer show up on top of the left side (files that have a mo) column.

Discovered this while translating the universal installer. (30% done, phew..

)

Not a big deal, but I suppose L18L's idea was to keep the latest files on top of the list, which is indeed very handy for quick corrections)

Posted: **Sun 26 May 2013, 07:52**

Bert wrote:The latest edited new (right-side) files no longer show up on top of the left side (files that have a mo) column.

If you restart momanager then the order is as always is.

Bert wrote:I suppose L18L's idea was to keep the latest files on top of the list, which is indeed very handy for quick corrections)

Putting that entry at top of the list is the easiest way for coding
and , yes, it is very handy. But "latest created files on top" is only true in a "session" of momanager.

Appears it is more difficult to explain than to code.

Posted: **Fri 31 May 2013, 15:56**

I fired up MoManager maybe for the first time this week and, feeling a bit tired, decided to translate a mini app first: pEqualizer (just a few lines

).

Translation went well, but pEqualizer did not appear on top of the left column drop down box. Instead, there was a whole list of Pburn and Pmusic entries on top. Both apps should have remained on the right side, as I haven't even started translating them. (Not all the Pburn/Pmusic entries had moved to the left, roughly 50% had stayed on the right side)

When I opened one of the Pburn entries on the left side I was greeted with the dreaded BAD NEWS popup again....

So...maybe vlcmz's report was correct and I've been just lucky not to experience this problem before.

After closing MoManager, shaking my fist at Tradir (*), the translators' patron saint, and two strong coffees later, I reopened MM and everything looked normal again:

pEqualizer to the left alphabetically, Pburn and Pmusic back to the right side.

This also relates to my last post above, I accepted your reply but kept feeling it happened before closing MoManager. (Haven't had time to try and reproduce it.)

(*)

Posted: **Fri 31 May 2013, 22:28**

Bert wrote:Don't use the 05-29 (the 29 was a typo, should have been 19)

This is what actually happened

And the app was a gettext version of PupSnap 1.8, which I could translate as usual with 05-22.

Thanks, Bert and L18L

Not so off-topic, can momanager be ported to older Puppies? I've received requests for localizing Lucid 528-005 and Puppy 431, it'd be easier to have momanager as a more organised method for translating these.

Posted: **Sat 01 Jun 2013, 09:44**

vicmz wrote:..can momanager be ported to older Puppies?..

I am sure it could. But not by me.

Just one hint:
Momanager identifies internationalized scripts by the line:

Code: Select all

export TEXTDOMAIN=

Why not use the new Puppies built with woof2 ?
... and improve them if there should be anything wrong in them ?

edit
waryq and lupq exist

http://www.murga-linux.com/puppy/profil ... le&u=17722

Posted: **Sat 01 Jun 2013, 09:52**

Bert wrote: I fired up MoManager maybe for the first time this week and, feeling a bit tired, decided to translate a mini app first: pEqualizer (just a few lines ).

Translation went well, but pEqualizer did not appear on top of the left column drop down box. Instead, there was a whole list of Pburn and Pmusic entries on top. Both apps should have remained on the right side, as I haven't even started translating them. (Not all the Pburn/Pmusic entries had moved to the left, roughly 50% had stayed on the right side)

When I opened one of the Pburn entries on the left side I was greeted with the dreaded BAD NEWS popup again....

So...maybe vlcmz's report was correct and I've been just lucky not to experience this problem before.

After closing MoManager, shaking my fist at Tradir (*), the translators' patron saint, and two strong coffees later, I reopened MM and everything looked normal again:

pEqualizer to the left alphabetically, Pburn and Pmusic back to the right side.

This also relates to my last post above, I accepted your reply but kept feeling it happened before closing MoManager. (Haven't had time to try and reproduce it.)

(*)

Thanks for reporting "bad news"

I will try to reproduce it now:

I rename my LC_MESSAGES/pequalizer.mo
and launch momanager

...wait a moment

/usr/local/pequalizer/func and
/usr/local/pequalizer/pequalizer at right side.

now create /usr/local/pequalizer/pequalizer
translate 2 phrases and

/usr/local/pequalizer/func and
/usr/local/pequalizer/pequalizer at left side.

Now edit /usr/local/pequalizer/func
and..... no bad news.

/usr/local/pequalizer/pequalizer wrote: # 20121028 (c) 01micko@gmail.com and zigbert@murgalinux.com 2011-2012
...
VERSION=0.9.0

Do we use the same version of momanager?
Here the last comments of the version I am using at the moment:

#130503 test if .po file changed.
#130503 L18L: rename AppInfo.xml to AppInfo.xml.in for langpack
#130505 L18L: quick version: caching variables in CACHE/... from 2m to 2s
#130512 acknowledge new translators, deleting /tmp/momanager
#130519 L18L bug fix: instead of APKGNAME use ASCRIPT, DESKFILE, XMLFILE, ABIN; code for sss and menu categories unchanged
#130520 L18L bug fix: multiple scripts for 1 TEXTDOMAIN
#130521 L18L bug fix binaries, update NOCNT,YESCNT
#130522 L18L bug fix 1 line NOXML_XML and multiple scripts
#130525 L18L replace intltool-update by msgmerge

Hope that helps
or how gcmartin uses to write
Here to help

[edit] Close momanager, restart and wait some minutes is good.
But I really liked to make fast momanager useable
that is: not only fast but also precise

.

Posted: **Sat 01 Jun 2013, 11:41**

Thank you!

The pEqualizer version is the same: v.0.9.0

Momanager is 20130522 as it left the factory...

I don't have

Code: Select all

#130525 L18L replace intltool-update by msgmerge

I presumed that was the code in your reply to Don570...so added that now.

Will let you know how it goes.

chüss.

(old)Puppy Linux Discussion Forum

official (momanager) language packs

fast momanager

fast momanager

fast momanager

xorgwizard and xorgwizard-cli

Re: xorgwizard and xorgwizard-cli

momanager-20130522.tar.gz

Re: momanager-20130522.tar.gz

fast momanager

fast momanager

problem returns

momanager

Re: problem returns