From: Hans Hagen <pragma@wxs.nl>
To: Mojca Miklavec <mojca.miklavec.lists@gmail.com>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: handling fonts with missing math
Date: Sat, 01 Oct 2011 10:56:43 +0200 [thread overview]
Message-ID: <4E86D5CB.402@wxs.nl> (raw)
In-Reply-To: <CALBOmsZfYpDzQ9rdT2nA=Tq+MQUxLYmEyHp1q_LoyM_S2+BP+Q@mail.gmail.com>
On 30-9-2011 23:39, Mojca Miklavec wrote:
> On Tue, Sep 27, 2011 at 19:57, Hans Hagen<pragma@wxs.nl> wrote:
>> On 27-9-2011 19:52, Mojca Miklavec wrote:
>>>
>>> On Tue, Sep 27, 2011 at 19:44, Hans Hagen wrote:
>>>>
>>>> there is some fall back mechanism that does that but as soon as one
>>>> defined
>>>> his/her own typescript that can interfere
>>>
>>> How should we define trypescripts to avoid interference then?
>>
>> A typeface definition normally has a matching monospace and math definition
>> (so: ss + tt + mm or rm + tt + mm or in some cases rm + ss + tt + mm). Of
>> course some relative scaling has to be considered then.
>
> Do you want to say that we need an explicit definition of LM Math?
>
> Just curious: how much information is missing/how much would would it
> be if we would want to create a virtual math font by combining LM +
> populating italic/bold/bold italic latin and greek math alphabets from
> text font? Would that look horrible because of lack of information
> about glyph metrics?
that is relatively easy: just make a lfg file that contains the
specification (and choose some math font that suits)
my guess is that it will look bad in most cases
we might consider making a sort of generic partial math font (maybe even
needs to be designed) that sort of fills in the usual bits and pieces
(root signs, arrows etc) in a way that matches an average font
(we probably need a few weights then)
of course that would only work for not too fancy math
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
| www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
prev parent reply other threads:[~2011-10-01 8:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-26 6:46 handling fonts with missing math (was: math signs in itemize) Mojca Miklavec
2011-09-27 17:44 ` Hans Hagen
2011-09-27 17:52 ` Mojca Miklavec
2011-09-27 17:57 ` handling fonts with missing math Hans Hagen
2011-09-28 8:58 ` R. Ermers
2011-09-28 9:14 ` luigi scarso
2011-09-28 11:14 ` R. Ermers
2011-09-28 11:21 ` luigi scarso
2011-09-30 21:39 ` Mojca Miklavec
2011-10-01 8:56 ` Hans Hagen [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4E86D5CB.402@wxs.nl \
--to=pragma@wxs.nl \
--cc=mojca.miklavec.lists@gmail.com \
--cc=ntg-context@ntg.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).