On Sun, 18 Jun 2006, Michelle Konzack wrote:

Hello *,

my girlfriend and me have translated my whole Workstation into de, fr,
tr, ar and fa but it was a nightmare, because 'gettext' was not able to
find the $[gt.XXX] strings...

Since I have to translate several Desktops (around 60) I want to know,
whether someone has written a tool which find the $[gt.XXX] strings and
create the "fvwm.pot" file

OK, I have done it allready with a BASH script, but it is tooooooo slow
and the functions are limited...

Only my Workstation has already 280 Strings... (my Develstation
is a nightmare, even if I have allready all i18n.)

if someone is interested in my BSH-Script please let me know.
(I have currently no possibility for uploads.

Short desription:

1)  Message strings must be

       $[gt.Some text to translate]

   (see desription 'man fvwm2' => LocalePath)

2)  Output is always "fvwm.pot" in the director where it was started
   (overrides previously versions)

3)  To read ONE file use

       tdgettext-fvwm -r -i <file>

4)  To read all files in the current directory

       tdgettext-fvwm -r -i '*'

5)  Now rename it from "fvwm.pot" to "fvwm.po" and translate it

6)  With the command tdgettext-fvwm -c' it will compile it to "fvwm.mo"

7)  Copy the file to $HOME/locale/CC/LC_MESSAGES/fvwm.mo where CC is
   the country code of your translated fvwm.po

8)  Put in your ~/.fvwm/config following line:

           LocalePath $HOME/locale/:+

9)  Restart and enjoy an internationalized and localized fvwm DeskTop.

Note 1: I like to see some people which test this script, because
       I want to improve it, but first it must work perfectly.

Note 2: Currently I am rereading the WHOLE bunch of Fvwm manpages
       since I have forgotten many options (and some are added
       since 2.4) and the manpages are better then the newspapers...

       Hey, I have found many spelling errors. Where can I report them?


You may report errors in the manpage to the fvwm-workers list. The preferred method is that you send in a patch against the cvs version where you fix the errors. Also note that many manpage errors have been fixed in cvs since 2.5.16 was released, so I recommend you to get the cvs version (or a recent snapshot) of the manpage instead of the 2.5.16 version to avoid double work in finding and fixing the errors.

/Viktor

Reply via email to