You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@xalan.apache.org by "Mukul Gandhi (Jira)" <ji...@apache.org> on 2026/02/28 15:25:00 UTC
[jira] [Updated] (XALANJ-2660) Implementation of xpath 3.1 function fn:unparsed-text(), for XalanJ's interpretive processor
[ https://issues.apache.org/jira/browse/XALANJ-2660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mukul Gandhi updated XALANJ-2660:
---------------------------------
Fix Version/s: xslt3.0_alpha1
> Implementation of xpath 3.1 function fn:unparsed-text(), for XalanJ's interpretive processor
> --------------------------------------------------------------------------------------------
>
> Key: XALANJ-2660
> URL: https://issues.apache.org/jira/browse/XALANJ-2660
> Project: XalanJ2
> Issue Type: New Feature
> Security Level: No security risk; visible to anyone(Ordinary problems in Xalan projects. Anybody can view the issue.)
> Components: Xalan-interpretive, XPath-function
> Reporter: Mukul Gandhi
> Assignee: Mukul Gandhi
> Priority: Major
> Fix For: xslt3.0_alpha1
>
> Attachments: fn_unparsed-text_test_files.zip
>
>
> I'm creating this jira issue, to track implementation of XPath 3.1 function fn:unparsed-text().
> I've written little bit of code for this, that has been committed to XalanJ dev repos's branch xalan-j_xslt3.0.
> Also attached are few working test cases, for this jira issue.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@xalan.apache.org
For additional commands, e-mail: dev-help@xalan.apache.org