Comment 1 Kev Jackson 2005-02-17 01:29:45 EST

Created attachment 18042 [details]
Patch to enable xml-pdf target

Comment 2 Kev Jackson 2005-02-17 01:31:25 EST

Created attachment 18043 [details]
Patch to fix a couple of problems with PDF generation of AspectJ devguide

Comment 3 Kev Jackson 2005-02-17 01:33:48 EST

Created attachment 18044 [details]
Patch to fix mater-name bug in version of dockbook that AspectJ uses

Comment 4 Kev Jackson 2005-02-17 01:34:42 EST

Created attachment 18045 [details]
Patch to fix the progguide PDF generation

Comment 5 Wes Isberg 2005-02-17 14:49:54 EST

Thanks very much for the patches.  They're hard to evaluate because there are  a
lot of whitespace and formatting changes; e.g., it appears that entire sections
of the build scripts and documentation were changed.  I suspect most are just
that, but it might take a while to verify.  (The doc build can only be validated
either by inspection of the input build changes or by inspection of the output,
the latter of which I'd like to avoid.)  Most likely rather than apply the
patches, I'll try to find and make the same changes you did.

Comment 6 Wes Isberg 2005-03-10 04:01:29 EST

I went through this and integrated some of it.  I was able to generate pdf for
all the guides, but the result was so poor as to be unusable.  In particular,
tables were not rendered (use informaltable instead) or rendered quit poorly (no
auto-layout) and much of the literal text in the dev guide overwrites itself. 
Also, we'd need to add things like page headers and footers, etc.  (Find
comments in the docs readme.)  It was hard to integrate the patch because the
xml had been formatted in addition to being updated, so it was tough to find the
changes.  For the programming guide, I happened upon a few places where the xml
structure had been changed (accidentally I think), so I did not commit the
programming guide.  As a result, the fop ant task throws a NullPointerException
on the programming guide.  (nice error handling).  More generally, it doesn't
look to me like the dream of docbook actually works for pdf right now, given the
level of tool support and the quality of the output, though if we can get a
working document, we can probably manage not to break it.  If I recall, this was
Erik's conclusion as well.  

Comment 7 Adrian Colyer 2005-08-26 11:57:31 EDT

Looks like we're not going to be able to do anything about this in the AJ 1.5.0
timeframe, marking as "LATER" for consideration in future release planning.

Comment 8 Eclipse Webmaster 2009-08-30 02:50:37 EDT

LATER/REMIND bugs are being automatically reopened as P5 because the LATER and REMIND resolutions are deprecated.