LISTSERV mailing list manager LISTSERV 16.5

Help for TEI-L Archives


TEI-L Archives

TEI-L Archives


TEI-L@LISTSERV.BROWN.EDU


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

TEI-L Home

TEI-L Home

TEI-L  July 1995

TEI-L July 1995

Subject:

Re: RulesBuilder a nightmare?

From:

Peter Flynn <[log in to unmask]>

Reply-To:

Peter Flynn <[log in to unmask]>

Date:

Fri, 14 Jul 1995 09:19:38 CDT

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (212 lines)

> I accidentally erased the message, but in the last couple of
> days someone wrote an aside about the horrors of using Rules Builder
> with the TEI DTD(s).
 
That was probably me, but there weren't any horrors, just a few snags
getting it to swallow stuff the right way round. Now that I have found
out how to do it (thanks to some swift help from SQ), it's working fine.
I was critical of RB doing things this way, but SQ's support has been
excellent and has fixed the problem.
 
> Please tell me more.  I am about to embark on a medium-sized tagging
> project (a 45,000-word language corpus), and after getting lots of
> really slick adverts from the big names in the business (ArborText,
> Interleaf, etc) with Big Business-sized price tags, I had pretty
> much decided on getting an Author/Editor-Rules Builder bundle
> which carries a *substantial* academic discount. But now I'm not
> so certain. . .
 
No, as far as I can see A/E is quite capable of handling this. I don't know
how it performs on a file that large (if you really do have it all
as a single corpus file), as my experience of editing files >1Mb
has been limited to A/E on a very small old PC, which is not a valid
platform to compare it with modern machines. (In fact, A/E worked
fine, it was the slowness of the PC and lack of memory and disk space
which I had a problem with :-)
 
I got the DTD finished yesterday, and I promised to tell you all what
I had to do, so here goes:
 
a. I had tried to compile the DTD as it stands, using Rules Builder
   for MS-Windoze. It didn't like it, which was why I posted my original
   complaint. I'm not sure why SQ wrote it so that it won't accept
   a prolog in the same fashion as other SGML software, but they were
   quick to find me a solution once I had identified the problem.
 
b. Here's what the original prolog said:
 
   <!DOCTYPE TEI.2 SYSTEM "tei2.dtd"
   [
   <!-- Standard tagsets needed for TLH work -- >
   <!ENTITY % TEI.corpus.dtd         'INCLUDE'>
   <!ENTITY % TEI.prose              'INCLUDE'>
   <!--ENTITY % TEI.verse              'INCLUDE' can't be used with prose-->
   <!ENTITY % TEI.transcr            'INCLUDE'>
   <!ENTITY % TEI.textcrit           'INCLUDE'>
   <!ENTITY % TEI.names.dates        'INCLUDE'>
   <!-- Extra tagset needed to allow documentation of tags in header -->
   <!--ENTITY % TEI.tagsets.dtd system 'teitsd2.dtd'>
   %TEI.tagsets.dtd;-->
   <!-- Standard character entities -->
   <!ENTITY % ISOlat1 system         "ISOLat1"
        --"ISO 8879:1986//ENTITIES Added Latin 1//EN"-->
   %ISOlat1;
   <!ENTITY % ISOlat2 system         "ISOLat2"
        --"ISO 8879:1986//ENTITIES Added Latin 2//EN"-->
   %ISOlat2;
   <!-- Local mods to supplement ISO char ents and rename tags -->
   <!ENTITY % CURIA.entities system  'curia.ent'>
   %CURIA.entities;
   ]>
 
c. The file curia.ent contains extra char ents as well as some renaming
   of elements. The project is adding a lot of content-descriptive markup,
   so shortening the tagnames shortens file size and makes it more usable
   for people without graphical SGML editors. Here's the file:
 
   <!ENTITY fdot     SDATA "f" -- lenited f (dot-over)-->
   <!ENTITY Fdot     SDATA "F" -- lenited F (dot-over)-->
   <!ENTITY ndot     SDATA "n" -- nasalised n (dot-over)-->
   <!ENTITY mdot     SDATA "m" -- nasalised m (dot-over)-->
   <!ENTITY mmacr    SDATA "m" -- m with macron -->
   <!ENTITY Sdot     SDATA "S" -- lenited S (dot-over)-->
   <!ENTITY sdot     SDATA "s" -- lenited s (dot-over)-->
   <!ENTITY ampersir SDATA "&" -- insular ampersand-->
   <!ENTITY turnsemi SDATA ";" -- inverted semi-colon-->
   <!-- we need to add more of these, eg &longe; -->
 
   <!ENTITY % n.persName  'ps'>
   <!ENTITY % n.addName   'an'>
   <!ENTITY % n.genName   'gn'>
   <!ENTITY % n.forename  'fn' >
   <!ENTITY % n.surname   'sn' >
   <!ENTITY % n.nameLink  'nk' >
   <!ENTITY % n.placeName 'pn'>
   <!ENTITY % n.orgName   'on' >
   <!ENTITY % n.roleName  'rn'>
   <!ENTITY % n.expan     'ex' >
   <!ENTITY % n.foreign   'frn' >
   <!ENTITY % n.milestone 'mls' >
   <!ENTITY % n.supplied  'sup' >
   <!ENTITY % n.quote     'qt' >
   <!ENTITY % n.unclear   'uncl' >
 
   <!-- Bodge to get round bug in TEI DTD, courtesy of LB -->
   <!ENTITY % x.data '%n.persName | %n.placeName | %n.orgName |'>
 
