Received: by nummer-3.proteosys id <01C19443.963855DC@nummer-3.proteosys>; Thu, 3 Jan 2002 11:44:14 +0100 In-Reply-To: <13335.9201072012@hilliard.ecs.soton.ac.uk> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C19443.963855DC" Return-Path: <@vm.gmd.de:LATEX-L@DHDURZ1.BITNET> X-MimeOLE: Produced By Microsoft Exchange V6.5 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]) Content-class: urn:content-classes:message Subject: Re: Re comments on 2alpha Date: Thu, 9 Jan 1992 13:53:15 +0100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "Sebastian Rahtz" Sender: "LaTeX-L Mailing list" To: "Rainer M. Schoepf" Reply-To: "LaTeX-L Mailing list" Status: R X-Status: X-Keywords: X-UID: 537 This is a multi-part message in MIME format. ------_=_NextPart_001_01C19443.963855DC Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Frank Mittelbach writes: > 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 > > you want a familiar syntax, how about having a default of 0, and = any > > other values put in [] before the string eg \verb|<6>[1]cmr10|? > > Why not? It could be interpreted as the optional argument to the > standard function for loading. It could then also be used as optional > argument to any loading function defined by the user. This needs more > thought but seems a possible way. What about more than one argument? is comma separation used elsewhere in LaTeX? yes, and there are tools for processing it, so yes please. <*scale>[0.9]ptimr would do me fine. > May I remark that this is not my mismatch but rather a compatibility > mismatch:-) But I'm happy to correct it next time. In my eyes the = best > solution would be to go for typographical sizes (Don gave the list, > > \verb|{14.4}|. Frank noted the problem in the latter case > > of the strings getting bigger, but more important is the fact = that > > the numbers then become unamenable to \TeX\ arithmetic, of the = type > > used in the function above. > > That's not true, only cumbersome. You could use \ifdim instead of > \ifnum that works fine. ugh! > of art one might to get information processed and in this case it > might be acceptable to use a nearby size if the real size is not > available on a particular installation. if i was in a high-production game, I'd either use a PS-type device which scaled, or have a computer-(rather than printer-) based font cache, or do substitution with the dvi driver. surely it muddies the waters to have *another* level of font substitution within TeX? if you aint got the font, dont ask for it in your style. sebastian ------_=_NextPart_001_01C19443.963855DC Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Re: Re comments on 2alpha

Frank Mittelbach writes:
 > 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

 > >   you want a familiar = syntax, how about having a default of 0, and any
 > >   other values put in [] = before the string eg \verb|<6>[1]cmr10|?
 >
 > Why not? It could be interpreted as the = optional argument to the
 > standard function for loading. It could = then also be used as optional
 > argument to any loading function defined = by the user. This needs more
 > thought but seems a possible way. What = about more than one argument?
is comma separation used elsewhere in LaTeX? yes, and = there are tools
for processing it, so yes please. = <*scale>[0.9]ptimr  would do me fine.

 > May I remark that this is not my mismatch = but rather a compatibility
 > mismatch:-) But I'm happy to correct it = next time. In my eyes the best
 > solution would be to go for typographical = sizes (Don gave the list,


 > >   \verb|{14.4}|.  Frank = noted the problem in the latter case
 > >   of the strings getting = bigger, but more important is the fact that
 > >   the numbers then become = unamenable to \TeX\ arithmetic, of the type
 > >   used in the function = above.
 >
 > That's not true, only cumbersome. You = could use \ifdim instead of
 > \ifnum that works fine.
ugh!

 > of art one might to get information = processed and in this case it
 > might be acceptable to use a nearby size = if the real size is not
 > available on a particular = installation.
if i was in a high-production game, I'd either use a = PS-type device
which scaled, or have a computer-(rather than = printer-) based font
cache, or do substitution with the dvi driver. surely = it muddies the
waters to have *another* level of font substitution = within TeX? if you
aint got the font, dont ask for it in your = style.

sebastian


------_=_NextPart_001_01C19443.963855DC--