DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=17265>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=17265

substring-before and substring-after

           Summary: substring-before and substring-after
           Product: XalanC
           Version: 1.4.x
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: XPathC
        AssignedTo: [EMAIL PROTECTED]
        ReportedBy: [EMAIL PROTECTED]


When
  substring-before("Some string with a newline","&#xA") 
or 
  substring-after("Some string with a newline","&#xA") 
are called, they return strings of 0 length, even though 
  contains("Some string with a newline","&#xA") 
evaluates to TRUE.

When the split string is expanded to include a non-escaped character, 
such ".&#xA", the routines return proper values and treats the newline 
character properly.

Reply via email to