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 f5OFVtf09525 for ; Sun, 24 Jun 2001 17:31:55 +0200 Received: by webgate.proteosys.de (8.11.4/8.11.0) with ESMTP id f5OFVoQ06456 . for ; Sun, 24 Jun 2001 17:31:50 +0200 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C0FCC2.CC6E2780" Received: from mail.Uni-Mainz.DE (mailserver1.zdv.Uni-Mainz.DE [134.93.8.30]) by mailgate1.zdv.Uni-Mainz.DE (8.11.0/8.10.2) with ESMTP id f5OFVlU27462 for ; Sun, 24 Jun 2001 17:31:47 +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 RAA08012 for ; Sun, 24 Jun 2001 17:31:46 +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 f5OFVkU27457 for ; Sun, 24 Jun 2001 17:31:46 +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 <1.A1149667@mail.listserv.gmd.de>; Sun, 24 Jun 2001 17:29:04 +0200 Received: from RELAY.URZ.UNI-HEIDELBERG.DE by RELAY.URZ.UNI-HEIDELBERG.DE (LISTSERV-TCP/IP release 1.8b) with spool id 498512 for LATEX-L@RELAY.URZ.UNI-HEIDELBERG.DE; Sun, 24 Jun 2001 17:31:42 +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 RAA05474 for ; Sun, 24 Jun 2001 17:31:41 +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 RAA69730 for ; Sun, 24 Jun 2001 17:31:42 +0200 Received: from csc.albany.edu (sarah.albany.edu [169.226.1.103]) by relay.uni-heidelberg.de (8.10.2+Sun/8.10.2) with ESMTP id f5OFVf324702 for ; Sun, 24 Jun 2001 17:31:42 +0200 (MET DST) Received: from fenris.math.albany.edu (fenris.math.albany.edu [169.226.23.39]) by csc.albany.edu (8.11.2/8.11.2) with ESMTP id f5OFV6908336 for ; Sun, 24 Jun 2001 11:31:07 -0400 (EDT) Received: (from mark@localhost) by fenris.math.albany.edu (8.11.2/8.11.2) id f5OFV6W05941 for LATEX-L@URZ.UNI-HEIDELBERG.DE; Sun, 24 Jun 2001 11:31:06 -0400 (EDT) Return-Path: X-Mailer: ELM [version 2.5 PL2] Content-class: urn:content-classes:message Subject: [Fwd: Proposal to Latex Development team] Date: Sun, 24 Jun 2001 16:31:06 +0100 Message-ID: <200106241531.f5OFV6W05941@fenris.math.albany.edu> X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "Mark Steinberger" 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: 4132 This is a multi-part message in MIME format. ------_=_NextPart_001_01C0FCC2.CC6E2780 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable -------- Original Message -------- Subject: Proposal to Latex Development team Date: Fri, 22 Jun 2001 16:43:19 -0500 From: "Lawrence S. Levy" Request to the Latex Development Team It would be very nice if someone who is more of a Tex-nologist than me could write a macro to solve the following conundrum involving \bar versus \overline. \bar is intended for individual letters, and \overline is intended for entire expressions. The trouble with \bar is that it does not adjust its size to the letter it occurs over, and is often too short. On the other hand, \overline is usually too long when it is used over a single letter. For example, putting it over a slanting math-italic Z gives a bar whose left-hand end is over the beginning of the bottom of the Z instead of the beginning of the top of the Z. Moreover, \overline-ing consecutive letters of the same height produces a single overline over all of the letters, instead of individual overlines over each of them, and it is necessary to insert thin spaces to resolve this. \overline works exactly as it should, when used over entire expressions. Thus what is needed is an improved \bar macro that adjusts its length to the letter it occurs over. If someone is inspired to write such a macro, please send a copy to me. I'm not the only one who would appreciate this. Lawrence Levy levy@math.wisc.edu ------_=_NextPart_001_01C0FCC2.CC6E2780 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable [Fwd: Proposal to Latex Development team]

-------- Original Message --------
Subject: Proposal to Latex Development team
Date: Fri, 22 Jun 2001 16:43:19 -0500
From: "Lawrence S. Levy" = <levy@math.wisc.edu>

Request to the Latex Development Team


It would be very nice if someone who is more of a = Tex-nologist than
me could write a macro to solve the following = conundrum involving
\bar versus \overline.

\bar is intended for individual letters, and \overline = is intended
for entire expressions. The trouble with \bar is that = it does not
adjust its size to the letter it occurs over, and is = often too short.

On the other hand, \overline is usually too long when = it is used over
a single letter. For example, putting it over a = slanting math-italic
Z gives a bar  whose left-hand end is over the = beginning of the
bottom of the Z instead of the beginning of the top = of the Z.

Moreover, \overline-ing consecutive letters of the = same height
produces a single overline over all of the letters, = instead of
individual overlines over each of them, and it is = necessary to insert
thin spaces to resolve this.

\overline works exactly as it should, when used over = entire expressions.

Thus what is needed is an improved \bar macro that = adjusts its length
to the letter it occurs over.


If someone is inspired to write such a macro, please = send a copy to
me. I'm not the only one who would appreciate = this.

Lawrence Levy
levy@math.wisc.edu

------_=_NextPart_001_01C0FCC2.CC6E2780--