(old)Puppy Linux Discussion Forum

Posted: **Mon 09 Nov 2015, 10:06**

technosaurus wrote:Leave me a link to your current work and I will try to keep it compatible or send a patch. I am going to be replacing some puppy terminology with appropriate standards from standards.freedesktop.org.

Purpose of my work is:
let translator use our translation tool momanager to translate jwm_create_menu.
They will see and translate just .po files as usual.
gettext tools msginit msgmerge and msguniq are used.
Translation file jwm had to be renamed to jwm_menu_create (or anything other than jwm).
Only translated items are to be stored in these translation files (the gettext way

).

Biggest change is use of variable _M_n
e.g. _M_6 instead of jwm_GraphicGraphics
Hope you can live with this; or with _M_jwm_GraphicGraphics
as _M_ is needed to identify this translation METHOD at the moment in momanager (3 methods ATM):

Code: Select all

 # METHOD
 # note, gettext method does NOT need explicit 'gettext', see ex: /etc/grub.d/20_ppc_terminfo
 # thus grep gettext is not useful
 case ${SCRIPT##*.} in
  md) METHOD='mdview' ;;
   *) [ "`grep -m 1 '${_M_'   $SCRIPT`" ] && METHOD='t12s' || METHOD='gettext' ;;
 esac

I'll post a link here if/when it is all tested and working (new version of momanager).

Note @all,
technosaurus' translation method is older than momanager.

EDIT
t12s method is in momanager but has never been really tested bacause no one seems to use it.

Posted: **Mon 09 Nov 2015, 16:31**

You do not need to give manually numbers for the _M_ variables. It is done automatically.

Tested. It works. Just use ${_M_:-English message}

Posted: **Wed 30 Dec 2015, 10:46**

technosaurus wrote:Leave me a link to your current work and I will try to keep it compatible or send a patch. I am going to be replacing some puppy terminology with appropriate standards from standards.freedesktop.org.

Latest momanager can use one and the same TEXTDOMAIN for
gettext, our t12s and mdview files now.

Thus a .md help file would be nice.

... and a Happy New Year

Posted: **Fri 01 Jan 2016, 21:39**

I don't think we'll need to generate translations specifically for jwm if we simply add the appropriate translations to /usr/share/desktop-directories/*.directory ... Translations (same format as .desktop files)are currently missing from woof-ce, but this way other menu systems can benefit.

(old)Puppy Linux Discussion Forum

jwm_tools-0.9 (was jwm_menu_create)

technosaurus' translation method in momanager

jwm_tools-0.9

Re: back to work on jwm tools