I guess an awful lot depends on how much your desired SGML output deviates from
the XML subset of SGML.
Are there things you need to produce that are outside the XML data model (e.g.
unnamed processing instructions)?
Or are all the differences at the serialization level?
If it's only a difference of serialization, then it should be easy enough to
write your own serializer or customize the Saxon serializer (so long as you
don't mind writing a bit of Java).
Michael Kay
Saxonica
On 23 Oct 2018, at 16:33, Rick Quatro rick(_at_)rickquatro(_dot_)com
<xsl-list-service(_at_)lists(_dot_)mulberrytech(_dot_)com> wrote:
Hi All,
I am at the preliminary stage of looking at a project. The input will be
authored in XML, but the output will be SGML. Is XSLT (version 2.0) a
reasonable language for doing this? Any pointers to examples, best practices,
etc., would be appreciated. Thank you very much.
Rick
Rick Quatro
Carmen Publishing Inc.
rick(_at_)frameexpert(_dot_)com <mailto:rick(_at_)frameexpert(_dot_)com>
585-729-6746 NEW!
XSL-List info and archive <http://www.mulberrytech.com/xsl/xsl-list>
EasyUnsubscribe <http://lists.mulberrytech.com/unsub/xsl-list/293509> (by
email <>)
--~----------------------------------------------------------------
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
--~--