On Fri, 24 Jun 2016 11:36:46 +0200 Martin Quinson wrote: > Hello, Hello Martin, thanks for your prompt reply. > > 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. OK, I assume the same holds for the other upstream authors of po4a (or do you just speak for yourself?). > > As a result, I think that you should develop this module yourself. I can try, with some help from you and the other po4a upstream developers. > I > understand that Perl will make your brain burn as a Ruby programmer, My brain is probably already burnt, due to overexposure to Fortran, but I digress... ;-) The fact is that I haven't programmed in Perl for about 14 years and my Perl knowledge was just a smattering anyway, so bear with me! > 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. Your guidance will be much appreciated, thanks a lot! > > Check the doc on writing a new module, here: > man Locale::Po4a::TransTractor I will study this soon, thanks for pointing it out. In the meanwhile, I have to study the Ruby document format description in more detail. > > 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. OK, I am replying to both the bug address and the po4a-devel mailing list. Please keep me in Cc, when replying (as I am not subscribed to the mailing list or to the bug). Thanks. Bye. -- 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

On Mon, 5 Sep 2016 15:00:11 +0200 Martin Quinson wrote: > Hello Francesco, Hello Martin, thank you so much for writing me! Your message is really appreciated, as I was just going to send an update today (an astonishing coincidence!). > > did you manage to do any progress on this front? It was an interesting ride in the last two months, and the time devoted to the development of the po4a module was not so abundant... But, nonetheless, I've just come up with the attached version of the Rd module. The tar archive includes the module implementation and a little document to test it (the tests/ directory also contains the various output files and two scripts). > Is there anything I could do to help? Yes, there is. Could you please * 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 and tell me how the module could be improved? Thanks for your time and helpfulness! Bye. 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

On Tue, 6 Sep 2016 02:40:49 +0200 Martin Quinson wrote:

> A first point would be to convert your tests to a proper test of our > infrastructure, somewhere under t/ Once you have some automated tests, > I will happily integrate your work in the main archive. This is where I need your help most: could you please do the conversion yourself? I am convinced that this would be the best option, since I have zero familiarity with the test infrastructure used in po4a and I am afraid I would mess everything up... :-p

> > Then, the next step will be to test your work against the existing > Ruby documentation, and fix it until it works properly. I'll try and find a little more time and test Rd.pm against some existing Ruby documentation.

> 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.

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.

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.

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.

Control: tags -1 + patch On Mon, 27 Mar 2017 09:15:38 +0200 Martin Quinson wrote: > On Sun, Mar 26, 2017 at 04:03:47PM +0200, Martin Quinson wrote: > > Hello, Hi! > > > > 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. Good, I am glad to read this. > > > > 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. I am attaching a full patch, with the new module, the new tests, everything with respect to po4a version 0.51. I hope this satisfies your expectations, since I have devoted a quantity of spare time to it and it was not easy to find such time... > > > > Sorry for the latency, I'll try to be more responsive in the future. > > > > In addition, you'll need the attached patch to integrate your module > to po4a and play with the test directory. It assumes that your Rd.pm > file is renamed as lib/Locale/Po4a/RubyDoc.pm (as it should). These modifications are included in the patch I am sending right now. Further actions yet to be performed: * the new module should probably be added to t/01-classes.t (could you please do it for me?) * three new copyright lines should be added to debian/copyright (please remember to do so; please note that my patch is released under the terms of the GNU GPL v2 or later, just like most of po4a) Copyright (c) 2016-2017 by Francesco Poli <invernomuto(a)paranoici.org&gt; Copyright (c) 2004 by MoonWolf <moonwolf(a)moonwolf.com&gt; Copyright (c) 2011-2012 by Youhei SASAKI <uwabami(a)gfd-dennou.org&gt; * my patch is to be applied to the official version of po4a (only you po4a developers can do that, so please accept it) * a new version of po4a will have to be uploaded to Debian unstable (please do so, when possible) > > Thanks for your time and patience, You're welcome. Looking forward to seeing this new module accepted in po4a. Bye! -- 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

On Tue, 11 Apr 2017 18:16:21 +0200 Martin Quinson wrote: > Of course I did not change the debian/changelog yet. Nor the debian/copyright file, obviously. But please remember to do so, when you upload the new version to Debian unstable...

> I did so in the git repo of the package. That way, I will not forget. Is it visible on a public repository? Where?

On Sun, 16 Apr 2017 16:03:51 +0200 Martin Quinson wrote: > > > I did so in the git repo of the package. That way, I will not forget. > > > > Is it visible on a public repository? Where? > > https://anonscm.debian.org/cgit/collab-maint/po4a.git I am probably misunderstanding something, since I cannot spot any commit done after 2017-03-28 ... And, above all, I cannot find any mention of the new Ruby Document module or its copyright notices in the debian/changelog or debian/copyright files. Could you please clarify? Thanks for your time and patience!