Remove_builtin: buttons translation + Xdialog.mo... [SOLVED]

For efforts in internationalising Puppy and solving problems in this area
Post Reply
Message
Author
User avatar
Bert
Posts: 1103
Joined: Fri 30 Jun 2006, 20:09

#16 Post by Bert »

Hi L18L,

I read your comment on Barry's blog:
While talking about momanager...
... we have found out that Xdialog uses Xdialog.mo in /usr/local/share/locale
I would like to add that this is not the case on my box. I had xdialog.mo in /usr/share/locale/nl/LC_MESSAGES only and Xdialog ran translated.

Only after that did I add the .mo to /usr/local/share/locale...

I just checked, by removing the .mo from /usr/local/etc and xdialog is still running translated.

I think rodin.s gave the second location only for Slacko.

Hope this is useful :wink:
[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: Xdialog

#17 Post by L18L »

L18L wrote:...Thus there is something to play with for me the next days.....
Game over :lol:

Xdialog had found its Xdialog.mo in default location before.
Recent Xdialogs must have been compiled without --prefix=/usr
thus it searches its Xdialog.mo in /usr/local/share/locale/

Having the same file in that 2 different locations is on the safe side.
Also sufficient is to have just a symlink in /usr/local/share/locale/....
Not really a hack... :wink:

Create it in command line for nl:
ln -s /usr/share/locale/nl/LC_MESSAGES/Xdialog.mo /usr/share/doc/langpack-template/usr/local/share/locale/nl/LC_MESSAGES/Xdialog.mo

The other issue was edit Xdialog.po in momanager

Find in /usr/sbin/momanager line which contains

Code: Select all

    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: Select all

    #LANG=${ORIGLANG} rxvt -e intltool-update --dist --gettext-package=${ATEXTDOMAIN} --output-file=${ATEXTDOMAIN}.po ${ATEXTDOMAIN}1
and append the following line:

Code: Select all

    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.


I do not want to make another momanager because I am hoping that all these changes will find their way into woof soon.
http://bkhome.org/blog2/?viewDetailed=00260

Bert,
please change the title to indicate that Xdialog is concerned.

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

#18 Post by L18L »

Bert wrote:Hi L18L,

I read your comment on Barry's blog:
While talking about momanager...
... we have found out that Xdialog uses Xdialog.mo in /usr/local/share/locale
I would like to add that this is not the case on my box. I had xdialog.mo in /usr/share/locale/nl/LC_MESSAGES only and Xdialog ran translated.

Only after that did I add the .mo to /usr/local/share/locale...

I just checked, by removing the .mo from /usr/local/etc and xdialog is still running translated.

I think rodin.s gave the second location only for Slacko.

Hope this is useful :wink:
Sorry I did not see this post before.

Yes, it is good to know that Barry has the correctly compiled Xdialog.
...and the symlink is the solution with the lowest memory usage.

All your posts are useful., thank you. 8)

Post Reply