Yes it is a reasonable approach and should be fairly easy (depending on
what your SGML output.  If the data structures are the same converting you
may only be required to add a DOCTYPE statement and make empty elements
SGML compliant (i.e., <br/> to <br></br>.

If you have to build a document declaration subset (for graphic entities)
you can build this with XSLT and include it as a pipeline step.  If you
don't need to build a document declaration subset should be able to use
XSLT for the whole process.

Betty

/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/
Betty Harvey                        | Phone:  410-787-9200  FAX: 9830
Electronic Commerce Connection, Inc. |
harvey@xxxxxxxxxx                    | Washington,DC XML Users Grp
URL:  http://www.eccnet.com  <http://www.eccnet.com>         |
http://www.eccnet.com/xmlug
/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\\/\/
 Member of XML Guild (www.xmlguild.org)


On Tue, Oct 23, 2018 at 11:33 AM Rick Quatro rick@xxxxxxxxxxxxxx <
xsl-list-service@xxxxxxxxxxxxxxxxxxxxxx> 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@xxxxxxxxxxxxxxx
>
> 585-729-6746 NEW!
>
>
>
>
>
>
>
>
> XSL-List info and archive <http://www.mulberrytech.com/xsl/xsl-list>
> EasyUnsubscribe <http://lists.mulberrytech.com/unsub/xsl-list/480526> (by
> email <>)