(old)Puppy Linux Discussion Forum

Posted: **Thu 13 Jun 2013, 12:17**

yesterday L18L wrote:will upload tomorrow

... and here it is:

New variable in configuration is WINDOW_WIDTH.
momanager starts in smallest possible width of 726 px.
You can increase it up to 1360 pixel.

Have fun

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

Posted: **Wed 19 Jun 2013, 22:20**

Hi L18L,

I just noticed this: the search result window gets stuck in the upper left corner of the screen, without a means to close it. (or move it)

Closing MoManager has no effect.
The window stays on top of everything else on the screen.
It cannot be killed, as it has no entry in the tray.

I have not yet tried to repeat this. I only used the search function maybe three times so far. This is the first time this happens.

All else is functioning beautifully!

Posted: **Thu 20 Jun 2013, 07:54**

Bert wrote:...I just noticed this: the search result window gets stuck in the upper left corner of the screen, without a means to close it. (or move it)..

Howto close any window in almost any GUI:

click the top right X

or if using jwm:

To close a window in jwm right click at top bar of the window and select (here translated to "Schließen") "close"

To move a window in jwm right click at top bar of the window and select (here translated to Bewegen) "move"

or keep ALT key pressed and move it with mouse left button pressed.

Bert wrote:It cannot be killed, as it has no entry in the tray....

To kill a window in jwm right click at top bar of the window and select (here translated to "Töten") "kill"

Bert,
I am describing this so verbously because I think this could become stuff for "Momanager for dummies"

Posted: **Thu 20 Jun 2013, 08:32**

Thanks for explaining.

However, I did know all that...

The problem is the search result window is placed so high, the window top bar is not on the screen. So moving and closing impossible.

Yours dummily,

Posted: **Thu 20 Jun 2013, 08:45**

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.

Posted: **Thu 20 Jun 2013, 09:28**

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

I will fix this soon.

Posted: **Thu 20 Jun 2013, 11:03**

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

Posted: **Thu 20 Jun 2013, 12:25**

Hosla IT rocks!

Thanks!

Posted: **Wed 26 Jun 2013, 00:18**

I have been using the forked momanager and I like it

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

Posted: **Wed 26 Jun 2013, 23:44**

I modified the recent fork of L18L

Posted: **Wed 07 Aug 2013, 16:11**

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

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

... 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....

Posted: **Thu 03 Oct 2013, 11:56**

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

Posted: **Fri 04 Oct 2013, 21:09**

Great, a momanager update after all these months!

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

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.

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

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!

Posted: **Sat 05 Oct 2013, 14:10**

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 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.

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

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....

Posted: **Sun 06 Oct 2013, 06:00**

Thank you L18L. Fast and Furious Marilyn Monroe is more and more sexy.

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.

Posted: **Sun 06 Oct 2013, 09:58**

vicmz wrote:Thank you L18L. Fast and Furious Marilyn Monroe is more and more sexy.
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.

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

Posted: **Sun 06 Oct 2013, 12:32**

L18L wrote:Sorry I cannot list these because I have deleted them.

I haven't

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

)

Posted: **Sun 06 Oct 2013, 15:45**

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 )

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

must stay because MoManager cannot create pot file for c source

in alsaconf/alsaconf.pot:

Code: Select all

#: alsaconf:54
msgid "Yes"
msgstr ""

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

Posted: **Sun 06 Oct 2013, 18:56**

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.

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!

**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/ !

Allright, never mind,

it's not that important, for FFMM actually works.

Posted: **Sun 06 Oct 2013, 19:18**

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

(old)Puppy Linux Discussion Forum

official (momanager) language packs

FFMM20130613

Search result can not be closed

Re: Search result can not be closed

urxvt

Re: urxvt

FFMM

FFMM

momanager

latest ffmm

Re: latest ffmm

pot files in devx

Re: latest ffmm

FFMM