topic How to import a set of text entities into a DocBook document? in Arbortext

How to import a set of text entities into a DocBook document?

sfogel — Fri, 22 Mar 2013 06:30:58 GMT

Hi, all...We have a large collection of potential text entities that we'd like to be able to import into any DocBook document with Arbortext. For example, for cross references to the many books in our library, we have 5-letter book IDs. If the writer uses an entity for the book

How to import a set of text entities into a DocBook document?

peter.li — Fri, 22 Mar 2013 07:41:38 GMT

Hey Steve,

I'm sure this could be done with a customisation, where are you based?

Pete

Peter Li

How to import a set of text entities into a DocBook document?

AndyEsslinger — Fri, 22 Mar 2013 11:34:50 GMT

Since you mention text entities, I assume that you are using the SGML version of docbook. If I understand what you want, you can implement a text entity library as a private declaration. Just put the entity declaration in the DOCTYPE as shown in red. Use the 5-letter book IDs. You might have to adjust the SGML capacities in the SGML declaration file if there are too many books. I did something similar and had to break the list of entities into three separate files :

%library;
]>
<book>
* * *
</book>

Contents of library file declared above:

How to import a set of text entities into a DocBook document?

LynnHales — Fri, 22 Mar 2013 12:43:38 GMT

Andy's solution will work if you're using SGML or an XML DTD. If you are
using a schema, you're "supposed" to be able to include a DOCTYPE in the
schema and declare the entities there.

If you are using an XML DTD you may get capacity error when Epic parses the
file, but it will not cause you any problems. The Army's 40051 DTD has
several large text entity files it calls and Epic routinely gives a LITLEN
warning, but still will process the information.

Lynn

How to import a set of text entities into a DocBook document?

ptc-953926 — Fri, 22 Mar 2013 15:05:01 GMT

Our entire system, which is XML Schema 1.0, uses text entities. Every one of our documents has a definition similar to this:

%textents;
]>

The authors have no control over the "text.ent" file, which is stored completely apart from the XML content. This setup works just fine with XML Schema.

Dave

How to import a set of text entities into a DocBook document?

ptc-953960 — Fri, 22 Mar 2013 18:06:47 GMT

How about maintaining your definition a magnificent, yest modest, Oracle
Database and having the XSL connect thereto using, perhaps, Saxon's SQL
extension?

How to import a set of text entities into a DocBook document?

sfogel — Fri, 22 Mar 2013 22:27:08 GMT

Hi, Andy.

Yup, that did it. Very grateful.

Steve

HYPERLINK " \nOracle
Steve Fogel | Information Architect, Oracle Database | 650.506.4914
Oracle Server Technologies Information Development
500 Oracle Parkway | M/S 4op1126 | Redwood Shores, CA 94065

EXTERNAL: How to import a set of text entities into a DocBook document?

ebenton — Mon, 25 Mar 2013 11:21:14 GMT

FYI -
I remember several years ago when we were using an SGML doctype with many text entities, that when we would try to compile the doctype for any change, Adept Editor would complain that we had exceeded the string capacity of Adept Editor. We had to reduce the number of text entities down to a quantity that would allow Adept Editor to compile the doctype without exceeding string capacity. This was not a capacity that was adjustable via an SGML setting in the declarations file. This was a hard-coded limit in Adept Editor's core code.

Today, this limit may not exist or is so high that it doesn't matter. Of course, if you are not using SGML you should be OK since doctype compilation is not an issue.