Is a long XSLT file a code smell?
In imperative programming languages it's generally acknowledged that very large classes and/or sub-routines are an indication of possible problems, e.g. a class that is doing too much. Such a class should be considered for refactoring into multiple smaller classes, each having a clearer and more well defined function thus making for code that is more easily unit tested, maintained etc.
Does a similar rule apply for XSL transforms?
When I see a large XSLT my instinct is that it needs breaking up in some way similar to how I would break up and refactor a large class.