Hello,
it took me a while, but I had a look at your code, at least. Your new
module seem very reasonnable to me, thank you.
The thing is that I don't quite understand the tests. Could you please
give your files sensible names? Have a look at how the AsciiDoc tests
are organized: they are in t/data-30. You have a bunch of source
files, one per feature set. And for each file you have a out and po
files. All of these files are listed in t/30-asciidoc.t
So you just have to "cp t/30-asciidoc.t t/31-rubydoc.t", edit
t/31-rubydoc.t to change the asciidoc tests into rubydoc ones.
if you have any issue with integrating your tests, I can certainly do
that, but I'd need you to give sensible names to the test files, please.
Sorry for the latency, I'll try to be more responsive in the future.
Bye, Mt.
On Mon, Dec 19, 2016 at 12:01:28AM +0100, Francesco Poli wrote:
On Tue, 13 Sep 2016 23:39:05 +0200 Francesco Poli wrote:
> On Tue, 13 Sep 2016 00:52:12 +0200 Martin Quinson wrote:
>
> > > Are you willing to convert my tests to a proper test integrated in po4a
> > > test infrastructure?
> > > I really hope you are, since I am not knowledgeable enough to do so by
> > > myself...
> >
> > Yes I am.
>
> That's wonderful news! Thank you so much!
>
> > But that's 10 years since the last time I added something
> > into the t/ directory, so I have to check again. Times are really
> > packed right now for me, so po4a will have to way a few days/weeks.
> [...]
>
> No need to apologize or explain personal commitments: waiting some
> days or weeks is more than acceptable! :-)
> It's just that I hadn't heard back from you and I needed confirmation
> that you were willing to work on this aspect...
>
> Thanks again for your helpfulness!
Dear Martin,
I prepared a new version of my Rd module for po4a (version 0.14),
with a new supported option to handle pure Rd documents (containing
only Ruby Document formatted text, without any "=begin" line).
The attached tar archive includes the module implementation and two
little documents to test it (the tests/ directory also contains the
various output files and two scripts).
As for the previous version, I am asking you to:
* review the code I wrote
* review the documentation I added (I haven't tried to convert it into
a man page with POD tools, so bear with me!)
* test the module with po4a
* convert my tests to a proper test integrated in po4a test
infrastructure (the t/ directory)
* include the module in the official version of po4a
* upload this new po4a version to Debian unstable
I hope all this can be done soon (before the stretch freeze, if
possible).
Many thanks for any help you may provide! :-)
BTW: it seems to me that po4a/0.48-1 has waited for some 6 months in
the git repository, without being uploaded to sid: any special
reason for that?
P.S.: Please remember to keep me in Cc, when replying (as I am not
subscribed to the mailing list or to the bug). Thanks.
--
http://www.inventati.org/frx/
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
_______________________________________________
Po4a-devel mailing list
Po4a-devel(a)lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/po4a-devel
--
Le problème, ce n'est pas l'internet. Le problème, c'est l'insécurité
désastreuse de tous ces ordinateurs reliés à l'internet. Il vaudrait
mieux réécrire Windows que TCP/IP. -- Bruce Schneier