From: Mariano Kamp <mariano.kamp@...>
Date: 2006-10-04T01:07:11+09:00
Subject: Re: rdoc -> pdf

Hi Gregory,

On Sep 28, 2006, at 10:15 PM, Gregory Brown wrote:

> I reformatted your post a tiny bit, to make it eaier to respond to...
> hope you don't mind...
>
Nope, not at all ;-)

> On 9/28/06, Mariano Kamp <mariano.kamp@acm.org> wrote:
>> Hi,
>>
>>    I found the below quoted message when searching for a pdf output
>> formatter for rdoc.
>
>
>> On 12/15/05, Austin Ziegler <halosta...@gmail.com> wrote:
>>
>>  > The Pickaxe2 has a PDF version available for purchase from the
>>  > Pragmatic Bookshelf. On the other hand, if someone wants to make a
>>  > RDoc formatter using PDF::Writer, I'll try to provide what  
>> assistance
>>  > I can.
>>
>> Ugh. This sounds like something that may need to go into Ruport.  I
>> hate when that happens!
>>
>> Would people be interesting in being able to use rdoc formatting to
>> generate PDFs using Ruby Reports?  If so... i'll put it on the  
>> dogpile
>> of features to be added this winter when I'm working full time on
>> Ruport for a couple weeks.
>
> Wow, this is an old message!  We've completely rewritten Ruport  
> since then. :)
>
>>    Any idea if there has been progress made?
>
> We didn't get a roaring response of Yes!
Well, I would like to have the docs available as pdf for offline use  
and because I never really quite got the hang of searching the html  
docs efficiently.

> [..]
> However, what we can offer is support for anyone interested in doing
> this.  I've used htmldoc to convert html to pdf, and it'd be cool if
> we can get something more robust into Ruport.
But rdoc already provides simple markup as a basis, doesn't it? Using  
html would mean to reverse engineer the semantics from a format that  
is already rendered for presentation, wouldn't it?

> It might be better to attack it from the HTML to PDF direction rather
> than the rdoc to PDF direction, since it would be more general.  (Then
> one could use textile,markdown,rdoc, whatever, convert to html and
> ruport could then render to PDF)
Not quite sure that I get that. Where exactly comes textile or  
markdown into the picture here?

> If anyone wants to take the initiative on something like that, go
> ahead and catch up with us on the Ruport mailing
> list(http://lists.stonecode.org/listinfo.cgi/ruport-stonecode.org) or
> in #ruport on Freenode.  All of our developers are currently tied
> down, but we can take the time to help get the information out there
> that would be needed for folks who wanted to build something like
> this.
I think I expected this to be something like a new output format for  
rdoc, like xml etc. is today. Your thinking goes along the lines to  
build something that works outside of rdoc in ruport, or am I missing  
the point here?

Cheers,
Mariano