Cart
[Home] [By Thread] [By Date] [Recent Entries]
On 07/06/2011 13:47, Philip Fearon wrote:
more effectively than text-only tools, trimming XSLT of tabs/spaces therefore shouldn't be a problem a well so long as the thing that was trimming knew enough xslt syntax not to trim significant white space, which means knowing the interrelation between xsl:text xsl:strip-space xsl:preserve-space and xml:space, and in general (to know if xsl:strip-space or xsl:preserve-space apply), it needs to know full xslt pattern matching behaviour. (in practice you might want to assume that xsl:strip-space xsl:preserve space and xml:space aren't applied to the xsl file, which simplifies things, but will lead to failures in edge cases). However even if the white space formatter does only change insignificant white space, so the reformatting won't affect XML processing, it can be terribly annoying (and space costly) if the code is being stored in a source code repository that (essentially) is storing line based diffs. If every time you touch the file it reflows it (or converts all line endings or whatever) then that ends up with a much bigger than expected diff showing up in change log at each stage. David
This e-mail has been scanned for all viruses by Star. The service is powered by MessageLabs. ________________________________________________________________________
|
