Subjects
Home
VOTE Move XML Commons to Xerces
Commented: (XERCESJ 589) Bug with pattern restriction on long strings
: Xerces J 2 8 1 Release on Wednesday, September 13th
: Xerces J 2 9 0 Release on Wednesday, November 22nd
Commented: (XERCESJ 1066) Restriction+choice+substitutionGroup error
Commented: (XERCESJ 1178) Error getting prefix for an attribute with no n
Updated: (XERCESJ 1244) XMLSchemaValidator does not contribute element 's
Some consideration about the xerces DOM implementation
Updated: (XERCESJ 1066) Restriction+choice+substitutionGroup error
Commented: (XERCESJ 1227) Poor performance / OutOfMemoryError for sequenc
retain exception stack traces
Updated: (XERCESJ 1193) NPE or hang when parsing using the "continue afte
Future of NekoHTML
Commented: (XERCESJ 1203) NPE in XMLDTDProcessor
DOM Level 3 APIs for Xalan J and a new Xalan release (2 7 1)
: xml commons external 1 3 04 Release on Wednesday, November 22nd
Commented: (XERCESJ 1247) Incorrect location information on SAX when usin
XInclude exceptions how to mirror Xerces J functionality into Xerces C++?
First proposal on SoC project "Add support for the StAX (JSR 173) cursor API
: xml commons resolver 1 2 Release on Wednesday, November 22nd
Typo in RangeToken java Please check
Validator features
java lang ClassCastException when adopting Node
using the org apache xerces impl xs identity package
Updated: (XERCESJ 1257) buffer overflow in UTF8Reader for characters out
Problem with ref attributes and schema validation
Updated: (XERCESJ 122) XMLSchemaValidator does not contribute element 's d
Performance problem under load Xerces with Weblogic 9 x
remove ignored memory allocation
Commented: (XERCESJ 1177) SAXXMLStreamReader doesn 't always report namesp
Commented: (XERCESJ 977) Null pointer exception during DOM parsing
Commented: (XERCESJ 1197) Code cleanup for org apache xml serialize
Commented: (XERCESJ 1201) Initial contribution for StAX Event API
Updated: (XERCESJ 1061) Regex "$ " and "^ " characters treated as special c
Commented: (XERCESJ 1199) SAXXMLStreamReader should attempt to register a
Commented: (XERCESJ 1061) Regex "$ " and "^ " characters treated as special
Updated: (XERCESJ 589) Bug with pattern restriction on long strings
StackOverflow
xerces Range unnecessarily not garbage collectable if not detached
Updated: (XERCESJ 1178) Error getting prefix for an attribute with no nam
Bug in xs:redefine
Commented: (XERCESJ 1204) Can not set XMLEntityResolver for LSParser
Updated: (XERCESJ 1253) Prototype for SoC2007 project "Add support for th
Updated: (XERCESJ 1259) Add SteamFilter Function to SoC2007 project "Add
Assigned: (XERCESJ 444) SAXException thrown by EntityResolver is reported
Google Summer of Code 2007
Xerces J and XInclude relative path issue
Assigned: (XERCESJ 206) Stack overflow when using a schema validation
Commented: (XERCESJ 1215) Restrictions involving two levels of substituti
Closed: (XERCESJ 1203) NPE in XMLDTDProcessor
non overriding equals methoda
Resolved: (XERCESJ 1079) invalid value returned for TOTALDIGITS facet in
Xerces AS3 port
Updated: (XERCESJ 325) Regular Expression; Pattern "| " clause order de
Updated: (XERCESJ 1196) Javadoc generation fails on Java SE 5 0
Closed: (XERCESJ 1202) DTD validation on XIncluded documents when the sch
Created: (XERCESJ 1124) Nonspecific schema error message
a bug in xerces
Updated: (XERCESJ 1201) Initial contribution for StAX Event API
Closed: (XERCESJ 1254) Empty uris in targetNamespace attribute not report
Links
Home
Oracle database error code
 
Search:  
Power your search with and, or, +, -, or "some phrase" operators.
could a line break be lost during parsing?

could a line break be lost during parsing?

2003-01-17       - By Christopher Ebert
Reply:     1     2     3     4     5     6  


   Hi,

   Oh, yes - sorry, the subject of the message made me think you were looking
for a problem in the parser. :)

   So, really you have an XSL issue, yes? This isn't really the list for XSL
issues. Xalan is the Apache XSL processor -- the xalan list would likely be
more helpful.

   That said, I'm guessing the line breaks are not appearing as 0xA. Is that
what's in your input file? Have you looked at the DOM element you get for the
text you're trying to process? You might find 0xD instead, (any change more
likely due to Java than Xerces). If I recall my ASCII, 0xA is line feed and 0xD
is carriage return. I don't remember off hand which one Java uses for a line
break ('\n').

   HTH


   Cheers,


           Chris


-----Original Message-----
From: dongjiang tang [mailto:dtang@(protected)]
Sent: Friday, January 17, 2003 11:15 AM
To: xerces-j-user@(protected)
Subject: Re: could a line break be lost during parsing?


Hi, thank you for the reply.
I was trying to add the <br> by a template as showed in the previous mail, but
did not get it.
I know the HTML will not show the line break, but I did look at the source of
that HTML page generated by my xsl template, I did not see the line break
either.

dongjiang

<xsl:template name="add-line-breaks">
  <xsl:param name="string" select="." />
  <xsl:choose>
     <xsl:when test="contains($string, '&#xA;')">
        <xsl:value-of select="substring-before($string, '&#xA;')" />
        <br />
        <xsl:call-template name="add-line-breaks">
           <xsl:with-param name="string"
                           select="substring-after($string, '&#xA;')" />
        </xsl:call-template>
     </xsl:when>
     <xsl:otherwise>
        <xsl:value-of select="$string" />
     </xsl:otherwise>
  </xsl:choose>
