Re: pages in texts
by "Frank Boumphrey" <bckman(at)ix.netcom.com>
|
| Date: |
Sat, 4 Mar 2000 01:28:59 -0500 |
| To: |
"Murray Altheim" <altheim(at)eng.sun.com> |
| Cc: |
<hwg-gutenberg(at)hwg.org>, <hwg-gutenberg-dtds(at)hwg.org> |
| References: |
prioritynetworks |
| |
todo: View
Thread,
Original
|
|
Yes,
I agree they are mix models. They also contain a lot of meta markup
"|txterr|mkuperr" and "pagenum" can be considered meta data.
I'm afraid that the current DTD's are very flawed in many ways, and
hopefully we will be able to adress these flaws when we move on to making an
'official' dtd.
However the current DTD's are at least allowing us to mark up documents!
Frank
----- Original Message -----
From: Murray Altheim <altheim(at)eng.sun.com>
To: Frank Boumphrey <bckman(at)ix.netcom.com>
Cc: <hwg-gutenberg-dtds(at)hwg.org>; <hwg-gutenberg(at)hwg.org>
Sent: Friday, March 03, 2000 2:25 AM
Subject: Re: pages in texts
> Frank Boumphrey wrote:
> >
> > I am struggeling with the etext of the scarlet letter. The problem is
that
> > the Etext retains the original page numbering.
> >
> > As others have pointed out the 'page' element in the bookfrag.dtd is not
up
> > to the task. What we need is a 'pagenum' element that can not only
appear
> > between paragraphs, but also in paragraphs.
> >
> > IOW we need to modify the general entities as follows
> >
> > <!ENTITY % inline.class
> >
"|quote|emph|ital|reference|date|place|name|graphic|txterr|mkuperr|misc|page
> > num ">
> >
> > <!ENTITY % block.class
> >
"|letter|blockquote|footnote|note|list|deflist|table|blockgraphic|pagenum">
>
> I'd also recommend reading over the section in Eve Maler's book on
> naming conventions and considering using both *.class and *.mix, as both
> of the above lists seem more like mixes to me. This will greatly assist
> when trying to subclass these to create more concise semantics within
> content models.
>
> If you break down HTML to its core element classes, you'll find block,
> inline and what has been called 'misc'. The latter includes <ins>, <del>
> and other element types whose presence is not connected to formatting
> or structure, and which may occur pretty much anywhere. You'll note
> that originally, <ins> and <del> were inclusions on <body>. An alternative
> to misc.class or misc.mix would be to put various elements in their own
> classes, and aggregate them in mixes.
>
> I hope this is helpful.
>
> Murray
>
>
...........................................................................
> Murray Altheim
<mailto:altheim@eng.sun.com>
> XML Technology Center
> Sun Microsystems, Inc., MS MPK17-102, 1601 Willow Rd., Menlo Park, CA
94025
>
> the honey bee is sad and cross and wicked as a weasel
> and when she perches on you boss she leaves a little measle -- archy
HWG: hwg-gutenberg mailing list archives,
maintained by Webmasters @ IWA