Sometimes query console output can be misleading, since it's creating a display. Another way to test is xdmp:save to the disk and look there.
Do you have a small example to try? /ch On Tue, Nov 7, 2017 at 6:22 PM, Mark Donoghue <m.donog...@ieee.org> wrote: > Hi, > > I am running a query in the query console that retrieves a document from the > database, invokes an XSLT and stores the result over the same document URI. > > The purpose of the XSLT is to unescape double-escaped character entities > (i.e.: &amp;). Following what I thought was standard practice, the XSLT > replaces &'s with &xE0000; and uses a character map to swap the private > character with an ampersand on output (using the use-character-maps on the > xsl:output element). > > This works fine in oXygen and even in the query console tests where I output > the result document to the output pane. > > The problem occurs when I retrieve the document from the database. The > private character &xE0000; is still in the result document I stored, and > hasn't been replaced with an ampersand. > > Does document-insert (or something) ignore the xsl:output directives in the > stylesheet? > > Am I running into some some query console behavior I'm not aware of (I'm > still rather new at using MarkLogic). > > Any pointers in the right direction will he much appreciated. > > Best, > Mark > > - -- --- ----- -------- ------------- > Mark Donoghue > IEEE > (732) 562-6045 > m.donog...@ieee.org > > IEEE - Advancing Technology for Humanity > > _______________________________________________ > General mailing list > General@developer.marklogic.com > Manage your subscription at: > http://developer.marklogic.com/mailman/listinfo/general > _______________________________________________ General mailing list General@developer.marklogic.com Manage your subscription at: http://developer.marklogic.com/mailman/listinfo/general
