Subject: [xsl] Trimming (formatting-only) leading tabs/spaces from XSLT - issues? From: Philip Fearon <philipfearon@xxxxxxxxxxx> Date: Tue, 7 Jun 2011 13:47:05 +0100 |
Say, (hypothetically) there was an XSLT-based system that included an editor that (if used) needed to trim leading tabs/spaces from XSLT when first loading a file, so as to provide a continously formatted view of the XSLT code as it was edited. Provided that this was done relatively reliably (i.e. without trimming significant tab and space characters) and predictably, would this cause significant problems in an XSLT development, test or production environment? So, would other editors, viewers, diff-tools, version-control systems, auto-documentation systems etc. be adversely affected? If such formatting characters needed to be added again, would it be best just to add them when required (letting the consumer choose the formatting style)? I ask, because the popular consensus seems to be that trimming non-XSLT code of formatting characters in this way would be a major issue. This is because of established working methods and tools that don't/won't/can't tolerate changes to whitespace (this seems to be quite an emotive issue).Now, whitespace has added significance (an understatement I think) in XML/XSLT systems. My experience (such that it is) in XSLT is that working methods and tools have therefore evolved to manage whitespace (removing it, comparing it, adding it, or ignoring it) more effectively than text-only tools, trimming XSLT of tabs/spaces therefore shouldn't be a problem and may even provide more flexibility, does this hold up in the wider XSLT world? Phil Fearon http://qutoric.com
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
Re: [xsl] xml:space preserve on ele, David Carlisle | Thread | Re: [xsl] Trimming (formatting-only, Dimitre Novatchev |
Re: [xsl] xml:space preserve on ele, Michael Kay | Date | Re: [xsl] Trimming (formatting-only, Dimitre Novatchev |
Month |