[
https://issues.apache.org/jira/browse/XALANJ-2419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16164487#comment-16164487
]
Jesper Steen Møller edited comment on XALANJ-2419 at 9/13/17 11:03 AM:
-----------------------------------------------------------------------
The Xalan project appears quite dormant, which is sad, but understandable. I
just came across this quite old posting on the subject:
https://intellectualcramps.wordpress.com/2011/06/03/xalan-a-step-closer-to-the-attic/
I suggest one of two courses of action:
* Contact the Xalan PMC (use the mailing list, not just JIRA) and volunteer to
help in putting out a new release (i.e. look for bugs with patches, or related
Unicode issues, e.g. XALANJ-2610). You can find about the current PMC members
and committers here: https://projects.apache.org/committee.html?xalan - ASF
house rules say that you need three positive PMC votes to allow a new release.
(Perhaps economic incentives work, i.e. pay existing committers to work on the
release)
* Fork Xalan-J on GitHub or similar a place. You'll likely have to rename the
project so Apache's trademarks aren't infringed, but the but it should be
possible to keep the package names, thus allowing for backwards compatibility
(But I'm not a lawyer!)
was (Author: jespersm):
The Xalan project appears quite dormant, which is sad, but understandable. I
just came across this quite old posting on the subject:
https://intellectualcramps.wordpress.com/2011/06/03/xalan-a-step-closer-to-the-attic/
I suggest that one of two courses of action:
* Contact the Xalan PMC (use the mailing list, not just JIRA) and volunteer to
help in putting out a new release (i.e. look for bugs with patches, or related
Unicode issues, e.g. XALANJ-2610). You can find about the current PMC members
and committers here: https://projects.apache.org/committee.html?xalan - ASF
house rules say that you need three positive PMC votes to allow a new release.
(Perhaps economic incentives work, i.e. pay existing committers to work on the
release)
* Fork Xalan-J on GitHub or similar a place. You'll likely have to rename the
project so Apache's trademarks aren't infringed, but the but it should be
possible to keep the package names, thus allowing for backwards compatibility
(But I'm not a lawyer!)
> Astral characters written as a pair of NCRs with the surrogate scalar values
> when using UTF-8
> ---------------------------------------------------------------------------------------------
>
> Key: XALANJ-2419
> URL: https://issues.apache.org/jira/browse/XALANJ-2419
> Project: XalanJ2
> Issue Type: Bug
> Components: Serialization
> Affects Versions: 2.7.1
> Reporter: Henri Sivonen
> Attachments: XALANJ-2419-fix.txt, XALANJ-2419-tests.txt
>
>
> org.apache.xml.serializer.ToStream contains the following code:
> else if (m_encodingInfo.isInEncoding(ch)) {
> // If the character is in the encoding, and
> // not in the normal ASCII range, we also
> // just leave it get added on to the clean characters
>
> }
> else {
> // This is a fallback plan, we should never get here
> // but if the character wasn't previously handled
> // (i.e. isn't in the encoding, etc.) then what
> // should we do? We choose to write out an entity
> writeOutCleanChars(chars, i, lastDirtyCharProcessed);
> writer.write("&#");
> writer.write(Integer.toString(ch));
> writer.write(';');
> lastDirtyCharProcessed = i;
> }
> This leads to the wrong (latter) if branch running for surrogates, because
> isInEncoding() for UTF-8 returns false for surrogates. It is always wrong
> (regardless of encoding) to escape a surrogate as an NCR.
> The practical effect of this bug is that any document with astral characters
> in it ends up in an ill-formed serialization and does not parse back using an
> XML parser.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org
For additional commands, e-mail: dev-h...@xalan.apache.org
