Re: Form feed character () in decoded xs:base64B

With xsl:output version="1.1", the form feed is not a problem - Saxon
writes the decoded xs:base64Binary string without any replacements.

However I'm getting weird parsing errors downstream in my RDF toolkit
(which works fine with XML 1.0). I'll try to see what the problem is.

On Mon, Jul 13, 2020 at 8:00 PM Imsieke, Gerrit, le-tex
gerrit.imsieke@xxxxxxxxx <xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx>
wrote:
>
> What happens if you use version="1.1" in the XML declaration (of the
> stylesheet)?
>
> On 13.07.2020 19:54, Martynas JuseviD
ius martynas@xxxxxxxxxxxxx wrote:
> > Hi,
> >
> > I'm transforming large JSON files with some email data using XSLT 3.0.
> > They contain xs:base64Binary literals which I'm decoding using
> > bin:decode-string() and want to include the decoded values in the
> > output XML.
> >
> > The problem is that some of the decoded string values have illegal XML
> > 1.0 characters in them, such as Form feed (&#xc;).
> >
> > I want to remove them but cannot find a way.
> > I can't use translate(., '&#xc;', '') because the stylesheet would not
> > be well-formed anymore.
> > I can't even use replace(., codepoints-to-string(12), '') because I
> > get this error (with Saxon 10.1 EE):
> >
> >      codepoints-to-string(): invalid XML character [xc]. Found while
> > atomizing the second argument of fn:replace()
> >
> > Are there any native XSLT options here?
> >
> > Thanks.