</xsl:template>
a





<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">


<META content="MSHTML 6.00.2800.1126" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT face=Arial color=#0000ff size=2></FONT>&nbsp;</DIV>
<DIV><SPAN class=208501820-17012003><FONT face=Arial color=#0000ff
size=2>&nbsp;&nbsp;&nbsp; Hi,</FONT></SPAN></DIV>
<DIV><SPAN class=208501820-17012003><FONT face=Arial color=#0000ff
size=2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=208501820-17012003>&nbsp;&nbsp;&nbsp; <FONT face=Arial
color=#0000ff size=2>Oh, yes - sorry, the subject of the message made me think
you were looking for a problem in the parser. :)</FONT></SPAN></DIV>
<DIV><SPAN class=208501820-17012003><FONT face=Arial color=#0000ff
size=2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=208501820-17012003>&nbsp;&nbsp;&nbsp; <FONT face=Arial
color=#0000ff size=2>So, really you have an XSL issue, yes? This isn't really
the list for XSL issues. Xalan is the Apache XSL processor -- the xalan list
would likely be more helpful.</FONT></SPAN></DIV>
<DIV><SPAN class=208501820-17012003><FONT face=Arial color=#0000ff
size=2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=208501820-17012003>&nbsp;&nbsp;&nbsp; <FONT face=Arial
color=#0000ff size=2>That said, I'm guessing the line breaks are not appearing
as 0xA. Is that what's in your input file? Have you looked at the DOM element
you get for the text you're trying to process? You might find 0xD instead, (any
change more likely due to Java than Xerces). If I recall my ASCII, 0xA is line
feed and 0xD is carriage return. I don't remember off hand which one Java uses
for a line break ('\n').</FONT></SPAN></DIV>
<DIV><SPAN class=208501820-17012003><FONT face=Arial color=#0000ff
size=2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=208501820-17012003>&nbsp;&nbsp;&nbsp; <FONT face=Arial
color=#0000ff size=2>HTH</FONT></SPAN></DIV>
<DIV><SPAN class=208501820-17012003><FONT face=Arial color=#0000ff
size=2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=208501820-17012003><FONT face=Arial color=#0000ff
size=2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=208501820-17012003>&nbsp;&nbsp;&nbsp; <FONT face=Arial
color=#0000ff size=2>Cheers,</FONT></SPAN></DIV>
<DIV><SPAN class=208501820-17012003><FONT face=Arial color=#0000ff
size=2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=208501820-17012003><FONT face=Arial color=#0000ff
size=2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN
class=208501820-17012003>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&nbsp;&nbsp;
<FONT face=Arial color=#0000ff size=2>Chris</FONT></SPAN></DIV>
<DIV><SPAN class=208501820-17012003></SPAN>&nbsp;</DIV>
<BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px">
 <DIV class=OutlookMessageHeader dir=ltr align=left><FONT face=Tahoma
 size=2>-----Original Message-----<BR><B>From:</B> dongjiang tang
 [mailto:dtang@(protected)]<BR><B>Sent:</B> Friday, January 17, 2003 11:15
 AM<BR><B>To:</B> xerces-j-user@(protected)<BR><B>Subject:</B> Re: could a
 line break be lost during parsing?<BR><BR></FONT></DIV>
 <DIV><FONT face=Arial size=2>Hi, thank you for the reply. </FONT></DIV>
 <DIV><FONT face=Arial size=2>I was trying to add the &lt;br&gt; by a template
 as showed in the previous mail, but did not get it. </FONT></DIV>
 <DIV><FONT face=Arial size=2>I know the HTML will not show the line break,
but
 I did look at the source of that HTML page&nbsp;generated by my xsl template,
 I did not see the line break either.</FONT></DIV>
 <DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
 <DIV><FONT face=Arial size=2>dongjiang</FONT></DIV>
 <DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
 <DIV>&lt;xsl:template name="add-line-breaks"&gt;<BR>&nbsp;&nbsp; &lt;xsl
:param
 name="string" select="." /&gt;<BR>&nbsp;&nbsp;
 &lt;xsl:choose&gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;xsl:when
 test="contains($string,
 '&amp;#xA;')"&gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
 &lt;xsl:value-of select="substring-before($string, '&amp;#xA;')"
 /&gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;br
 /&gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
 &lt;xsl:call-template
 name="add-line-breaks"&gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp
;&nbsp;&nbsp;&nbsp;
 &lt;xsl:with-param
 name="string"<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&nbsp;&nbsp;&nbsp;&nbsp;
 select="substring-after($string, '&amp;#xA;')"
 /&gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
 &lt;/xsl:call-template&gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
 &lt;/xsl:when&gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
 &lt;xsl:otherwise&gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
 &lt;xsl:value-of select="$string" /&gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
 &lt;/xsl:otherwise&gt;<BR>&nbsp;&nbsp;
 &lt;/xsl:choose&gt;<BR>&lt;/xsl:template&gt;<BR><FONT face=Arial
 size=2>a</FONT></DIV>
 <DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
 <BLOCKQUOTE dir=ltr
 style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT:
#000000 2px solid; MARGIN-RIGHT: 0px">
   <DIV style="FONT: 10pt arial"><FONT face=Arial
 size=2>&nbsp;</DIV></FONT></BLOCKQUOTE></BLOCKQUOTE></BODY></HTML>