When copying the data and stylesheet into OxygenXML and also enabling bidi
support, the XSLT processing works fine.
<?xml version="1.0" encoding="UTF-8"?>
<foo>
<bar>𐑄𐐮𐑅 𐐮𐑆 𐐾𐐲𐑅𐐻 <word origerror="𐑂𐐯𐑉𐐮">𐐻𐐭</word> 𐑁𐐲𐑌𐐮</bar>
</foo>
So your problems may come form some details in your setup? How are you running
the transform?
BTW, interesting letters!
- Michael
Am 07.07.2016 um 20:54 schrieb Kenneth Reid Beesley
krbeesley(_at_)gmail(_dot_)com
<xsl-list-service(_at_)lists(_dot_)mulberrytech(_dot_)com>:
I now see that some of my own attempts also worked, on the same ASCII-based
example.
***** Suspected bug involving supplementary characters *****
But my real task involves an input XML document, in UTF-8 encoding, that
consists of Deseret Alphabet characters, which are encoded in the
supplementary area. In such a case, the resulting text content in the <word>
element, copied from an original attribute value, is corrupted. I saw such
corruption in my own attempts, and couldn’t understand what was happening.
--~----------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
EasyUnsubscribe: http://lists.mulberrytech.com/unsub/xsl-list/1167547
or by email: xsl-list-unsub(_at_)lists(_dot_)mulberrytech(_dot_)com
--~--