Received: from webgate.proteosys.de (mail.proteosys-ag.com [62.225.9.49]) by lucy.proteosys (8.11.0/8.9.3/SuSE Linux 8.9.3-0.1) with ESMTP id f5ONBEf11183 for ; Mon, 25 Jun 2001 01:11:14 +0200 Received: by webgate.proteosys.de (8.11.4/8.11.0) with ESMTP id f5ONBDQ08613 . for ; Mon, 25 Jun 2001 01:11:13 +0200 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C0FD02.F6DFD500" Received: from mail.Uni-Mainz.DE (mailserver1.zdv.Uni-Mainz.DE [134.93.8.30]) by mailgate2.zdv.Uni-Mainz.DE (8.11.0/8.10.2) with ESMTP id f5ONBA027273 for ; Mon, 25 Jun 2001 01:11:10 +0200 (MET DST) Received: from mailgate1.zdv.Uni-Mainz.DE (mailgate1.zdv.Uni-Mainz.DE [134.93.8.56]) by mail.Uni-Mainz.DE (8.9.3/8.9.3) with ESMTP id BAA07528 for ; Mon, 25 Jun 2001 01:11:09 +0200 (MEST) X-MimeOLE: Produced By Microsoft Exchange V6.5 Received: from mail.listserv.gmd.de (mail.listserv.gmd.de [192.88.97.5]) by mailgate1.zdv.Uni-Mainz.DE (8.11.0/8.10.2) with ESMTP id f5ONB9U15984 for ; Mon, 25 Jun 2001 01:11:09 +0200 (MET DST) Received: from mail.listserv.gmd.de (192.88.97.5) by mail.listserv.gmd.de (LSMTP for OpenVMS v1.1a) with SMTP id <0.CDC992B1@mail.listserv.gmd.de>; Mon, 25 Jun 2001 1:08:27 +0200 Received: from RELAY.URZ.UNI-HEIDELBERG.DE by RELAY.URZ.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 1.8b) with spool id 497724 for LATEX-L@RELAY.URZ.UNI-HEIDELBERG.DE; Mon, 25 Jun 2001 01:11:06 +0200 Received: from ix.urz.uni-heidelberg.de (mail.urz.uni-heidelberg.de [129.206.119.234]) by relay.urz.uni-heidelberg.de (8.8.8/8.8.8) with ESMTP id BAA11718 for ; Mon, 25 Jun 2001 01:11:05 +0200 (MET DST) Received: from relay.uni-heidelberg.de (relay.uni-heidelberg.de [129.206.100.212]) by ix.urz.uni-heidelberg.de (8.8.8/8.8.8) with ESMTP id BAA57598 for ; Mon, 25 Jun 2001 01:11:05 +0200 Received: from ams.org (sun06.ams.org [130.44.1.6]) by relay.uni-heidelberg.de (8.10.2+Sun/8.10.2) with ESMTP id f5ONB4305507 for ; Mon, 25 Jun 2001 01:11:05 +0200 (MET DST) Received: from localhost (bnb@localhost) by ams.org (8.11.2/8.11.2) with ESMTP id f5OMlkg00689; Sun, 24 Jun 2001 18:47:47 -0400 (EDT) In-Reply-To: <20010624.094814.98349906.wl@gnu.org> Return-Path: X-Scanned-By: MIMEDefang 1.0 (http://www.roaringpenguin.com/mimedefang/) Content-class: urn:content-classes:message Subject: Re: Justin Ziegler's YAASP math encoding Date: Sun, 24 Jun 2001 23:47:46 +0100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "Barbara Beeton" Sender: "Mailing list for the LaTeX3 project" To: "Multiple recipients of list LATEX-L" Reply-To: "Mailing list for the LaTeX3 project" Status: R X-Status: X-Keywords: X-UID: 4137 This is a multi-part message in MIME format. ------_=_NextPart_001_01C0FD02.F6DFD500 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable werner lemberg asks, Is there any plan to adapt Justin Ziegler's math encoding proposal = as documented in l3d007.tex as `official'? What are the results of the TUG Technical Working Group on a math encoding? the working group hasn't done anything as a group for several years. however, various individuals post new material from time to time. i have been working on a project (stix) that has some bearing on math fonts, namely - working with the unicode technical committee to add a quite large number of math symbols to unicode and iso 10646. - participating in the review of new fonts being created for use both in print and on the web, which will be freely available under license; these will contain all the newly encoded symbols, and will be made in both type 1 and truetype formats. for some background information on the stix project, see http://www.ams.org/STIX (unfortunately, it's not up to date; documentation always seems to come last ...) for a draft of unicode 3.2, which contains most of the newly coded symbols, see http://www.unicode.org/charts/draftunicode32/ regarding justin's proposal, various problems have begun to loom large when considering that the stix fonts are to be used both in print and on the web. they are intended for use with browsers and other software that can't cope with the way tex fonts are constructed. for example, positions 0-32, and some others, must not be used, meaning that the full 256 positions cannot be filled. not all the organizations participating in the stix project use tex, so the fonts meet their needs as well as those of (la)tex. i have every intention of encouraging the use of justin's work as a basis for arranging the new fonts, insofar as possible given the limitations. i've taken a look at the working group page, and found some glitches. i'll try to get those fixed soon, in particular the pointer to the unicode material. werner continues, I'm working on encguide.tex and a German translation of it, and I = try to fill the gaps which still are in the document... that's a worthy endeavour. please do provide a pointer when it's ready for comments. -- bb ------_=_NextPart_001_01C0FD02.F6DFD500 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Re: Justin Ziegler's YAASP math encoding

werner lemberg asks,

    Is there any plan to adapt Justin = Ziegler's math encoding proposal as
    documented in l3d007.tex as = `official'?  What are the results of the
    TUG Technical Working Group on a = math encoding?

the working group hasn't done anything as a group for = several years.
however, various individuals post new material from = time to time.

i have been working on a project (stix) that has some = bearing on math
fonts, namely
 - working with the unicode technical committee = to add a quite large
   number of math symbols to unicode and = iso 10646.
 - participating in the review of new fonts = being created for use
   both in print and on the web, which will = be freely available
   under license; these will contain all = the newly encoded symbols,
   and will be made in both type 1 and = truetype formats.

for some background information on the stix project, = see
    http://www.ams.org/STIX
(unfortunately, it's not up to date; documentation = always seems to
come last ...)

for a draft of unicode 3.2, which contains most of the = newly coded
symbols, see
    http://www.unicode= .org/charts/draftunicode32/

regarding justin's proposal, various problems have = begun to loom
large when considering that the stix fonts are to be = used both in
print and on the web.  they are intended for use = with browsers and
other software that can't cope with the way tex fonts = are constructed.
for example, positions 0-32, and some others, must = not be used,
meaning that the full 256 positions cannot be = filled.  not all the
organizations participating in the stix project use = tex, so the
fonts meet their needs as well as those of = (la)tex.  i have every
intention of encouraging the use of justin's work as = a basis for
arranging the new fonts, insofar as possible given = the limitations.

i've taken a look at the working group page, and found = some glitches.
i'll try to get those fixed soon, in particular the = pointer to the
unicode material.

werner continues,

    I'm working on encguide.tex and a = German translation of it, and I try
    to fill the gaps which still are = in the document...

that's a worthy endeavour.  please do provide a = pointer when it's
ready for comments.
          &nbs= p;            = ;            =             &= nbsp;        -- bb

------_=_NextPart_001_01C0FD02.F6DFD500--