 |
 |
 |
Yeah, I knew about the bugs in XML-Spy and IE. If you
include the stylesheet in your XML document and open directly in the browser, IE
still overrides the preserve-space (this is a bug, not a feature).
If, however, you convert the file to HTML (say via Saxon or
Xalan) before opening it in the browser, it will work. But this may not fall
within the guidelines of your project (e.g., if you need to actual XML available
in the background in the browser).
From: russ@w...
[mailto:russ@w...]
Sent: Friday, December 02,
2005 2:16 PM
To: Doug Rudder
Cc:
xml-dev@l...
Subject: RE: [xml-dev] Preserving whitespace
between nodes - XSLT
Thanks for the reply, Doug. However, I tried this before and just tried
again, and still get the same results. I'm putting this line before the first
template. The space is still removed, using IE and XMLSpy">XMLSpy.
Thanks
Russ
--------
Original Message --------
Subject: RE: [xml-dev] Preserving whitespace
between nodes - XSLT
From: Doug Rudder
<drudder@d...>
Date: Fri, December 02, 2005 2:47 pm
To:
"'russ@w...'" <russ@w...>,
xml-dev@l...
Include <xsl:preserve-space
elements="text"/> in your XSLT. We commonly
use
<xsl:strip-space> to remove unwanted space (newlines, etc.),
but use
preserve space for any elements containing text that allows mixed
content.
For example:
<xsl:strip-space
elements="*"/>
<xsl:preserve-space elements="para title item
entry"/>
=======================
Douglas Rudder
XML
Analyst
WoltersKluwer Health - Clinical Tools
77 West Port Plaza,
Suite 450
Phone: 314-216-2227
e-mail:
drudder@d...
www.drugfacts.com
=======================
>
-----Original Message-----
> From: russ@w...
> [mailto:russ@w...]
> Sent: Friday,
December 02, 2005 1:12 PM
> To: xml-dev@l...
> Subject:
[xml-dev] Preserving whitespace between nodes - XSLT
>
>
>
> Hi,
>
> I have an XSLT question that I'm
unable to answer, and I'm
> starting to think there may not be an
answer. Before I give
> up, allow me to consult your
expertise.
>
> I'm trying to preserve significant whitespace
between element
> nodes during transformation. For example, if I had
some XML like:
>
> <x>text <x>text</x>
<x>text</x> text</x> (note the space in
> the
middle, between nodes)
>
> ...and some kind of simple transform
like:
>
> <xsl:template match="*">
>
<x>
>
<xsl:apply-templates/>
> </x>
>
</xsl:template>
>
> ... I end up with:
>
>
<x>text <x>text</x><x>text</x>
text</x>
> (space is removed)
>
> I understand why
this is happening... I'm just looking for a
> way around it, if there
is one. It becomes significant when
> the element nodes ultimately
indicate text-range formatting, such as:
>
> <div>text
<b>bold</b> <i>italics</i> text</div>
>
> ...which erroneously becomes "text bolditalics text."
>
> Thanks for any insight.
>
> Russ
>
>
>
>
>
>
>
>
-----------------------------------------------------------------
>
The xml-dev list is sponsored by XML.org
>
<http://www.xml.org>, an initiative of OASIS
>
<http://www.oasis-open.org>
>
> The list archives are at
http://lists.xml.org/archives/xml-dev/
>
> To subscribe or
unsubscribe from this list use the subscription
> manager:
<http://www.oasis-open.org/mlmanage/index.php>
>
|
 | 

|  |
These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.
|  |
| |
 |
 |
 |