d. This lot compiled happily with psgml-mode. I had simply snipped the
   prolog out of an instance and put it in a separate file and expected
   it to compile. But here's the way SQ said to do it:
 
   <!-- Standard tagsets needed for TLH work -- >
   <!ENTITY % TEI.corpus.dtd         'INCLUDE'>
   <!ENTITY % TEI.prose              'INCLUDE'>
   <!--ENTITY % TEI.verse              'INCLUDE' can't be used with prose-->
   <!ENTITY % TEI.transcr            'INCLUDE'>
   <!ENTITY % TEI.textcrit           'INCLUDE'>
   <!ENTITY % TEI.names.dates        'INCLUDE'>
   <!-- Extra tagset needed to allow documentation of tags in header -->
   <!--ENTITY % TEI.tagsets.dtd system 'teitsd2.dtd'>
   %TEI.tagsets.dtd;-->
   <!-- Standard character entities -->
   <!ENTITY % ISOlat1 system         "ISOLat1"
        --"ISO 8879:1986//ENTITIES Added Latin 1//EN"-->
   %ISOlat1;
   <!ENTITY % ISOlat2 system         "ISOLat2"
        --"ISO 8879:1986//ENTITIES Added Latin 2//EN"-->
   %ISOlat2;
   <!-- Local mods to supplement ISO char ents and rename tags -->
   <!ENTITY % CURIA.entities system  'curia.ent'>
   %CURIA.entities;
 
   <!ENTITY % TEI2.full.dtd "tei2.dtd">
   %TEI2.full.dtd;
 
e. These last two lines are what was supposed to do the trick, but
   RB still didn't like it, so I replaced the two lines with the entire
   contents of tei2.dtd and suddenly it seemed to work.
 
   Not quite: during compilation it claimed it couldn't find any of the
   parameter entity files referenced in the above, even though they were
   in the same directory as the DTD it was compiling, but fortunately it's
   smart enough to put up a dialog box so you can tell it (rather than
   dying like so much software does). This is fixed by editing the
   configuration file rb.ini and including a period and semicolon before
   the relevant search paths, so that it searches the current directory
   first, before trying elsewhere and failing.
 
   Incidentally that still doesn't fix the failure to find isolat1.ent
   and isolat2.ent...I've obviously missed something, and I'm sure it must
   be easy to fix.
 
f. At the end of compilation it complained fatally that I had some elements
   referenced but not declared. Now, this is the source of some contention.
   First, you have to be _very_ clear that we are talking about elements
   which your DTD _mentions_ ina  content model, but which are not declared
   because they come from modules which are not loaded in your version of
   the DTD (eg <camera>, because you might not be doing film stuff). We are
   _not_ talking about elements which are declared but simply not used
   anywhere: RB already handles these latter via a checkbox on the BUILD
   panel.
 
   Referencing elements which are not declared is actually permissible SGML
   (which surprised me when I first learned it) but it is quite kosher:
   it's just not handled by RB. In some people's view this is a bug. IMHO
   it's probably politer to call it by the latest buzzword, a USI (Unexpected
   System Inability :-)
 
   The simple way round it is to add declarations for all the `missing'
   elements, and set them either to EMPTY or ANY. This does have the
   disadvantage that they will then appear in the `allowed elements'
   menus when you do an `Insert Element' etc, but you can comment them using
   the tag file mechanism that RB provides, so that users know not to use
   them.
 
   RB doesn't do a log file which includes a list of the undeclared elements,
   so you have to copy them down from the error panel (which only mentions
   the first few), then add them to the DTD, re-compile, note down the next
   batch mentioned, add them, re-compile, and repeat until you have them
   all. Windoze doesn't let you clip text from error panels :-)
 
g. So here's what I ended up with, taking it from the bit about referencing
   the `master' tei2.dtd file which you recall I commented out:
 
   <!--ENTITY % TEI2.full.dtd "tei2.dtd">
   %TEI2.full.dtd;-->
 
   <!ENTITY % missing.bits  "lang|oref|ovar|pref|pvar|link|xptr|xref|caesura|
                             anchor|c|cl|m|phr|s|seg|w|att|gi|tag|val|formula|
                             camera|caption|move|sound|tech|view|castlist|
                             figure|table|textdesc|etree|graph|tree|
                             particdesc|settingdesc|alt|altgrp|certainty|
                             flib|fs|fslib|fvlib|interp|interpgrp|join|
                             joingrp|linkgrp|respons|span|spangrp|timeline|
                             epilogue|performance|prologue|set">
 
   <!ELEMENT (%missing.bits;) - o EMPTY>
 
   <!-- tei2.dtd:  written by OddDTD 1994-09-09                  -->
   <!-- 3.6.1: File tei2.dtd: Main document type declaration     -->
   <!-- file                                                     -->
 
   and then the rest of the DTD. Note the sequence is important:
 
   a. your module options first
   b. any private project additions
   c. any `missing' declarations
   d. then the `master' DTD
 
   It works just fine now I've got the knack. It sounds long-winded but
   it's not, really, just a little different from other systems I've used.
 
