On Sat, Aug 14, 2010 at 3:26 AM, Daniel James
On 13 August 2010 23:46, Steven Watanabe
wrote: AMDG
OvermindDL1 wrote:
And in the generated PDF it put: """ [id test] [id test] ] """ too, like it did in the html, see attached...
I'd guess that the comment is prematurely terminated.
For some reason, the comment parser for document info is defined differently to the other parts of quickbook and doesn't deal with nested brackets. I'll fix that in the 1.45.
Ah, thanks, was wondering what was going on.
On Sat, Aug 14, 2010 at 3:27 AM, Daniel James
On 14 August 2010 00:07, OvermindDL1
wrote: It was not prematurely terminated, I had to comment out that one line or quickbooks would not compile, which is odd because the documentation says that line should be allowed. The id line is also in the documentation, but it is seeming like it is not supported either, but it still lets it compile...
I found out recently that some of the document info attributes are only valid for the 'library' documentation type. So I put in an error if they were used, but then I realised that it broke some of the documentation, so I changed it to a warning (this was about a month ago). I suspect that you built quickbook between those changes. If you're using a prebuilt quickbook, you should build it from a released version, since that will be better tested.
I built quickbook less then a week ago from trunk since that is what I
have available, could download a release version if necessary.
On Sat, Aug 14, 2010 at 3:27 AM, Daniel James
On Fri, Aug 13, 2010 at 4:46 PM, Steven Watanabe
wrote: Also, what is the difference between article and the other possible types, the documentation did not elaborate at all, just listed them...
Still curious.
Types other than library are docbook document types. You can read about them in the docbook documentation.
What about the 'library' type? This should all be explained in the
quickbook documentation, along with a look to the proper docbook page
for the other types perhaps?
On Sat, Aug 14, 2010 at 3:27 AM, Daniel James
Also, what about the man not building issue, and the fop issue? Why does the setup sh script try to download a non-existing fop version, and why does fop1.0 fail with what boostbook generates for it, although fop0.95 works?
I wouldn't bother with fop, it doesn't produce very good results. We've have better luck with xep, The setup script is problematic, it breaks quite frequently. I've been thinking about deleting it or cutting it down to something simpler. The instructions I linked to earlier would setup quickbook without using that script.
Heh, well fop is what quickbook recommends and uses, never heard of xep, will it pick it up if I aptitude install it?