I also was experimenting with gettext and poedit. Locale file consists of 353 lines so it's easier to use poedit to handle it. Normal locale file is created with script gettext_script.
Some instructions how to use it are in the script:

Code:

# use 'xgettext -L shell gettext_file -o pmusic2.pot' to generate pot file
# use poedit to create and translate po file and then mo file will be created
# put pmusic2.mo to /usr/share/locale/xx/LC_MESSAGES (xx - name of your locale)
# run the script to create text translation file for pmusic with name of your locale (ex: ./gettext_file)
# you can run the script with your name as first parameter for tranlsator line. (ex: ./gettext_file rodin.s)
# and locale could be second parameter. If it is not given then it defaults to current locale (ex: ./gettext_file rodin.s ru_RU.UTF-8)
# place the file to /usr/local/pmusic/locals

I wonder if you could tell me....
What is so great about gettext? I have never used it....
I have just put all this NLS on hold until things get settled in Puppy. Now when Barry has started the work on NLS, all I see is many different standards. I hoped that Puppy should use one (or a few) to standardize the handling of language files.

From the view-point of a translater, do you find the zigbert-way hard to manage? I clearly see that I have missed the placement of the local files. I will probably move them, now when Puppy seems to be using /usr/share/locale/xx/

I simply want to learn more about the pro and cons for the different ways of doing things.

In my opinion gettext is easy to use with scripts and internationalization could be made faster. It is a great tool for my work on Russian l10n of Puppy. Poedit has features of spell-checking and translation memory. It also works good when old script is updated. Old translation is not lost but updated automatically and new untranslated lines appear at the top of the list.
In case of Pmusic I have two files: new English file and old Russian one and then I have to compare them using information about changes made. And these changes are in different parts of the file. It takes time to find them all. These files are usually opened in different tabs of geany and I have to switch between the tabs.
Gettext is a little bit slower but it's a price I'm ready to pay for comfort. I had 2100 lines in my puppy.pot file and I could manage them with poedit but I think it would be hard to do zigbert-way.

I have made Russian translation for version 2.6.3. As I understand now it should be in /usr/share/locale/ru/LC_MESSAGES. There are also two LOC2913 which is confusing.
I was also experimenting with my gettext translation method and I have made some scripts to make it easier.
Directory pmusic_translate in archive has two scripts: gettext_file and create_translation.sh. To use it you should open urxvt in this dir and run with your name as argument for translator credit:

Code:

./create_translation.sh

When you choose '1' pmusic2.pot will be created.
Then you have to use poedit and create translated file YOUR_LANG.po and YOUR_LANG.mo.
(in my case it was ru.mo and ru.po, ru.mo is created automatically by poedit).
After translation files are created choose '2' in the script and translation file for pmusic will be created and copied to proper directory to work. My one for Russian was created this way.
After making some changes in your translation with poedit you may repeat step '2'.
If translation is changed by zigbert you may add new English lines (also change or remove) to gettext_file and apply to them similar gettext format as in all lines in the script. Then you can regenerate pot file with create_translation.sh (repeat step '1'), update your po-file with new pot-file in poedit and generate new file for new pmusic (repeat step '2').

esmourguit
ahem, pMusic 3 does not anymore support the old NLS model.....
The 3 branch uses gettext for language support. I see that the old locales file is included in the pet. I kept it for transition, but now that period should be over. I will remove it.

Sorry being here maybe late since i posted about french translation (around November2012 - see main post pp.94 and following)...was awaiting a kind of pMusic-final release.
I indeed got a try making a pmusic.po using MoManager as also re-using Jean-Jacques's (as. Esmourguit - merci Jean-Jacques !) some translated strings.

Here is the ca. 80% (maybe more ) french translated tar.gz archive made from pMusic-3.0.6. : it has in it pmusic.mo and also pmusic-3.0.6.po.

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum