XSL Formatting Objects Developer's Handbook (Developer's...

Features

• Cover Type: Paperback with 456 pages
• Published by: Sams November 11, 2002
• Written in: English
• ISBN 10 Number: 0672322811
• ISBN 13 Number: 978-0672322815
• Book Dimensions: 9.1 x 7.4 x 1 inches
• Weighs: 1.7 pounds

Reader Reviews
I rated the book 4 stars because it provides solid examples in many areas of XSL FO that actually work. Even though the W3C recommendation has been out since October, 2001, we have just started to see accessible books on XSL FO, and this is the best. The author provides a hands-on view and gives you examples that work and get you up and going quickly. Not a lot of wading through esoterica wondering how you would even get started with a simple document. However, that is not to say that the book is without problems. Let me list them in order: 1. Software that will format XSL FO is in its infancy. Therefore, although the examples work, you have to burn some shoe leather finding software that is compliant with the spec. It would have been better if the author had bundled an evaluation copy of either the Antenna House software which he claimed would format *almost* all of the examples or his own XFC software that he developed for IBM alphaworks. I did download the XFC software, but although written in Java, it is very much oriented towards a windows platform, and I could not concoct a way to get it to run on my linux machine (I gave up after discovering I had a non-compliant version of the xerces package). I think one of the reasons Michael Kay's Wrox XSLT book has been so popular has been because of his work on Saxon. Software would have made this book a 5 star book. 2. Downloadable examples. These were not available at first, but the author had them up within a week of my email, correcting an error on the publisher's web page. So, this went from a problem to a plus. 3. Pagination (Chapter 8) is not very clear. Some of the figure references seem to have been reversed (generally, in many places where the author refers to figure 8.1 you should read 8.2 and vice versa). This chapter needed a concrete example to start. Then the author could have gotten into the more esoteric issue of overlapping regions. Comment | | (Report this)