You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@xalan.apache.org by "pohl (JIRA)" <xa...@xml.apache.org> on 2005/06/02 16:15:52 UTC

[jira] Commented: (XALANC-245) substring-before and substring-after

     [ http://issues.apache.org/jira/browse/XALANC-245?page=comments#action_66859 ]
     
pohl commented on XALANC-245:
-----------------------------

We have encountered this exact issue in XalanJ 2.6.0.  I can't
find a XalanJ issue that tracks fixing it.

Is it Xalan developer policy to fix both implementations at the
same time, or do we need a separate issue to be entered?

> substring-before and substring-after
> ------------------------------------
>
>          Key: XALANC-245
>          URL: http://issues.apache.org/jira/browse/XALANC-245
>      Project: XalanC
>         Type: Bug
>   Components: XPathC
>     Versions: 1.4.x
>  Environment: Operating System: Linux
> Platform: PC
>     Reporter: Henry Houh
>     Assignee: Xalan Developers Mailing List
>  Attachments: substring-bug.html, substring-bug.xml, substring-bug.xsl
>
> 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.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xalan-dev-help@xml.apache.org