Re: [docbook-apps] Extend supported output formats
Hi Gihan, On Thu, 22 Mar 2012 03:20:35 +0530 gihan karunarathne gckarunarat...@gmail.com wrote: [...] But I keep focus on learning XSLT and XSL with the hope of contribute to the DocBook projects. So, I followed some tutorials of vogella [1] [2]. Those are really help me to sharpen my understanding about technologies. Also I following some complete guide tutorials [3]. In case you need further information about DocBook, XSLT, and customization, may I point you to my cookbook? It is freely available as HTML: http://doccookbook.sourceforge.net/html/en/DoCookBook.html Hope you find it useful. :) -- Gruß/Regards, Thomas Schraitle - To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org
Re: [docbook-apps] Extend supported output formats
Hi Thomas : Thank you very much for your interesting about my procedure under * Android-xsl* project idea. I have a quick look on the book. It seems to be written in user friendly manner and easy to understand. I hope, it will accelerate my learning process towards the DocBook. I like to invite other contributes and GSoC students to have a look on this book. Thank you !. On Thu, Mar 22, 2012 at 1:04 PM, Thomas Schraitle tom_s...@web.de wrote: Hi Gihan, On Thu, 22 Mar 2012 03:20:35 +0530 gihan karunarathne gckarunarat...@gmail.com wrote: [...] But I keep focus on learning XSLT and XSL with the hope of contribute to the DocBook projects. So, I followed some tutorials of vogella [1] [2]. Those are really help me to sharpen my understanding about technologies. Also I following some complete guide tutorials [3]. In case you need further information about DocBook, XSLT, and customization, may I point you to my cookbook? It is freely available as HTML: http://doccookbook.sourceforge.net/html/en/DoCookBook.html Hope you find it useful. :) -- Gruß/Regards, Thomas Schraitle - To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org -- Regards Gihan Chanuka Karunarathne Department of Computer Science and Engineering University of Moratuwa Sri Lanka Twitter: https://twitter.com/#!/gihanchanuka LinkedIn: http://lk.linkedin.com/pub/gihan-karunarathne/25/ba3/993
Re: [docbook-apps] Extend supported output formats
Hi Gihan, I happy to hear that my tutorials (vogella) were helpful. Good luck with your project. Best regards, Lars 2012/3/21 gihan karunarathne gckarunarat...@gmail.com Hi David, Hi mentors : Thank you very much David again for your interesting towards this project idea and help me to get through this. Some are more worked up than others, but you're free to change based on your interests, feedback, community interest, and so on. I will track on the feedback and other helps which are really help me to get through the process. But I keep focus on learning XSLT and XSL with the hope of contribute to the DocBook projects. So, I followed some tutorials of vogella [1] [2]. Those are really help me to sharpen my understanding about technologies. Also I following some complete guide tutorials [3]. In the case of building an apk from DocBook, much of the source for the apk will be generated from DocBook at build time. I don't understand this point clearly. Can you explain it further, David? I would look around for some .apk books and see how close the html and other internal resources are to .epub. If a .apk book is very close to .epub, then it should be a pretty easy task to turn the .epub you currently get from DocBook into a .apk file. I don't know about the idea of .apk is going to implement from the scratch or in top of the DocBook. In case, it can implement like .epub built with the help of XHTML then it will be a easy task. I can build it by studying .apk from its basic [4]. Or try with some alternative method which will get the external dependencies support and get the job done. As an example, I found that AIR application for Android with the Flex SDK [5] is doing such kind of alternative. According to my understanding with my experience about Android by roughly go through this web page, they are simply creating a Android source and manifest.xml file to configure Android settings. It also ask for java class which is similar to Activity class in Android and use Android SDK to build .apk. According to my idea, we can generate those manifest.xml and other java class which help to build GUI in the Android by using XSLT transformation. Then use Android SDK to compile and build .apk by configure dependencies in Ant script. Other way, we can use from the beginning method to build .apk by using XSLT transformation. If I have misunderstanding or some wrong idea with regarding this, please correct me. Then If that's the case, you would want to find other stuff to add to the proposal so you have enough to do over the summer. I will seek for another output format during this period. We should also ask the other mentors if any are interested in this project and what their thoughts are. I'm hoping they'll chime in. Yes David. I also very appreciate if a mentor can help to me through out this project idea. We will wait until some one help us. I also think, this is a critical point with regarding where should I heading. If I tried to follow any difficult method to implement this idea, I'm wasting my time. So, any thoughts about this idea are highly valuable and appreciate for me. Thank you in Advance !. [1]. http://www.vogella.de/articles/DocBook/article.html#epub [2]. http://www.vogella.de/articles/XSLT/article.html [3]. http://www.w3.org/TR/xsl/ [4]. http://forum.sdx-developers.com/index.php?topic=3472.0 [5]. http://help.adobe.com/en_US/air/build/WS901d38e593cd1bac25d3d8c712b2d86751e-8000.html -- Regards Gihan Chanuka Karunarathne Department of Computer Science and Engineering University of Moratuwa Sri Lanka Twitter: https://twitter.com/#!/gihanchanuka LinkedIn: http://lk.linkedin.com/pub/gihan-karunarathne/25/ba3/993 -- Lars http://www.vogella.de - Eclipse, Android and Java Tutorials http://www.twitter.com/vogella - Lars on Twitter
Re: [docbook-apps] Extend supported output formats
Hi Gihan, On Thu, 22 Mar 2012 14:15:05 +0530 gihan karunarathne gckarunarat...@gmail.com wrote: Thank you very much for your interesting about my procedure under * Android-xsl* project idea. I have a quick look on the book. It seems to be written in user friendly manner and easy to understand. I hope, it will accelerate my learning process towards the DocBook. I like to invite other contributes and GSoC students to have a look on this book. Thank you. Keep in mind, the book is a draft and work in progress, but I think it contains some useful topics. :) Good luck with your project. -- Gruß/Regards, Thomas Schraitle - To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org
[docbook-apps] DocBook - PDF paths that aren't hugely expensive?
I don't mind paying for software but I can't afford the thousands that XEP costs, for exmaple. I'm really wondering what paths exist these days for turning DocBook into something that you can actually send to a book publisher (which seems to mean PDF, and that's certainly my preference, but I'm open to other options there)? I'm looking at http://www.dpawson.co.uk/docbook/tools.html#d884e128 as a starting point, and here's what I know: - dblatex is hugely brittle (trust me on this) - PassiveTeX appears to be dead - DocBook In ConTeXt was last updated in 2003, which means that even if it works it's pre-5.0 (you may notice from the ordering of this list that I like TeX's output style :) - FOP can't handle auto-width tables, which rules it out entirely for my purposes - xmlroff's compatibility page claims that it, also, doesn't do auto tables - wkhtml2pdf can't do page-number-based cross references, which means it's of no use for printed output Those are all the ones I've tried or seriously looked at. I could *really* use some pointers here. I'm feeling a bit grumpy about the whole thing because I was under the impression from the DocBook site that I could, ya know, use it to produce books. :) And so for that hasn't actually worked out very well. -Robin -- http://singinst.org/ : Our last, best hope for a fantastic future. .i ko na cpedu lo nu stidi vau loi jbopre .i danfu lu na go'i li'u .e lu go'i li'u .i ji'a go'i lu na'e go'i li'u .e lu go'i na'i li'u .e lu no'e go'i li'u .e lu to'e go'i li'u .e lu lo mamta be do cu sofybakni li'u - To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org
Re: [docbook-apps] DocBook - PDF paths that aren't hugely expensive?
On 22.3.2012 11:11, Robin Lee Powell wrote: I don't mind paying for software but I can't afford the thousands that XEP costs, for exmaple. According to http://www.renderx.com/download/shop.html XEP costs 360 USD which is not free, but far from thousands. Antenna House is for similar price if your documents are bellow 300 pages. I'm feeling a bit grumpy about the whole thing because I was under the impression from the DocBook site that I could, ya know, use it to produce books.And so for that hasn't actually worked out very well. I know about many books which had been directly typesetted from DocBook sources (I made dozen of such books myself). Usually commercial XSL-FO rendering engine like XEP or AntennaHouse was used. (FOP is almost there, but not quite yet, it certainly improved in past years.) If you have strong XSLT and TeX skills you can build on top of dblatex or db2latex, or even write your own transformation to TeX covering just DocBook subset used. Jirka -- -- Jirka Kosek e-mail: ji...@kosek.cz http://xmlguru.cz -- Professional XML consulting and training services DocBook customization, custom XSLT/XSL-FO document processing -- OASIS DocBook TC member, W3C Invited Expert, ISO JTC1/SC34 member -- signature.asc Description: OpenPGP digital signature
Re: [docbook-apps] DocBook - PDF paths that aren't hugely expensive?
I'm not trying to convince you that DocBook Friends are perfect, but really, you are able to prepare books with it! I'm personally quite happy with fop xsltproc. It requires some knowledge, but works pretty well. -- Regards / Pozdrawiam Tomek Kaczanowski http://practicalunittesting.com 2012/3/22 Robin Lee Powell rlpow...@digitalkingdom.org: I don't mind paying for software but I can't afford the thousands that XEP costs, for exmaple. I'm really wondering what paths exist these days for turning DocBook into something that you can actually send to a book publisher (which seems to mean PDF, and that's certainly my preference, but I'm open to other options there)? I'm looking at http://www.dpawson.co.uk/docbook/tools.html#d884e128 as a starting point, and here's what I know: - dblatex is hugely brittle (trust me on this) - PassiveTeX appears to be dead - DocBook In ConTeXt was last updated in 2003, which means that even if it works it's pre-5.0 (you may notice from the ordering of this list that I like TeX's output style :) - FOP can't handle auto-width tables, which rules it out entirely for my purposes - xmlroff's compatibility page claims that it, also, doesn't do auto tables - wkhtml2pdf can't do page-number-based cross references, which means it's of no use for printed output Those are all the ones I've tried or seriously looked at. I could *really* use some pointers here. I'm feeling a bit grumpy about the whole thing because I was under the impression from the DocBook site that I could, ya know, use it to produce books. :) And so for that hasn't actually worked out very well. -Robin -- http://singinst.org/ : Our last, best hope for a fantastic future. .i ko na cpedu lo nu stidi vau loi jbopre .i danfu lu na go'i li'u .e lu go'i li'u .i ji'a go'i lu na'e go'i li'u .e lu go'i na'i li'u .e lu no'e go'i li'u .e lu to'e go'i li'u .e lu lo mamta be do cu sofybakni li'u - To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org - To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org
Re: [docbook-apps] DocBook - PDF paths that aren't hugely expensive?
On Thu, 22 Mar 2012 03:11:37 -0700, Robin Lee Powell rlpow...@digitalkingdom.org wrote: - dblatex is hugely brittle (trust me on this) I guess I don't trust you on this. We've been using dblatex for several years now on book-length grammars, with excellent results for articles, reports, and books. It's true that we don't exercise all the DocBook elements (we don't use most of the computational elements, for example), but I would be surprised to find dblatex having significant problems there. Between the command-line parameters to dblatex (which can be put into a .xsl file) and LaTeX style sheets, there's not much you can't tweak. Mike Maxwell University of Maryland - To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org
Re: [docbook-apps] Extend supported output formats
Hi Lars Vogel : Thank you very much !. It's nice to meet you in DocBook. I got to know about basics of Android from a tutorial of you. Great work, keep it up !. On Thu, Mar 22, 2012 at 3:14 PM, Lars Vogel lars.vo...@googlemail.comwrote: Hi Gihan, I happy to hear that my tutorials (vogella) were helpful. Good luck with your project. Best regards, Lars 2012/3/21 gihan karunarathne gckarunarat...@gmail.com Hi David, Hi mentors : Thank you very much David again for your interesting towards this project idea and help me to get through this. Some are more worked up than others, but you're free to change based on your interests, feedback, community interest, and so on. I will track on the feedback and other helps which are really help me to get through the process. But I keep focus on learning XSLT and XSL with the hope of contribute to the DocBook projects. So, I followed some tutorials of vogella [1] [2]. Those are really help me to sharpen my understanding about technologies. Also I following some complete guide tutorials [3]. In the case of building an apk from DocBook, much of the source for the apk will be generated from DocBook at build time. I don't understand this point clearly. Can you explain it further, David? I would look around for some .apk books and see how close the html and other internal resources are to .epub. If a .apk book is very close to .epub, then it should be a pretty easy task to turn the .epub you currently get from DocBook into a .apk file. I don't know about the idea of .apk is going to implement from the scratch or in top of the DocBook. In case, it can implement like .epub built with the help of XHTML then it will be a easy task. I can build it by studying .apk from its basic [4]. Or try with some alternative method which will get the external dependencies support and get the job done. As an example, I found that AIR application for Android with the Flex SDK [5] is doing such kind of alternative. According to my understanding with my experience about Android by roughly go through this web page, they are simply creating a Android source and manifest.xml file to configure Android settings. It also ask for java class which is similar to Activity class in Android and use Android SDK to build .apk. According to my idea, we can generate those manifest.xml and other java class which help to build GUI in the Android by using XSLT transformation. Then use Android SDK to compile and build .apk by configure dependencies in Ant script. Other way, we can use from the beginning method to build .apk by using XSLT transformation. If I have misunderstanding or some wrong idea with regarding this, please correct me. Then If that's the case, you would want to find other stuff to add to the proposal so you have enough to do over the summer. I will seek for another output format during this period. We should also ask the other mentors if any are interested in this project and what their thoughts are. I'm hoping they'll chime in. Yes David. I also very appreciate if a mentor can help to me through out this project idea. We will wait until some one help us. I also think, this is a critical point with regarding where should I heading. If I tried to follow any difficult method to implement this idea, I'm wasting my time. So, any thoughts about this idea are highly valuable and appreciate for me. Thank you in Advance !. [1]. http://www.vogella.de/articles/DocBook/article.html#epub [2]. http://www.vogella.de/articles/XSLT/article.html [3]. http://www.w3.org/TR/xsl/ [4]. http://forum.sdx-developers.com/index.php?topic=3472.0 [5]. http://help.adobe.com/en_US/air/build/WS901d38e593cd1bac25d3d8c712b2d86751e-8000.html -- Regards Gihan Chanuka Karunarathne Department of Computer Science and Engineering University of Moratuwa Sri Lanka Twitter: https://twitter.com/#!/gihanchanuka LinkedIn: http://lk.linkedin.com/pub/gihan-karunarathne/25/ba3/993 -- Lars http://www.vogella.de - Eclipse, Android and Java Tutorials http://www.twitter.com/vogella - Lars on Twitter -- Regards Gihan Chanuka Karunarathne Department of Computer Science and Engineering University of Moratuwa Sri Lanka Twitter: https://twitter.com/#!/gihanchanuka LinkedIn: http://lk.linkedin.com/pub/gihan-karunarathne/25/ba3/993
RE: [docbook-apps] DocBook - PDF paths that aren't hugely expensive?
Hi Robin, I've had a lot of success with PrinceXML (http://www.princexml.com/) as a DocBook to PDF solution. Like Antenna House (which I haven't used), it allows you to control appearance via fairly robust CSS stylesheets. It's not free (about $500 for a single-user license last time I looked), but it's incredibly flexible for layout and design. Also note that while it can produce your PDF directly from the DocBook XML source, I find it much better to transform your DocBook to HTML (using the open source stylesheets) then process the HTML through Prince. This allows you to take advantage of some of DocBook's more powerful features- auto-TOCs, labeling, indices, etc. Good luck. jz -Original Message- From: Robin Lee Powell [mailto:rlpow...@digitalkingdom.org] Sent: Thursday, March 22, 2012 5:12 AM To: docbook-apps@lists.oasis-open.org Subject: [docbook-apps] DocBook - PDF paths that aren't hugely expensive? I don't mind paying for software but I can't afford the thousands that XEP costs, for exmaple. I'm really wondering what paths exist these days for turning DocBook into something that you can actually send to a book publisher (which seems to mean PDF, and that's certainly my preference, but I'm open to other options there)? I'm looking at http://www.dpawson.co.uk/docbook/tools.html#d884e128 as a starting point, and here's what I know: - dblatex is hugely brittle (trust me on this) - PassiveTeX appears to be dead - DocBook In ConTeXt was last updated in 2003, which means that even if it works it's pre-5.0 (you may notice from the ordering of this list that I like TeX's output style :) - FOP can't handle auto-width tables, which rules it out entirely for my purposes - xmlroff's compatibility page claims that it, also, doesn't do auto tables - wkhtml2pdf can't do page-number-based cross references, which means it's of no use for printed output Those are all the ones I've tried or seriously looked at. I could *really* use some pointers here. I'm feeling a bit grumpy about the whole thing because I was under the impression from the DocBook site that I could, ya know, use it to produce books. :) And so for that hasn't actually worked out very well. -Robin -- http://singinst.org/ : Our last, best hope for a fantastic future. .i ko na cpedu lo nu stidi vau loi jbopre .i danfu lu na go'i li'u .e lu go'i li'u .i ji'a go'i lu na'e go'i li'u .e lu go'i na'i li'u .e lu no'e go'i li'u .e lu to'e go'i li'u .e lu lo mamta be do cu sofybakni li'u - To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org - To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org
[docbook-apps] Olink sitemap for chunked HTML?
Hello, I'm stumped getting the sitemap right to resolve Olinks in chunked HTML. The Olinks between different files of the same document seem to come out fine. But Olinks between documents are broken. Bob Stayton's book, DocBook XSL: The Complete Guide, has solved lots of the DocBook XSL problems between my keyboard and chair. So I'm probably misreading the chapter on Olinks or missing something in the section about sitemaps, http://www.sagehill.net/docbookxsl/OlinkDetails.html#UsingSitemap Would one of you have a working, open source example of Olinks between docs in chunked HTML that I could read through to perhaps understand? If not, an example that demonstrates the problem is at https://github.com/markcraig/olink-test (with the problem showing up for example in target/docbkx/html/bogus-guide/index/ch01.html#olink-checks after you `mvn pre-site`; first link in the section works and it's inside the document; second link in the section fails to make it to the other document). Thanks for your time and your advice. Regards, Mark
Re: [docbook-apps] DocBook - PDF paths that aren't hugely expensive?
On Thu, Mar 22, 2012 at 08:48:55AM -0400, maxwell wrote: On Thu, 22 Mar 2012 03:11:37 -0700, Robin Lee Powell rlpow...@digitalkingdom.org wrote: - dblatex is hugely brittle (trust me on this) I guess I don't trust you on this. *chuckle* *That* was unexpected (not). :D We've been using dblatex for several years now on book-length grammars, with excellent results for articles, reports, and books. It's true that we don't exercise all the DocBook elements (we don't use most of the computational elements, for example), but I would be surprised to find dblatex having significant problems there. Between the command-line parameters to dblatex (which can be put into a .xsl file) and LaTeX style sheets, there's not much you can't tweak. What I was specifically referring to was docbook.sty, which I thought dblatex required you to use to function. It has really horrible things in it, like fixed sizes for elements that are based on A4 and won't work on anything else. I have just discovered (like, literally, 2 minutes before I sent this email) that I absolutely do *not* have to use docbook.sty, and in fact that there are alternative styles out there for this purpose. So, umm, sorry about that. -_- -Robin -- http://singinst.org/ : Our last, best hope for a fantastic future. .i ko na cpedu lo nu stidi vau loi jbopre .i danfu lu na go'i li'u .e lu go'i li'u .i ji'a go'i lu na'e go'i li'u .e lu go'i na'i li'u .e lu no'e go'i li'u .e lu to'e go'i li'u .e lu lo mamta be do cu sofybakni li'u - To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org
Re: [docbook-apps] Olink sitemap for chunked HTML?
Here's an example of a map that I am using for chunked HTML. It can be a little tricky to figure out what the relative path to other documents is. It all depends on how you are packaging the HTML files. Mine are grouped in directories for the product, then the document, and then a directory named html. So my links from one document to another have to go up three directories in the hierarchy and then back down the path to the directory that holds the chunked files for each specific document. targetset sitemap dir name=documentation document targetdoc=ERDSupportingInfo baseuri=../../../platform/documentfoo/html/documentfooTargetswebhelp;/document document targetdoc=ERDSupportingInfo baseuri=../../../otherproduct/bardocument/html/bardocumentTargetswebhelp;/document /dir /sitemap /targetset Peter On Thu, Mar 22, 2012 at 2:07 PM, Mark Craig mark.cr...@gmail.com wrote: Hello, I'm stumped getting the sitemap right to resolve Olinks in chunked HTML. The Olinks between different files of the same document seem to come out fine. But Olinks between documents are broken. Bob Stayton's book, DocBook XSL: The Complete Guide, has solved lots of the DocBook XSL problems between my keyboard and chair. So I'm probably misreading the chapter on Olinks or missing something in the section about sitemaps, http://www.sagehill.net/docbookxsl/OlinkDetails.html#UsingSitemap Would one of you have a working, open source example of Olinks between docs in chunked HTML that I could read through to perhaps understand? If not, an example that demonstrates the problem is at https://github.com/markcraig/olink-test (with the problem showing up for example in target/docbkx/html/bogus-guide/index/ch01.html#olink-checks after you `mvn pre-site`; first link in the section works and it's inside the document; second link in the section fails to make it to the other document). Thanks for your time and your advice. Regards, Mark - To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org
Re: [docbook-apps] DocBook - PDF paths that aren't hugely expensive?
On Thu, Mar 22, 2012 at 01:57:18PM +, Jason Zech wrote: Hi Robin, I've had a lot of success with PrinceXML (http://www.princexml.com/) as a DocBook to PDF solution. Like Antenna House (which I haven't used), it allows you to control appearance via fairly robust CSS stylesheets. It's not free (about $500 for a single-user license last time I looked), but it's incredibly flexible for layout and design. Also note that while it can produce your PDF directly from the DocBook XML source, I find it much better to transform your DocBook to HTML (using the open source stylesheets) then process the HTML through Prince. This allows you to take advantage of some of DocBook's more powerful features- auto-TOCs, labeling, indices, etc. That's an interesting option. In a way, I'd rather go via (X)HTML so that the visual layout is consistent. The problem I've had with every such mothed I've tried is that internal cross references show up as see section 2.1 wibble instead of see page 23. For a printed book, I strongly prefer the later, or at least that the page number be included. Does Prince handle that? -Robin - To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org
RE: [docbook-apps] DocBook - PDF paths that aren't hugely expensive?
You can use the content property in CSS to replace text, and they have some prefixed CSS selectors/properties to convert an anchor link into a page reference. You'd have to look at their documentation as to how to handle it. This article gives a nice overview of some of the book-specific capabilities they have: http://www.alistapart.com/articles/boom/ -Original Message- From: Robin Lee Powell [mailto:rlpow...@digitalkingdom.org] Sent: Thursday, March 22, 2012 1:39 PM To: Jason Zech Cc: docbook-apps@lists.oasis-open.org Subject: Re: [docbook-apps] DocBook - PDF paths that aren't hugely expensive? On Thu, Mar 22, 2012 at 01:57:18PM +, Jason Zech wrote: Hi Robin, I've had a lot of success with PrinceXML (http://www.princexml.com/) as a DocBook to PDF solution. Like Antenna House (which I haven't used), it allows you to control appearance via fairly robust CSS stylesheets. It's not free (about $500 for a single-user license last time I looked), but it's incredibly flexible for layout and design. Also note that while it can produce your PDF directly from the DocBook XML source, I find it much better to transform your DocBook to HTML (using the open source stylesheets) then process the HTML through Prince. This allows you to take advantage of some of DocBook's more powerful features- auto-TOCs, labeling, indices, etc. That's an interesting option. In a way, I'd rather go via (X)HTML so that the visual layout is consistent. The problem I've had with every such mothed I've tried is that internal cross references show up as see section 2.1 wibble instead of see page 23. For a printed book, I strongly prefer the later, or at least that the page number be included. Does Prince handle that? -Robin - To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org
Re: [docbook-apps] DocBook - PDF paths that aren't hugely expensive?
Great, thanks! -Robin On Thu, Mar 22, 2012 at 06:43:32PM +, Jason Zech wrote: You can use the content property in CSS to replace text, and they have some prefixed CSS selectors/properties to convert an anchor link into a page reference. You'd have to look at their documentation as to how to handle it. This article gives a nice overview of some of the book-specific capabilities they have: http://www.alistapart.com/articles/boom/ -Original Message- From: Robin Lee Powell [mailto:rlpow...@digitalkingdom.org] Sent: Thursday, March 22, 2012 1:39 PM To: Jason Zech Cc: docbook-apps@lists.oasis-open.org Subject: Re: [docbook-apps] DocBook - PDF paths that aren't hugely expensive? On Thu, Mar 22, 2012 at 01:57:18PM +, Jason Zech wrote: Hi Robin, I've had a lot of success with PrinceXML (http://www.princexml.com/) as a DocBook to PDF solution. Like Antenna House (which I haven't used), it allows you to control appearance via fairly robust CSS stylesheets. It's not free (about $500 for a single-user license last time I looked), but it's incredibly flexible for layout and design. Also note that while it can produce your PDF directly from the DocBook XML source, I find it much better to transform your DocBook to HTML (using the open source stylesheets) then process the HTML through Prince. This allows you to take advantage of some of DocBook's more powerful features- auto-TOCs, labeling, indices, etc. That's an interesting option. In a way, I'd rather go via (X)HTML so that the visual layout is consistent. The problem I've had with every such mothed I've tried is that internal cross references show up as see section 2.1 wibble instead of see page 23. For a printed book, I strongly prefer the later, or at least that the page number be included. Does Prince handle that? -Robin - To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org -- http://singinst.org/ : Our last, best hope for a fantastic future. .i ko na cpedu lo nu stidi vau loi jbopre .i danfu lu na go'i li'u .e lu go'i li'u .i ji'a go'i lu na'e go'i li'u .e lu go'i na'i li'u .e lu no'e go'i li'u .e lu to'e go'i li'u .e lu lo mamta be do cu sofybakni li'u - To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org
Re: [docbook-apps] Olink sitemap for chunked HTML?
Aha! Thanks very much, Peter. I got confused, thinking I only needed the baseuri attribute for single-page HTML output. That fixes it the problem completely. Before (and broken): sitemap dir name='html' dir name='another-doc' dir name='index' document targetdoc='another-doc' another-doc; /document /dir /dir dir name='bogus-guide' dir name='index' document targetdoc='bogus-guide' bogus-guide; /document /dir /dir /dir /sitemap After (and fixed): sitemap dir name='html' dir name='another-doc' dir name='index' document targetdoc='another-doc' baseuri='../../another-doc/index/' another-doc; /document /dir /dir dir name='bogus-guide' dir name='index' document targetdoc='bogus-guide' baseuri='../../bogus-guide/index/' bogus-guide; /document /dir /dir /dir /sitemap Thanks again. Regards, Mark On Thu, Mar 22, 2012 at 7:35 PM, Peter Desjardins peter.desjardins...@gmail.com wrote: Here's an example of a map that I am using for chunked HTML. It can be a little tricky to figure out what the relative path to other documents is. It all depends on how you are packaging the HTML files. Mine are grouped in directories for the product, then the document, and then a directory named html. So my links from one document to another have to go up three directories in the hierarchy and then back down the path to the directory that holds the chunked files for each specific document. targetset sitemap dir name=documentation document targetdoc=ERDSupportingInfo baseuri=../../../platform/documentfoo/html/documentfooTargetswebhelp;/document document targetdoc=ERDSupportingInfo baseuri=../../../otherproduct/bardocument/html/bardocumentTargetswebhelp;/document /dir /sitemap /targetset Peter On Thu, Mar 22, 2012 at 2:07 PM, Mark Craig mark.cr...@gmail.com wrote: Hello, I'm stumped getting the sitemap right to resolve Olinks in chunked HTML. The Olinks between different files of the same document seem to come out fine. But Olinks between documents are broken. Bob Stayton's book, DocBook XSL: The Complete Guide, has solved lots of the DocBook XSL problems between my keyboard and chair. So I'm probably misreading the chapter on Olinks or missing something in the section about sitemaps, http://www.sagehill.net/docbookxsl/OlinkDetails.html#UsingSitemap Would one of you have a working, open source example of Olinks between docs in chunked HTML that I could read through to perhaps understand? If not, an example that demonstrates the problem is at https://github.com/markcraig/olink-test (with the problem showing up for example in target/docbkx/html/bogus-guide/index/ch01.html#olink-checks after you `mvn pre-site`; first link in the section works and it's inside the document; second link in the section fails to make it to the other document). Thanks for your time and your advice. Regards, Mark - To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org
