mavrothal 07a44aa52f Initial commit from Nov 11, 2013, woof2 fossil repo %!s(int64=11) %!d(string=hai) anos
..
README.txt 07a44aa52f Initial commit from Nov 11, 2013, woof2 fossil repo %!s(int64=11) %!d(string=hai) anos
ROX-Filer.pot 07a44aa52f Initial commit from Nov 11, 2013, woof2 fossil repo %!s(int64=11) %!d(string=hai) anos

README.txt

ROX-Filer source package does not have .pot file!

However, it does have lots of .po files, ex de.po.

However, Puppy Forum member LaRioja has done some work on de.po, improved it:
http://www.murga-linux.com/puppy/viewtopic.php?t=76281

However, i need a .pot file, to put here:
/usr/share/doc/nls/ROX-Filer/ROX-Filer.pot

...MoManager will find this and a translator can then create a .po hence .mo file.

I found some info how to convert po to pot:
http://www.commandlinefu.com/commands/view/10042/empty-a-gettext-po-file-or-po2pot

This line does it (plus a bit of editing by me):

# msgfilter --keep-header -i ROX-Filer.po -o ROX-Filer.pot awk -e '{}'

Extract from the User Manual is below. It states that src/messages.pot exists in source,
but it doesn't.
The gist of the docs is that a .mo file has to be in a special location, for example:
/usr/local/apps/ROX-Filer/Messages/de/LC_MESSAGES/ROX-Filer.mo

The docs also state that /usr/local/apps/ROX-Filer/Options.xml has to be edited:

"so that your language is listed, restart the filer and select it from the Options box
(see the section)"

Barry Kauler
March 7, 2012

INSTRUCTIONS FROM ROX-FILER USER MANUAL
---------------------------------------











ROX-Filer is able to translate many of its messages,
provided suitable translation files are provided:


Open the Options box from the menu,
Select a language from the list,
Click on OK and restart the filer
for the new setting to take full effect.










Go into the src/po directory and create
the file src/messages.pot:


$ cd ROX-Filer/src/po
$ ./update-po



Copy the file into the src/po
directory as <name>.po. Eg, if your
language is referred to as `ml' (`my language'):

$ cp ../messages.pot ml.po


Load the copy into a text editor.

Fill in the translations, which are all blank to start with.


Run the make-mo script to create the
binary file which ROX-Filer can use.
You will need the GNU gettext package for this.


$ cd ROX-Filer/src/po
$ ./make-mo ml
Created file ../../Messages/ml.gmo OK


Edit ROX-Filer/Options.xml so that
your language is listed, restart the filer and select it from the Options box
(see the section).


Submit the .po file to the ROX
patch tracker so that we can include it in future releases of the filer.











Go into the directory containing the .po
files and run the update-po script.
This checks the source code for new and changed strings and updates all
the translation files.


$ cd ROX-Filer/src/po
$ ./update-po


Edit the file by hand as before, filling in the new blanks
and updating out-of-date translations.
Look out for fuzzy entries where
update-po has made a guess; check it's correct and
remove the fuzzy line.


Run make-mo as before.

Submit the updated file to us.



See the gettext info page for more instructions on creating
a translation.





ROX-FILER SCRIPTS
-----------------

The script src/po/make-mo:

#!/bin/sh

if [ "$#" != 1 ]; then
cat << HERE
Usage: 'make-mo '
Eg: 'make-mo fr' to compile the French translation, fr.po, ready for use.
HERE
exit 1
fi

OUT_DIR=../../Messages
LOCALE_DIR="$OUT_DIR/$1/LC_MESSAGES"
OUT="$LOCALE_DIR/ROX-Filer.mo"
mkdir -p "$LOCALE_DIR"

# This code converts to UTF-8 format. Needed by Gtk+-2.0 at
# least, and may help with other versions.
charset=`grep "charset=" $1.po | head -1 | sed 's/^.*charset=\(.*\)\\\n.*/\1/'`
echo Using charset \'$charset\'
iconv -f $charset -t utf-8 $1.po | \
sed 's/; charset=\(.*\)\\n"/; charset=utf-8\\n"/' | \
msgfmt --statistics - -o $OUT && echo Created file $OUT OK