🚀 go-pugleaf

Hi Alex,

* For the NAMELEN problem, you can fix it by setting up a structured application for importing your SGML and specifying your own SGML declaration which sets NAMELEN to some larger value. In the DocBook SGML Structured Application that comes with FrameMaker, NAMELEN is set to 239, which is the maximum, so you could reference that declaration in your structured applications definition or make your own SGML declaration and use that. FrameMaker uses a default SGML declaration if you don't specify one; I believe that the default value is 8, as specified in the reference concrete syntax (from memory, could be wrong), so if you have any NAMEs longer than 8 characters, FrameMaker will complain.

* For the DTD path, you could edit the SGML file to point to the location of the DTD on your system, and you can also specify the location of the DTD in your application definition.

* As for the errors when opening the DTD, it's hard to say based on your description.

* For your question on how the SGML was correct in Epic but causes errors in FrameMaker, the thing with SGML is that it's a amazingly configurable standard: you can change loads of things, and so the defaults are only helpful in circumstances where the supplier of the document didn't do anything too "whacky". So it may well be that the document is correct when viewed in Epic.


Jon