On Thu, Aug 28, 2014 at 2:44 AM, Gour <[email protected]> wrote: > In the past I bought XSLT book, but now wonder where was my > intelligence that I was considering doing XSLT programming. :-) >
I can make you feel better perhaps by saying I've spent years of my life working with XSLT and buying books about it. For a long time, I was convinced it was a holy grail for text transformation. Before we had good dynamic languages like Ruby, Python, Groovy, etc, with built-in transformers, maybe it _was_ a reasonable approach over doing something in C or (dare I say it) PHP. Experience has taught me that when you need to do programming tasks, it's best to use a programming language. Of course, we will always have a need for declarative languages like CSS so you can control the behavior without having to dive into programming. But it's hard to argue that when you have 200,000 lines of XML like in the DocBook XSL, it's time to think about a different approach :) I'll also mention that as I watch this list, more than half the questions are how to find some setting buried deep in some XSL stylesheet. My goal in Asciidoctor PDF is to provide a Bootstrap-like declarative theme language for the high-level stuff, like changing font colors, and pointing anyone wanting to control the output in a fine-grained way to simply extend the converter in any language of their choice (since Asciidoctor runs in Ruby and on the JVM...even use Python!) -Dan -- Dan Allen | http://google.com/profiles/dan.j.allen -- You received this message because you are subscribed to the Google Groups "asciidoc" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/asciidoc. For more options, visit https://groups.google.com/d/optout.
