Received: by nummer-3.proteosys id <01C19443.97C5AABC@nummer-3.proteosys>; Thu, 3 Jan 2002 11:44:17 +0100 Return-Path: <@vm.gmd.de:LATEX-L@DHDURZ1.BITNET> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C19443.97C5AABC" x-vm-v5-data: ([nil nil nil nil nil nil nil nil nil][nil nil nil nil nil nil nil nil nil nil nil nil nil nil nil nil]) X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message Subject: Function and ranges Date: Thu, 9 Jan 1992 23:18:51 +0100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "Frank Mittelbach" Sender: "LaTeX-L Mailing list" To: "Rainer M. Schoepf" Reply-To: "LaTeX-L Mailing list" Status: R X-Status: X-Keywords: X-UID: 548 This is a multi-part message in MIME format. ------_=_NextPart_001_01C19443.97C5AABC Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subj: Functions and ranges: Sebastian pointed out the problem that in 2\alpha it is always single size, range, or function. As an alternative I suggested to allow a combination of range and function. > > it would better (as Sebastian already said) to allow function and > > range in the <..> and making the empty function the standard = scaling > > function. Question is function followed by range or range followed = by > > function, the latter seems to be more logical to me, e.g. = <10-cmxiipt> > not sure i understand. dont i want a function for the range 10-12? ie > <10-12>[*cmxiipt]cmr > or whatever I now like to make this more concrete: I suggest to allow the simple-size as well as the size-range to include a function after the decimals specifying the size, i.e.: \begin{bnf} & | . | , \\ & | \end{bnf} \begin{bnf} & "-" "-" | "-" | "-" \\ & "*" | "*" \end{bnf} Remarks: 1) the * is actually not necessary but may make scanning easier. = Perhaps not. 2) the for the we can but we need not to introduce a = separator. 3) the old could be handled as an unrestricted range with function (e.g. `<-scale>' so it isn't necessary. But maybe we want = it? I talked already about an extended concept of the formerly stuff called allowing a comma separated parameter list. Are there additional comments then the one from Sebastian, that he wants it? cheers Frank ------_=_NextPart_001_01C19443.97C5AABC Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Function and ranges

Subj: Functions and ranges:

Sebastian pointed out the problem that in 2\alpha it = is always single
size, range, or function.  As an alternative I = suggested to allow a
combination of range and function.

>  > it would better (as Sebastian already = said) to allow function and
>  > range in the <..> and making = the empty function the standard scaling
>  > function. Question is function = followed by range or range followed by
>  > function, the latter seems to be more = logical to me, e.g. <10-cmxiipt>
> not sure i understand. dont i want a function = for the range 10-12? ie
>  <10-12>[*cmxiipt]cmr
> or whatever

I now like to make this more concrete: I suggest to = allow the
simple-size as well as the size-range to include a = function after the
decimals specifying the size, i.e.:

\begin{bnf}
  <size-spec>   = &   <unsigned-integer> |
          &nbs= p;         = <unsigned-integer>.<unsigned-integer> |
          &nbs= p;         = <unsigned-integer>,<unsigned-integer>    =   \\

  <simple-size> & <size-spec> | = <size-spec> <function-name>
\end{bnf}

\begin{bnf}
  <size-range-spec>    = &   <size-spec> "-" = <simple-size>
          &nbs= p;            = ;    <empty> "-" <simple-size> = |
          &nbs= p;            = ;    <size-spec> "-" <empty> = |
          &nbs= p;            = ;    <empty> "-" = <empty>          =        \\
  <size-range>  & "*" = <size-range-spec> |
          &nbs= p;       "*" = <size-range-spec>  <function-name>
\end{bnf}

Remarks:

 1) the * is actually not necessary but may make = scanning easier. Perhaps not.
 2) the for the <function-name> we can but = we need not to introduce a separator.
 3) the old <size-function> could be = handled as an unrestricted range
with function (e.g. `<-scale>' so it isn't = necessary. But maybe we want it?

I talked already about an extended concept of the = formerly stuff
called <map-type> allowing a comma separated = parameter list. Are there
additional comments then the one from Sebastian, that = he wants it?


cheers

Frank

------_=_NextPart_001_01C19443.97C5AABC--