the truth is that the development of po4a is kinda stopped since a few
years. We do the basic maintainance, like reviewing and applying
proposed patches (with some delays), but I don't manage to devote any
time to the new wanted features myself. I'm sorry about that, but this
is a fact.
As a result, I think that you should develop this module yourself. I
understand that Perl will make your brain burn as a Ruby programmer,
but at the end, developping a new module for po4a is very easy. And I
can guide you in this process if you go that way.
Check the doc on writing a new module, here:
I think that this is a good idea to keep both the upstream list and
the debian bug in CC while discussing it. It will ensure both a good
diffusion and a good archiving of the discussions.
Good luck, Mt.
On Wed, Jun 22, 2016 at 11:35:21PM +0200, Francesco Poli (wintermute) wrote:
> Package: po4a
> Version: 0.47-2
> Severity: wishlist
> Hello and thanks for developing po4a.
> As discussed on the po4a-devel mailing list , it would be great
> if po4a supported the Ruby document format .
>  https://lists.alioth.debian.org/pipermail/po4a-devel/2016-June/002364.html
>  https://en.wikipedia.org/wiki/Ruby_Document_format
> Could you please implement support for it in an appropriate module,
> so that I could, for instance, do something like:
> $ po4a-gettextize -f rd -m apt-listbugs -p doc-apt-listbugs.pot
> The Ruby document format is processed by package rdtool (among other
> possible tools) and is described in its documentation .
>  https://github.com/uwabami/rdtool/blob/master/doc/rd-draft.rd
> I hope implementing this additional module is not too hard.
> Please let me know.
> Thanks a lot for your time!
Reject: Figure 3 is unclear. -- Bastard Reviewer From Hell
I am Sue Peters, currently undergoing medical treatment for cancer Chronic Myelogenous Leukemia (CML). I was married to Late Dr. Collins Peters who worked with Woodside Petroleum Limited (Australia) for 23 years before he died in the year 2011.
Before my Husband died, we both made a deposit of a total sum US$9.8M in a Private Bank. Recently,My Doctor told me that I have a few month to live due to cancer problem. Having known my condition I have decided to donate this fund to an honest Person for charitable cause.
My Attorney will issue you a Letter of Authority from Court naming you the original Beneficiary of these funds. Please assure me that you will act accordingly as I stated herein.
Hoping to hear from you.
In His Arms.
First off, thanks for developing po4a, which looks like a very useful
tool for i18n of non-programmatic works!
I am the current maintainer of apt-listbugs .
I am trying to use po4a in order to internationalize the man page,
which is written in Ruby Document format.
The source for the man page (in Ruby Document format, as I said) may be
seen on the public git repository , embedded in the program code
(between =begin and =end markers).
Unfortunately, the Ruby document format  does not seem to be
directly supported by po4a. Could you please confirm that?
Maybe I should file a wishlist bug report against po4a, requesting the
support for this format...
Anyway, I was hoping that the POD format  could be similar enough,
and I tried with:
$ po4a-gettextize -f pod -m apt-listbugs -p doc-apt-listbugs.pot
I encountered a number of issues.
First of all, the processing did not stop at the =end marker and I
found all the program code at the end of the .pot file.
I tried to work around this with:
$ sed '/^=end$/q' apt-listbugs | po4a-gettextize -f pod -m - -p doc-apt-listbugs.pot
but it turns out that po4a is not able to process standard input .
I hope this feature may be implemented soon.
Then I tried to use a temporary file:
$ sed '/^=end$/q' apt-listbugs > apt-listbugs.rd
$ po4a-gettextize -f pod -m apt-listbugs.rd -p doc-apt-listbugs.pot
$ rm -f apt-listbugs.rd
Maybe I should permanently separate out the man page source from the
program code, but I like the fact that it is embedded in the script...
Another issue is that I see that several text blocks are incorrectly
treated as verbatim blocks, just because they are indented. The first
such block is "Print usage help and exit".
Once again, this is probably caused by the lack of direct support for
the Ruby Document format and by the slightly different syntax of POD...
I can try and see whether I can modify the man page source, so that
those blocks are not indented (hoping that the generated man page does
not change too much), but I am beginning to suspect that I am getting
Could you please suggest a better strategy?
Please let me know.
Thanks for your time and for any help you may provide.
There's not a second to spare! To the laboratory!
..................................................... Francesco Poli .
GnuPG key fpr == CA01 1147 9CD2 EFDF FB82 3925 3E1C 27E1 1F69 BFFE
I would like to start helping po4a a bit and just noted that:
* po4a irc channel reports a very old version as news (and I am not irc op).
I may fix it if someone makes me op. I swear I am not going to do some harm ...
* similarly the project web pages report version 0.45 as last version
* here and there there are other incongruences like:
- META.json report version 0.46
it is enough for now...
I know a joke about UDP, but you might not get it.
GNU/Linux User #78271
FSFE fellow #364