From: "Jonathan F. Dill" <jfdill@jfdill.suite.net>
To: Mark Galassi <rosalia@lanl.gov>
Cc: docbook-tools <docbook-tools-discuss@sourceware.cygnus.com>
Subject: Re: tei-lite DTD?
Date: Wed, 27 Dec 2000 06:36:00 -0000 [thread overview]
Message-ID: <38C74835.A746EED8@jfdill.suite.net> (raw)
In-Reply-To: <877lfc4yt8.fsf@portacipria.lanl.gov>
Mark Galassi wrote:
>
> Jonathan> Hi everybody, Is there anyone out there using the TEI
> Jonathan> tei-lite DTD? I'm trying to make it work with all of
> Jonathan> the bits and pieces that I already have from
> Jonathan> docbook-tools. Perhaps instead I should ask on the TEI
> Jonathan> mailing list if anyone is using docbook-tools.
>
> :-) Maybe. I would suggest that for now you use "jade" (from our
> distribution) with its own flags to point to your DTD and stylesheets.
OK Thanks for thinking about it. I tried using the system from
tei-dsl.961210.tar.gz which should be self-contained as it includes the
ISO entities it needs, dsssl.dtd, fot.dtd, catalog etc. using the TEI
User's Manual teiu5.sgm as a test case. The stylesheets appear to be
originally writen by Richard Light, possibly last touched by Jon Bosak,
but the whole TEI project is "in transition." I found some messages in
list archives on Mulberry tech along the lines, "Yes, I had this problem
with TEI-lite" but no mention of a solution. I downloaded another copy
of the stylesheet and DTD from the Oxford site and had no better luck
with that. I think there may be some case-sensitive type problems in
the stylesheet which appears to have come originally from a
case-insensitive OS like Windows9X.
Most of the TEI SGML stuff appears to have been collecting dust since
about 1996-1997, and meanwhile, there is a flurry of activity around the
TEI XML DTD.
Is there a method for generating a document instance from XML source
that is analogous to using jade to generate a document instance from
SGML source? I guess I'll give jade a try and see if it can handle xml.
In particular, I need tools that compile and run on Linux.
I suppose next I'll see what I can find out from the DSSSL list on
Mulberry tech.
I have no problems writing valid markup. I have no problems grasping
how wonderful is the promise of SGML/XML. It seems to me about 99% of
the pages I find on the web about SGML and XML are either explaining how
to mark things up correctly, or talking about how wonderful SGML and XML
are, and maybe a scant 1% actually deals with the very practical details
of getting a document instance, and what to do if you have a problem.
% jade -c catalog -d tei-dem.dsl -t rtf -o teiu5.rtf teiu5.sgm
jade:tei-dem.dsl:6:33:E: document type does not allow element
"STYLE-SPECIFICATION" here; assuming missing "STYLE-SHEET" start-tag
jade:tei-dem.dsl:8:0:E: character data is not allowed here
jade:tei-dem.dsl:26:53:E: document type does not allow element
"EXTERNAL-SPECIFICATION" here
jade:tei-dem.dsl:26:55:E: "STYLE-SPECIFICATION" not finished but
document ended
jade:tei-dem.dsl:26:55:E: end tag for "STYLE-SPECIFICATION" omitted, but
OMITTAG NO was specified
jade:tei-dem.dsl:6:0: start tag was here
jade:tei-dem.dsl:26:55:E: end tag for "STYLE-SHEET" omitted, but OMITTAG
NO was specified
jade:tei-dem.dsl:6:0: start tag was here
jade:E: specification document does not have the DSSSL architecture as a
base architecture
I put in the missing tags in tei-dem.dsl, which is the customization
stylesheet which invokes tei-lite.dsl, but I was still left with:
jade:E: specification document does not have the DSSSL architecture as a
base architecture
and an RTF document that consists of all of the words run together in
huge paragraphs without any real formatting.
> I agree that DocBook would not do well for that, and it would violate
> the spirit of SGML.
>
> I think tha the DocBook tools project should consider this issue (of
> DTDs for non-technical use) because it would be nice for people to use
> the same tools and types of scripts for DocBook and for
> poetry/fiction/whatever
>
> Does anyone (Norm?) know much about these more "casual" DTDs?
--
"Jonathan F. Dill" (jfdill@jfdill.suite.net)
prev parent reply other threads:[~2000-12-27 6:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-27 6:36 Jonathan F. Dill
2000-12-27 6:36 ` Mark Galassi
2000-12-27 6:36 ` Jonathan F. Dill [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=38C74835.A746EED8@jfdill.suite.net \
--to=jfdill@jfdill.suite.net \
--cc=docbook-tools-discuss@sourceware.cygnus.com \
--cc=rosalia@lanl.gov \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).