official (momanager) language packs

[L18L]

Interesting link. I have learned something new although I have some experience with gettext.
A bit offtopic but I was thinking about script that finds updated scripts. When script is updated mo-file sometimes should be updated too, if translation is changed. I was thinking about script that should compare date of a script a date of corresponding mo-file and if script is newer than mo-file then in should be in the list of updated scripts.

...done

Note,
_ and X are configurable
That is why config file /root/.config/momanager will be deleted and newly created.
...and you will have to edit your preferences once again.

Note2,
The mark X is not immediately changed to _ because fast momanager shall stay fast
At next new start of momanager these marks are-up-to-date.

[Bert]

Anyone else seeing this with FFMM-20130604?

What is FFMM-20130604?

Hmm, I'm just reporting what I'm experiencing, hoping it can be helpful.

[vicmz]

Problem: scripts from the right side, when clicked to edit, don't open in editor.

Editing existing translated scripts (left side): no problem.

Editing new XML (right): no problem.

When clicking a right side script, there's a short flashing window and then Momanager returns to its main page.

Anyone else seeing this with FFMM-20130604?

Back to the garden now

EDIT: 'preferences':

showINTRO=no
transLANG=nl
myEMAIL=bert@localpub

Same here for v2013-06-05, edit existing files works but create new doesn't, it just reloads Momanager.

[L18L]

Bert,
sorry, I really did not understand that abbreviation yesterday
Marilyn Monroe in Frankfurt/Main came to my mind

Victor,
thanks for confirming the bug

which is fixed in version 130606 now:
#130606 L18L bug fix create_mo, ~/.config/momanager edited

[Bert]

Thanks for the bug fix. It's working well now.

One little thing I just noticed after posting the Peasyglue translation:

Fast and Furious Marilyn Monroe looks at the pc's locale when giving a .mo its name. It does not 'see' the transLANG in preferences.

Peasyglue was translated with transLANG : nl

but this is the resulting archive: MoManager-nl_NL-peasyglue-1.4.tar.gz

(this, of course, has nothing to do with the new MoManager version)

[L18L]

Bert,

the little thing was 65 changes

But we can do it in 1 comment line and 1 code line

Code: Select all

#130607 L18L changing all 'MoManager-${ORIGLANG12' to 'MoManager-${transLANG' requested by Bert

Code: Select all

sed -i 's/MoManager-${ORIGLANG12/MoManager-${transLANG/g' /usr/sbin/momanager

.. and you have version 130607

[Bert]

Bert,

the little thing was 65 changes

If I had known that beforehand, I would have never dared to mention it

