Received: by nummer-3.proteosys id <01C19442.D6961D8C@nummer-3.proteosys>; Thu, 3 Jan 2002 11:38:53 +0100 MIME-Version: 1.0 x-vm-v5-data: ([nil nil nil nil nil nil nil t nil][nil nil nil nil nil nil nil nil nil nil nil nil nil nil nil nil]) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C19442.D6961D8C" X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message Subject: arithmetic for dimen and counters Date: Fri, 2 Nov 1990 18:02:14 +0100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "MITTELBACH FRANK" Sender: "LaTeX-L Mailing list" To: "Rainer M. Schoepf" Reply-To: "LaTeX-L Mailing list" Status: R X-Status: X-Keywords: X-UID: 260 This is a multi-part message in MIME format. ------_=_NextPart_001_01C19442.D6961D8C Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable During my discussions with Leslie we talked about a possible way to give the user and especially the style designer a possibility to express certain assignments to dimen skip and/or count registers in a general way using some sort of arithmetic notation. We both felt that this would be a great advantage to the user. My question is: do you have any suggestions how one can specifiy a syntax which is 1) general enough to handle all possible variations 2) is easy enough to parse by TeX 3) and is easy to handle for the user Suggestions are very welcome ... :-) Frank ------_=_NextPart_001_01C19442.D6961D8C Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable arithmetic for dimen and counters

During my discussions with Leslie we talked about = a
possible way to give the user and especially the = style designer
a possibility to express certain assignments to dimen = skip
and/or count registers in a general way using some = sort
of arithmetic notation. We both felt that this would = be a great
advantage to the user.

My question is: do you have any suggestions how one = can
specifiy a syntax which is

  1) general enough to handle all possible = variations
  2) is easy enough to parse by TeX
  3) and is easy to handle for the user

Suggestions are very welcome ... :-)

Frank

------_=_NextPart_001_01C19442.D6961D8C--