Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!zaphod.mps.ohio-state.edu!rpi!uupsi!sunic!nuug!ulrik!ulrik!blarsen
From: blarsen@spider.uio.no (Bjorn Larsen)
Newsgroups: comp.text.sgml
Subject: Re: Is there a DTD standard?
Message-ID: <BLARSEN.90Sep12090821@spider.uio.no>
Date: 12 Sep 90 07:08:21 GMT
References: <141829@sun.Eng.Sun.COM> >
	<EMV.90Sep6191207@urania.math.lsa.umich.edu> <8027@mcshh.hanse.de>
	<1990Sep11.163347.7593@zorch.SF-Bay.ORG>
	<1990Sep11.193327.19935@terminator.cc.umich.edu>
	<1990Sep12.020242.2916@cs.rochester.edu>
	<BZS.90Sep11225016@world.
Sender: news@ulrik.uio.no (USENET News System)
Reply-To: Bjorn.Larsen@usit.uio.no
Organization: University of Oslo, Norway
Lines: 30
In-Reply-To: bzs@world.std.com's message of 12 Sep 90 02:50:16 GMT


In article <BZS.90Sep11225016@world.std.com> bzs@world.std.com (Barry Shein) writes:
> 
> 	Are we happy with the convention &char-name to encode non-ascii
> 	characters (e.g. &oumlaut), how far along is the Text Encoding
> 	Initiative with this? Can we use their conventions yet?
> 

No, of course we're not! I wite Norwegian using SGML, and of course
it Will Not Do for me to have to scatter &Oslash, &oslash, &Aring,
&aring, &AElig and &aelig specifications all around my text.

I want to be able to use ISO Latin 1. At the moment, the text I write
end up inside The Publisher, and my approach is the following:

1. Write the text using ISO Latin 1. (or, occationally, write the
   text on my Mac, and then translate it to ISO Latin 1. Argh.)
2. Translate ISO Latin 1 to SGML-type codes.
3. Import the resulting SGML into The Publisher.

Of course, a small perl script makes it easy to automate this,
but I really got irritated about a year back when it dawned on me
that I was expected to write my name as "Bj&oslash rn" in SGML-ese.

Anyways, what is the 'Text Encoding Initiative', and what are their
'conventions'?

--
Bjorn Larsen                University of Oslo,  Norway
                               Bjorn.Larsen@usit.uio.no