(you don't deserve that much fun )

Thank you L18L!

[Think I'll wait for your next release, as I don't know where to put the code line (sed -i...)]

[L18L]

[Think I'll wait for your next release, as I don't know where to put the code line (sed -i...)]

drag and drop to a console and press ENTER key

What else is required for next release?

[Bert]

What else is required for next release?

- basename. not PATH

- I liked the proposal by don570: some kind of warning when a .pot file from /usr/share/doc/nls will be used by Momanager. Checking the pot creation date is not so straightforward for poedit users as it is for Geany users.
I don't know if your new "up-to-date?"code (the idea by rodin.s) covers this or if/how it deals with pot files taken from /usr/share/doc/nls.

Off-topic: I saw the German floods images. Brrr.
Hope your house and area are safe!

[vicmz]

Fast and Furious Marilyn Monroe running fine here. Thank you for your hard work, L18L.

[L18L]

Poor Victor, more and more stuff for MM for dummies

Bert, we live high up in the mountains here

- I liked the proposal by don570: some kind of warning when a .pot file from /usr/share/doc/nls will be used by Momanager. Checking the pot creation date is not so straightforward for poedit users as it is for Geany users.
I don't know if your new "up-to-date?"code (the idea by rodin.s) covers this or if/how it deals with pot files taken from /usr/share/doc/nls.!

Date of mo file is compared with date of script resulting in _ or +. That's all.

Now trying to find a pot file

Code: Select all

 ls /usr/share/doc/nls/*/*.pot

41 pot files !

1 example: peasyscan.po
"POT-Creation-Date: 2013-02-26 19:09+0800\n"
"PO-Revision-Date: 2013-02-26 19:59+0100\n"

I will delete the pot file and its directory and there is no problem anymore

Code: Select all

rm -r /usr/share/doc/nls/peasyscan

Storing pot files is from pre_MM-ages
Invented by shinobar IIRC.
But now only necessary if momanager cannot produce an actual pot file. The only known case is alsaconf.....

The same is valid for po files:

Code: Select all

# ls /usr/share/doc/nls/*/*.po
/usr/share/doc/nls/get_libreoffice/de.po  /usr/share/doc/nls/obconf/de.po
/usr/share/doc/nls/grub4dosconfig/de.po
#

oops again
get_libreoffice/ deleted
obconf is binary
grub4dosconfig/ deleted

Thank you, langpack_de is going to become a bit less bloated.

- basename. not PATH

All right. I was also having some trouble to find a script.....

[Bert]

Thank you for your hard work, L18L.

+1

Poor Victor, more and more stuff for MM for dummies

Yeah, but cover ready for printing press:

[L18L]

[L18L]

New:
Scripts displayed as base name → path
→ is configurable

Making find of any Script in drop down lists easy now




edit
momanager-20130609.pet deleted
please use recent pet at http://www.murga-linux.com/puppy/viewto ... &start=137

[Bert]

A mi gusto!

Nice to see the left column full of smilies...

This improvement is even better than I had imagined. Really very nice!

The only place where it gets a bit more difficult is with the many "func_" entries (Pburn, Pmusic)



But the ease of the rest of the sorting more than makes up for this.

Thank You!

[L18L]

New:
Sort of Binary executables same as Scripts
Highlight search term in search result

2 more configuration variables,
SHOW_SEARCH_RESULT and
HIGH_BG which is a background colour.

Code: Select all

### edit between = and #   
showINTRO=no               # anything other than yes will skip the intro   
transLANG=de               # de_DE or de
myEMAIL=fido@localhost     # used when create a mo file
ISIN=☺                                         #       1 printable character to indivate mo file newer than script: ☺ or _
NOTIN=↻                                       # other 1 printable character to indicate mo file older than script: ↻ or X
SEPARATOR=⇔                               # or → or :                different from ISIN and NOTIN
SHOW_SEARCH_RESULT=1       # =0 in Xdialog without highlight or =1 highlighted in defaulthtmlviewer 
HIGH_BG='lightyellow'      # background colour for search term in search result
                           #         or choose colour with Gcolor2 (Menu > Graphics)
HIGH_BG='rgb(255,255,204)' # background colour for search term in search result

Have fun

edit

No wait some moments:

I am going to make it easier, without html using builtin --colour of grep

[L18L]

... I am going to make it easier, without html using builtin --colour of grep

Proudly presenting FFMM 130610

Binary executables in same sort order like Scripts
Search result highlighted in console
Search configurable context lines and geometry of result

Fun



edit
momanager-20130610.pet deleted
please use recent pet at http://www.murga-linux.com/puppy/viewto ... &start=137

[Bert]

Let me be the first one to admit I'm not clever enough for this L18L guy

He proudly presents FFMM 130610:

Binary executables in same sort order like Scripts
Search result highlighted in console
Search configurable context lines and geometry of result

The first two I understand, but I cannot digest the third one without a (polite) burb
If I'm allowed some humour, I think his coding voodoo is now also infecting his human-readable-output

I've been staring at this screenshot, wondering how it was done:

,
because here it looks like this, also in the latest FFMM:



Apologies if I missed the obvious.

Preferences-questions:



"ISIN" would be understandable if named "ISUP2D8"?
(same for "NOTIN": NOTUP2D8"?)

SEPARATOR: Will it change from '<=>' to '->' at some point and why? And how to interpret 'different from ISIN and NOTIN' ?

Written with the greatest respect L18L !
And again, thanks for your work!

[L18L]

Search configurable context lines and geometry of result

The first two I understand, but I cannot digest the third one without a (polite) burb
If I'm allowed some humour, I think his coding voodoo is now also infecting his human-readable-output

Search: the "new" way to find anything inside mo files
configurable context lines: number of lines before found search term and number of lines before found search term
configurable geometry of result: geometry of a rectanlgle is WiDTH and HEIGHT

I've been staring at this screenshot, wondering how it was done

,
because here it looks like this, also in the latest FFMM:



Apologies if I missed the obvious.

I am not sure if I understand your question.
It was done using with mtPaint-snapshot. I do not see any relevant difference in the two images.

Preferences-questions:



"ISIN" would be understandable if named "ISUP2D8"?
(same for "NOTIN": NOTUP2D8"?)

But a smiley and the symbol for refresh are understandable?
I could change the configuration file saying something like
If you do not understand anything then do not touch.

SEPARATOR: Will it change from '<=>' to '->' at some point and why? And how to interpret 'different from ISIN and NOTIN' ?

SEPARATOR is one character and separates "base name" from "path/base name".
Change it for example to ☺ (which is NOT different from ISIN) and momanager could not work as before.

Thinking about next version now
which will have no choices of changing SEPARATOR ISIN and NOTIN

Answered with the greatest respect!
And again, thanks for your feed back

[L18L]

simplified configuration now, thanks Bert
have fun


edit
momanager-20130611.pet deleted
please use recent pet at http://www.murga-linux.com/puppy/viewto ... &start=137