Off-topic half way, but I just had to get it out of my Brain.
In search of a better cross-format conversion, I followed Oliver Taylors advice about Prince, to generate my PDF files, and after investing a couple of hours, this proved to be rewarding.
I made a command in a similar way as Oliver did, and made a custom CSS, which in this case suits the needs for a Client Manual.
Currently, I keep the Source File in XHTML format. (One large file, not like in DocBook ).
My problem is, that apart from the prince-bookmark-level property I also need to structure the content using ID anchors for the Targets and then keep a TOC, that would then dynamically update as per command, much like the one, that is available in AMAYA.
And second to this, I'd like to keep the source file either in Textile or Markdown format and then convert to XHTML and PDF.
I use Bret Teerpsa's HTML Index Bundle in the meanwhile, for what I need.
I believe for some reason, that a command that dynamically updates a TOC, if present, would be of much sense, to be available in the markdown, textile and HTML Bundles by default.
Out of Interest, I'd like to know Allan's opinion about this for version 2, and if so, any other advice, suggestions about maintaining Documentation files in a separate Project in General.
regards, marios
Just to sum this up, why I prefer Textile over markdown , is only because Textile supports attributes like classes, which I need on those documentation files.
So I can convert a Textile document to XHTML with the built in Textile command. But not the other way around.
If I use markdown, I can convert both ways, from what we've got now.
regards, marios
On 20/09/2007, at 22:09, marios wrote:
Just to sum this up, why I prefer Textile over markdown , is only because Textile supports attributes like classes, which I need on those documentation files.
I think Maruku adds classes to Markdown: http://maruku.rubyforge.org/
I have yet to look into it myself (I’d also like the occasional class for my markup).
On 20/09/2007, at 19:26, marios wrote:
[...] I believe for some reason, that a command that dynamically updates a TOC, if present, would be of much sense, to be available in the markdown, textile and HTML Bundles by default.
Out of Interest, I'd like to know Allan's opinion about this for version 2, and if so, any other advice, suggestions about maintaining Documentation files in a separate Project in General.
I think a TOC should not be updated, it should be generated.
One option I think is nice is http://projects.serenity.de/textmate/markdown2book/ (since I use something similar for the TextMate manual :) )
I’d like for the bundle to have a “New Book…” command though, to easily get the user started on a new documentation project (rather than have him create the required folder + initial chapter).
Allan Odgaard wrote:
On 20/09/2007, at 19:26, marios wrote:
[...] I believe for some reason, that a command that dynamically updates a TOC, if present, would be of much sense, to be available in the markdown, textile and HTML Bundles by default.
Out of Interest, I'd like to know Allan's opinion about this for version 2, and if so, any other advice, suggestions about maintaining Documentation files in a separate Project in General.
I think a TOC should not be updated, it should be generated.
One option I think is nice is http://projects.serenity.de/textmate/markdown2book/ (since I use something similar for the TextMate manual :) )
I’d like for the bundle to have a “New Book…” command though, to easily get the user started on a new documentation project (rather than have him create the required folder + initial chapter).
I'd love to use this. Unfortunately a successful pdf conversion will fail, in that all the external links being used internally in the Index will break.
That's why I'd rather prefer to keep everything in one single large file, since internal links is the only thing that the PDF document can handle in this case.
Amaya also seems to have a make book command. Haven't tried it out yet.
regards, marios
-
Allan Odgaard -
marios