Received: by nummer-3.proteosys id <01C19443.929113FC@nummer-3.proteosys>; Thu, 3 Jan 2002 11:44:08 +0100 In-Reply-To: CA_ROWLEY%VAX.ACS.OPEN.AC.UK@vm.gmd.de's message of Sun, 5 Jan 92 21:58:59 GMT <9201060943.AA03003@ufer.ZIB-Berlin.DE> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C19443.929113FC" 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]) x-to: LATEX-L%DHDURZ1.BITNET@vm.gmd.de Content-class: urn:content-classes:message Subject: scaling of math fonts Date: Tue, 7 Jan 1992 20:10:08 +0100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: From: "Rainer Schoepf" Sender: "LaTeX-L Mailing list" To: "Rainer M. Schoepf" Reply-To: "LaTeX-L Mailing list" Status: R X-Status: X-Keywords: X-UID: 504 This is a multi-part message in MIME format. ------_=_NextPart_001_01C19443.929113FC Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Since I'm "not responsible" I'll throw in what I have... Here are the types of input required to set-up the tables: something of this form would replace the present collection of \define@mathsizes commands. 1. Constants: \mathsizes@table{% <*5-5.5>{5}{5}{5}% <*5.5-6.5>{6}{5}{5}% <*6.5-7.5>{7}{6}{5}% <*7.5-8.5>{8}{6}{5}% <*8.5-9.5>{9}{7}{5}% <*9.5-10.5>{10}{8}{6}% <*10.5-11.5>{11}{9}{7}% <*11.5-12.5>{12}{10}{8}% ) [Semantics (eg): <*7.5-8.5>{8}{6}{5}% means that for text-size in the range 7.5pt to 8.5pt, math-size is 8pt scriptsize is 6pt scriptscriptsize is 5pt ] OK, but what happens at exactly 5.5? I assume that the first of the entries is selected. OK so far, but what if you want to specify {5}{5}{5} for everything strictly smaller than 5.5, and {6}{5}{5} for >=3D5.5 ? Just asking, it's not clear to me whether this is really a problem...probably not. 2. This one also contains more general linear functions (defined by their end-point values): Same comment here. ----------- The first time a text-size is called in a document, the result of consulting tables such as the above is stored in the same way as all math-sizes are stored at present; so that the next time that same = size is called, the math-sizes are immediately available---no need to analyse the set-up table again. ... Note that this means that the math-sizes table in use should not be changed within a document. Yes, but I pointed out before that the relation between \fontsize, and the corresponding three mathsizes may change when fonts are changed. Example: imagine switching from cm-type fonts to ccr or grotesque-type or whatever. It may then be that the math sizes have to be calculated anew, in other words, what has been stored before has to be deleted. I think it is crucial to allow such a change. I *don't* think it has to be as efficient as the rest of the font change mechanism. Finally, something that was only briefly mentioned in our pensees du jardin: some dimen parameters should change with the size, e.g. the height of \bigggggggggggggg delimiters, or \jot. The idea was to record this in the mathsizes table, e.g. \mathsizes@table{% <*5-5.5>{5}{5}{5}{\jot:*1.5-1.8}% <*5.5-6.5>{*I}{5}{5}{\jot:*1.8-2}% <*6.5-7.5>{*I}{*5-5.5}{5}{\jot:2-2.3}% .. da capo at nausea } Open questions: 1. Is this a good idea? 2. If so, which syntax is apropriate? Food for thought, folks! Rainer ------_=_NextPart_001_01C19443.929113FC Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable scaling of math fonts

Since I'm "not responsible" I'll throw in = what I have...


   Here are the types of input required to = set-up the tables:
   something of this form would replace the = present collection of
   \define@mathsizes commands.

   1. Constants:

   \mathsizes@table{%
   <*5-5.5>{5}{5}{5}%
   <*5.5-6.5>{6}{5}{5}%
   <*6.5-7.5>{7}{6}{5}%
   <*7.5-8.5>{8}{6}{5}%
   <*8.5-9.5>{9}{7}{5}%
   <*9.5-10.5>{10}{8}{6}%
   <*10.5-11.5>{11}{9}{7}%
   <*11.5-12.5>{12}{10}{8}%
   )

   [Semantics (eg):

   <*7.5-8.5>{8}{6}{5}%   = means that for text-size in the range
     7.5pt to 8.5pt,

     math-size is 8pt
     scriptsize is 6pt
     scriptscriptsize is 5pt = ]

OK, but what happens at exactly 5.5? I assume that the = first of the
entries is selected. OK so far, but what if you want = to specify
{5}{5}{5} for everything strictly smaller than 5.5, = and {6}{5}{5} for
>=3D5.5 ? Just asking, it's not clear to me = whether this is really a
problem...probably not.

   2. This one also contains more general = linear functions
   (defined by their end-point = values):

Same comment here.

   -----------

   The first time a text-size is called in a = document, the result of
   consulting tables such as the above is = stored in the same way as all
   math-sizes are stored at present; so = that the next time that same size
   is called, the math-sizes are = immediately available---no need to
   analyse the set-up table again.

   ...

   Note that this means that the math-sizes = table in use should not be
   changed within a document.

Yes, but I pointed out before that the relation = between \fontsize, and
the corresponding three mathsizes may change when = fonts are changed.
Example: imagine switching from cm-type fonts to ccr = or grotesque-type
or whatever. It may then be that the math sizes have = to be calculated
anew, in other words, what has been stored before has = to be deleted.

I think it is crucial to allow such a change. I = *don't* think it has
to be as efficient as the rest of the font change = mechanism.

Finally, something that was only briefly mentioned in = our pensees du
jardin: some dimen parameters should change with the = size, e.g. the
height of \bigggggggggggggg delimiters, or \jot. The = idea was to
record this in the mathsizes table, e.g.

\mathsizes@table{%
<*5-5.5>{5}{5}{5}{\jot:*1.5-1.8}%
<*5.5-6.5>{*I}{5}{5}{\jot:*1.8-2}%
<*6.5-7.5>{*I}{*5-5.5}{5}{\jot:2-2.3}%
.. da capo at nausea
}


Open questions:

1. Is this a good idea?
2. If so, which syntax is apropriate?


Food for thought, folks!

Rainer






------_=_NextPart_001_01C19443.929113FC--