<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<?xml-stylesheet type="text/css"
   href="/~hammond/gellmu/gellmuart.css"?>
<!DOCTYPE article
  PUBLIC "-//GNU GPL: William F. Hammond//DTD GELLMU XML 0.7.5U//EN"
  "http://www.albany.edu/~hammond/gellmu/xml/uxgellmu.dtd" [
<!ENTITY TableOfContentsFile SYSTEM "gents.xcn">
<!ENTITY % ComputedEntitiesFile SYSTEM "gents.xet">
%ComputedEntitiesFile;
]>
<article stem="gents"
><preamble
><surtitle
>The GELLMU Archive</surtitle><title
>The Use of SGML Entities in GELLMU</title><author
>William F. Hammond</author><date
>21 July 2000</date></preamble><body
><Section depth="1" seq = "1" sid="1"
><sunit>&SecRef-1;</sunit
><shead
><label lseq="1">SU-1</label
>Introduction</shead><parb
><abbr
>GELLMU</abbr> now has provision for the incorporation of an
internal declaration subset with either <abbr
>SGML</abbr> or direct <abbr
>XML</abbr>
output from the syntactic translator <softw
>gellmu.el</softw><eos
/>  (The didatic
<emph
>article</emph> document type is first written as <abbr
>SGML</abbr> and then
re<hyp
/>formatted with some normalization, including <quophrase
>argument
naming</quophrase>, as <abbr
>XML</abbr>.)</parb><parb
>SGML entities do not correspond in any obvious way to classical
LaTeX markup<eos
/>  However, as things unfold, it is expected that
use of SGML entities may accommodate <emph
>some</emph> <latex
/><hyp
/>like
macro functionality<eos
/></parb><parb
>As things stand with the didactic document type, all entity expansion
takes place when the SGML created by <softw
>gellmu.el</softw> is first
parsed<eos
/></parb><parb
>With an appropriate <abbr
>SGML</abbr> document type defintion, one might
provide for an <quophrase
>internal</quophrase> command in the article preamble
that spawns an internal declaration subset in the <abbr
>XML</abbr> image<eos
/>
For direct production of <abbr
>XML</abbr> this is not an issue<eos
/></parb><parb
>These two ways of handling entities could be used in the same
document<eos
/>
</parb></Section
><Section depth="1" seq = "2" sid="2"
><sunit>&SecRef-2;</sunit
><shead
><label lseq="2">SU-2</label
>A Few Simple Examples</shead><parb
>The quoted phrase at the end of this sentence is produced with entity
markup under the name <emph
>foo</emph>: <quophrase
>a <ltc
/>sample<gtc
/> string</quophrase><eos
/>  The GELLMU source
used for this phrase is <qquostr
><amp
/>foo</qquostr><eos
/></parb><parb
>The <abbr
>GELLMU</abbr> source for the definition of the entity <emph
>foo</emph>
is <display
><verb
><bsl
/>entity{foo "a <amp
/>oltc;sample<amp
/>ogtc; string"}</verb><spc
/><eos
/></display> Note that <emph
>sample</emph> is not
markup<eos
/>  The expansion of this definition uses another entity
<emph
>fooglm</emph><eos
/>  The entity <emph
>oltc</emph> is defined in the source with
<display
><verb
><bsl
/>entity<lbr
/>oltc STARTTAG "ltc"<rbr
/></verb><spc
/><eos
/></display>
It invokes at parse<hyp
/>time the starttag for the empty element <emph
>ltc</emph>
in the didactic <abbr
>GELLMU</abbr> document type that gives rise in most
formattings to the character <quochar
><ltc
/></quochar><eos
/>  Note that this layer of
indirection is only required for an <abbr
>SGML</abbr> (or <abbr
>XML</abbr>) document
that is going to be subjected to a formatting pipeline that involves
at least one target language under <abbr
>SGML</abbr> or <abbr
>XML</abbr> where
an instance of the character <quochar
><ltc
/></quochar> might not be intended as markup<eos
/></parb><parb
>The <abbr
>GELLMU</abbr> source for the definition of <emph
>foo</emph> translates
under <softw
>gellmu.el</softw> to SGML as <display
><verb
><ltc
/>!ENTITY foo "a <amp
/>oltc;sample<amp
/>ogtc; string"<gtc
/></verb><spc
/><eos
/></display> The
display of this translation is marked up with still another entity
<emph
>foosgml</emph><eos
/>
</parb></Section
></body
></article>

