On Thu, May 21, 2015 at 01:22:44AM +0200, Martin Quinson wrote: > Hello guys, > > after almost 2 years, I just released a new version of po4a. That > version does not come with a huge load of changes (I just integrated > some of the available patches on the Debian bug tracker), but that's > still a very good news: I managed to get into the situation where I > can upload versions of that software again! I think that more releases > will flow in now that my setup is fixed. > > That being said, I don't expect much free time to hack on po4a so I'll > mainly do the basic maintainance. That's already much more than what I > did in the recent years (my last upstream release was almost 10 years > ago!) > > Feel free to write patches, and I'll integrate them ;) > > Bye, Mt. Very good news. I was afraid it was a dead project and almost ready to take over and fork it. We (KiCad development team) are rely on asciidoc+po4a for handling the i18n of the documentation. Asciidoc is (IMHO) the best light markup format but it lacks (for now) internal handling of i18n strings. Thanks to po4a that makes it possible.

I know a joke about UDP, but you might not get it.

On Thu, May 21, 2015 at 09:32:13AM +0200, Martin Quinson wrote: > Thanks for your support. > > There is definitely no need to fork the project: our resources are > already scarce, and a fork would not help us. I'm ok with migrating > the project to another host if that's what you need to participate, > but your energy is welcome within the project, no need to fork ;) I would LOVE to see it into a git(hub? bucket? or the like) hosting service.

> There is still a bunch of low hanging fruits in the debian and alioth > bug trackers that I plan to fix, but any help (and patches) for the > other bugs is really warmly welcome. I would like to contribute in the translation of po4a doc in italian and for bug report/test with asciidoc.

> One of my dreams would be to port po4a to perl6 to enjoy the new way > of writing parsers. But it won't happen anytime soon, I fear. Support for Perl5 will last for many years so there is no need to hurry...

Also, I have a request, addressed to anyone willing to provide patches (Marco?): that would be the ability to show anywhere in the UI the current column number while editing, as in a lot of text editors and in Lokalize. That _really_ helps, e.g. when translating messages output of shell scripts whose lines shouldn't wrap. Unfortunately I never wrote a single line of perl, so I can't do that myself.