🚀 go-pugleaf

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