Received: by nummer-3.proteosys id <01C19443.971C0974@nummer-3.proteosys>; Thu, 3 Jan 2002 11:44:16 +0100 Return-Path: <@vm.gmd.de:LATEX-L@DHDURZ1.BITNET> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C19443.971C0974" 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: RE: scaling of math fonts Date: Thu, 9 Jan 1992 13:18:30 +0100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: From: Sender: "LaTeX-L Mailing list" To: "Rainer M. Schoepf" Reply-To: "LaTeX-L Mailing list" Status: R X-Status: X-Keywords: X-UID: 533 This is a multi-part message in MIME format. ------_=_NextPart_001_01C19443.971C0974 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Rainer writes: > > OK, but what happens at exactly 5.5? I assume that the first of the > entries is selected. Mais d'accord: it may even say this somewhere in the "pens'ees". > 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. I am not excluding the posibilty of "simple entries" such as <5.5>{6}{5}{5}% also being in the table, or any other method of doing such things--- definitely not a problem. > 2. This one also contains more general linear functions > (defined by their end-point values): > > Same comment here. Same answer! > ----------- > > 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. > You did indeed---I was asked to give simple examples, so I deliberately left out this possibilty and carefully pointed out the consequence: ie that table changing is not possible (well, not quite, I can think of methods of doing both, but they are not very elegant or efficient). > 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. maybe not. > 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 > } I think that it is probably necessary to provide a \everymathversionchange hook as well. > Open questions: > > 1. Is this a good idea? Important. > 2. If so, which syntax is apropriate? Dont get too hung up on detailed syntax: views are welcome, but since it is possible that the whole lot will get re-coded for ltx3, there may be unknown (at present) efficiency/coding-constraint issues which affect choice of syntax. > Food for thought, folks! Indeed: I hope i can here those brains ticking and fingers tapping "real soon". chris ------_=_NextPart_001_01C19443.971C0974 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable RE: scaling of math fonts

Rainer writes:

>
> OK, but what happens at exactly 5.5? I assume = that the first of the
> entries is selected.
Mais d'accord: it may even say this somewhere in the = "pens'ees".

> 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.
I am not excluding the posibilty of "simple = entries" such as

   <5.5>{6}{5}{5}%

also being in the table, or any other method of doing = such things---
definitely not a problem.

>    2. This one also contains more = general linear functions
>    (defined by their end-point = values):
>
> Same comment here.
Same answer!

>    -----------
>
>    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.
>
You did indeed---I was asked to give simple examples, = so I
deliberately left out this possibilty and carefully = pointed out the
consequence: ie that table changing is not possible = (well, not quite,
I can think of methods of doing both, but they are = not very elegant or
efficient).

> 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.
maybe not.

> 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
> }

I think that it is probably necessary to provide = a
\everymathversionchange hook as well.


> Open questions:
>
> 1. Is this a good idea?
Important.

> 2. If so, which syntax is apropriate?
Dont get too hung up on detailed syntax: views are = welcome, but since
it is possible that the whole lot will get re-coded = for ltx3,
there may be unknown (at present) = efficiency/coding-constraint issues
which affect choice of syntax.

> Food for thought, folks!
Indeed: I hope i can here those brains ticking and = fingers tapping
"real soon".


chris



------_=_NextPart_001_01C19443.971C0974--