> (BTW, I am primarily an OS/2 user, and although I have several
> Windows-based products, MS-published software is generally not
> welcome here. So the inexpensive MS Word SGML editor add-ons are
> not an option.)
 
I don't know if SQ do an OS/2 version of A/E. I haven't had a chance to test
SGML Author for Word or WordPerfect SGML Edition with the TEI. Anyone done
this yet?
 
///Peter

Top of Message | Previous Page | Permalink

Advanced Options


Options

Log In

Log In

Get Password

Get Password


Search Archives

Search Archives


Subscribe or Unsubscribe

Subscribe or Unsubscribe


Archives

June 2019
May 2019
April 2019
March 2019
February 2019
January 2019
December 2018
November 2018
October 2018
September 2018
August 2018
July 2018
June 2018
May 2018
April 2018
March 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
December 2006
November 2006
October 2006
September 2006
August 2006
July 2006
June 2006
May 2006
April 2006
March 2006
February 2006
January 2006
December 2005
November 2005
October 2005
September 2005
August 2005
July 2005
June 2005
May 2005
April 2005
March 2005
February 2005
January 2005
December 2004
November 2004
October 2004
September 2004
August 2004
July 2004
June 2004
May 2004
April 2004
March 2004
February 2004
January 2004
December 2003
November 2003
October 2003
September 2003
August 2003
July 2003
June 2003
May 2003
April 2003
March 2003
February 2003
January 2003
December 2002
November 2002
October 2002
September 2002
August 2002
July 2002
June 2002
May 2002
April 2002
March 2002
February 2002
January 2002
December 2001
November 2001
October 2001
September 2001
August 2001
July 2001
June 2001
May 2001
April 2001
March 2001
February 2001
January 2001
December 2000
November 2000
October 2000
September 2000
August 2000
July 2000
June 2000
May 2000
April 2000
March 2000
February 2000
January 2000
December 1999
November 1999
October 1999
September 1999
August 1999
July 1999
June 1999
May 1999
April 1999
March 1999
February 1999
January 1999
December 1998
November 1998
October 1998
September 1998
August 1998
July 1998
June 1998
May 1998
April 1998
March 1998
February 1998
January 1998
December 1997
November 1997
October 1997
September 1997
August 1997
July 1997
June 1997
May 1997
April 1997
March 1997
February 1997
January 1997
December 1996
November 1996
October 1996
September 1996
August 1996
July 1996
June 1996
May 1996
April 1996
March 1996
February 1996
January 1996
December 1995
November 1995
October 1995
September 1995
August 1995
July 1995
June 1995
May 1995
April 1995
March 1995
February 1995
January 1995
December 1994
November 1994
October 1994
September 1994
August 1994
July 1994
June 1994
May 1994
April 1994
March 1994
February 1994
January 1994
December 1993
November 1993
October 1993
September 1993
August 1993
July 1993
June 1993
May 1993
April 1993
March 1993
February 1993
January 1993
December 1992
November 1992
October 1992
September 1992
August 1992
July 1992
June 1992
May 1992
April 1992
March 1992
February 1992
January 1992
December 1991
November 1991
October 1991
September 1991
August 1991
July 1991
June 1991
May 1991
April 1991
March 1991
February 1991
January 1991
December 1990
November 1990
October 1990
September 1990
August 1990
July 1990
June 1990
April 1990
March 1990
February 1990
January 1990

ATOM RSS1 RSS2



LISTSERV.BROWN.EDU

CataList Email List Search Powered by the LISTSERV Email List Manager