Hi all
L18L had an course with me regarding gettext. I have avoided this as much as possible, but he (I assume that it's a he) pushed it the all way through, so I simply couldn't step off..... The result is seen in pClock which uses gettext for NLS - thanks to L18L.

Now that I know how it works you might find it reasonable that I convert my tiny apps to gettext to give our translators a better working environment. I have spend the last day thinking about this, and come to a conclusion. The work is just bigger than I find inspiration to offer. Puppy is mainly a fun-project for me, and I want it to stay that way..... I already spend some hours maintaining codelines, and I don't find bugfixing to be funny only.

But that doesn't mean I don't want gettext.

If someone out there wants to help out converting apps to use gettext (like L18L did for pClock), that is no problem to fix. The only thing we need to keep track of is that you work on the latest code. And it is no problem for me if you spend some time on the work. I don't work on all apps at the same time anyway. Let's just agree what app I should stay away from.

Today I released Pmusic 2.6.4. This is a bugfix release, and I plan the next to be 2.7.0 which includes new stuff - This will take much time, and if someone wants to work on NLS, now it's a perfect time.

Most of the others apps are smaller (except Pburn), so these is probably less time consuming to work with.

I would like to try something simple like pProcess first. Maybe even some automatic script based on sed can do it: to take some lines from translation file and put them into main script with addition of necessary gettext syntax...

I would like to try something simple like pProcess first. Maybe even some automatic script based on sed can do it: to take some lines from translation file and put them into main script with addition of necessary gettext syntax...

Hi rodin.s
I have a script that you made for Pmusic 2.6.3, I was able to create a .pot file. Do I need an updated version of your script for new versions of Pmusic?

Sorry for the off-topic (well, not so off-topic): I need someone who is able to teach me some gettext basics. The information I find on the Internet assumes I have console and compiling skills (not something I can learn in the short term). If anyone is willing to, just PM me. (I know, there is MoManager, but I haven't seen any puplets with MoManager yet, and not all software is internationalized to use this method)_________________Puppy Linux en español

I know, there is MoManager, but I haven't seen any puplets with MoManager yet, and not all software is internationalized to use this method

I don't know what you mean by the second half of the sentence.

All puppies built from Woof since late February 2012 have MoManager and the support inftrastructure.
That includes Wary, Racy (me), Slacko (01micko). There are various Debian and Ubuntu builds, including a Upup made by pemasu from a recent Woof. Also there is a Mageia puplet created by scsijon. Probably some others too that I can't recall right now.

Oh yes, the ARM-board puppies are built from latest Woof.

Looking ahead, all puppies will have it.

There are some "legacy" puppies that don't, however, in theory MoManager could be backported.

The special case of forks of Woof, such as FatDog64, MoManager could also be ported to that. But, that would be up to the FatDog developers. It would be a very good thing for them to do, as then all of the langpacks would work on their puplet, and we have a growing collection._________________http://barryk.org/news/

With MoManager, you should not require "console" or "compiling" skills. It is a GUI, and the console utilities are executed automatically. MoManager will even create a langpack PET for you automatically._________________http://barryk.org/news/

Thank you guys. Regarding puplets I've received requests for compatibility with puplets that were built before MoManager was implemented, especially Lucid and Saluki, that was the reason of my request. I do use MoManager actively and release at least one update per month, many users are glad that you created it, BarryK. OK, after this I can focus entirely on the official langpack_es. The langpack_es official page explains which Puppy versions are compatible but doesn't include any puplets, so I'll add those you mentioned. Thank you again.

I will be posting a new version of puppy backup
(the improved version of pmirror). It will
have a yaf-splash window to show activity.
It should be released in couple of days so I can
test it thoroughly.

I have added gettext to pProcess. It's MoManager compatible. File pprocess.mo will be created in MoManager after translation. I had to do some workaround sins MoManager supports only one script for one mo-file and pprocess has tree scripts with gettext. Main script is pprocess so I have added lines from two others into main script.
Maybe now I want to try pBurn as something more complex.

What I don't like is the comments at the end to sync with *.pot. I see this as a temporarily solution until MoManager supports multiple scripts for one *.mo file. For pProcess, the comments are few.... for pMusic it will be 'endless'. The worst is not extra codelines, but the fact that I have to update these comments as the app evolves. The arguments for gettext fails with this solution. We could instead use your pMusic-gettext script....

I assume that MoManager will be improved, and we continue the way towards gettext.....

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