W3C home > Mailing lists > Public > xproc-dev@w3.org > May 2010

xsl:result-document and character maps

From: Alex Muir <alex.g.muir@gmail.com>
Date: Thu, 27 May 2010 11:02:15 +0000
Message-ID: <AANLkTimoY6JSI1ozUFKJAQsBCr_zYFWp6nnpTdmmbay7@mail.gmail.com>
To: XProc Dev <xproc-dev@w3.org>

So I thought I had a good idea to get character maps working in my xproc
pipeline by using a  xsl:result-document within an xslt file thinking it
would bypass the xproc pipeline output thus allowing the character maps in
my xslt to work.

I then found in the spec it says "The use-character-maps parameter in [
specification has not been provided in the standard serialization options
provided by this specification." so that explains why it does not work.

I found that the result-document in not saved when running with the pipeline
even if the href is hard-coded with a file name that outputs correctly when
running in oxygen.  I then read in the xproc archive that suggested the
output from a result document appears in a secondary port.

Q: Can someone show me how to access a result-document using a secondary
port that and what if you have multiple xsl result-documents?

Q: Would having an option that allows an xslt file to save result documents
directly and thus not on a port be a bad idea? I assume this would give
character maps a chance to work and might be desired generally as a feature.

Let me know your thoughts.


An informal recording with one mic under a tree leads to some pretty sweet
acoustic sounds.
Received on Thursday, 27 May 2010 11:02:48 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:03:07 UTC