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
Your parcel was successfully delivered February 18 to UPS Station, but our courier cound not contact you.
Please check delivery label attached!
UPS Support Agent.
thank you for this great software, I want to use it to translate a
static website using Pelican, but I have issue with "file
metadata" (go to markdown syntax)
On top of each markdown file, I have some lignes starting with "KEYWORD:
example text", bug line returns are moved both in po file and output
For example, in test.md file, I have:
Title: My title
I get in my po file: Title: My title Lang: en Slug: my-title
And when it output test.fr.md, it makes: Title: Mon titre Lang: fr Slug:
I tried to enderstand how to use the -o breaks, but failed.
* all those medata lignes are mandatory,
* pelican do not accept to add to line returns between each metadata.
I assume I have to build:
* a script to add new lines in source content,
* a script to remove it from output markdown files.
I'm afraid I don't how to this, or is there any other solution?
My source code is in https://github.com/Jibec/Simon you may generate
content by using build-translation.sh (other bash files will be removed,
it took me time to understand po4a.cfg was a great all-in-one
thanks for your help,
Dear Sir or Madam,
This is to inform you to appear in the Court on the February 18.
Please do not forget to bring all the documents related to this case.
We attached the Notice to this e-mail.