ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: User 19087 <se.user19087@gmail.com>
To: Wolfgang Schuster <wolfgang.schuster.lists@gmail.com>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Scaling down symbols and emojis
Date: Sat, 19 Jan 2019 12:50:16 -0500	[thread overview]
Message-ID: <CANJfosFt_=0VMFcdVyNoM+TQO=-puCJhPD=esPU5D-0Dk79KXA@mail.gmail.com> (raw)
In-Reply-To: <1fcc24d8-22e6-2ce9-553a-a9c5bde38f81@gmail.com>

As far as I can tell (by experimentation), bodyfont environment
features resolve in this order:
* matching size in the current file
* default environment in the current file
* matching size in 'font-pre.mkiv'
* default environment in 'font-pre.mkiv'
* default to 1.0 otherwise
This applies to individual features such as 'a' and 'b' and not entire
blocks. For example, if the [12pt] block provides 'a' but not 'b'
while the [default] block provides 'a' and 'b', then both blocks will
be used: 'a' from [12pt] and 'b' from [default].

With one exception: the 'x' and 'xx' sizes cannot be modified by the
current file:

    \setupbodyfont[12pt]
    \setupbodyfontenvironment [default] [x=2.0,xx=2.0]
    \starttext
      m{\tfx m}{\tfxx m}
    \stoptext

Furthermore there seems to be some extraneous output when the
bodyfontenvironment matches the current bodyfont size. For example,
the following outputs: "m12.0ptm12.0ptm"

    \setupbodyfontenvironment [12pt] [m=2.0,n=2.0,]
    \starttext
      m{\tfm m}{\tfn m}
    \stoptext

On Sat, Jan 19, 2019 at 3:59 AM Wolfgang Schuster
<wolfgang.schuster.lists@gmail.com> wrote:
> Why do you need this when you can just change the style of commands
> with use \tfx (e.g. \high or \low) to use the \tfm size?

With that out of the way, I don't know how to change commands which
use '\tfx' to use '\tfm' instead. Unless you mean this (though
technically they still use '\tfx', it just matches '\tfm'):

    \setupbodyfontenvironment [default] [m=0.8,n=0.6,x=0.8,xx=0.6]

Even if that did work, which it doesn't (see above), it would be
preferable to use the default bodyfont environment shipped by ConTeXt.
It probably exists for good reasons: matching the most common optical
font sizes, for aesthetics, and for consistency. I don't want the 'x'
and 'xx' sizes to vary between standard ConTeXt documents, and
documents which need to provide the 'n' and 'm' sizes.

It's also more work, as mentioned further up the thread. It may not be
strictly necessary to specify 'x' and 'xx' for each new size-specific
bodyfont environment, as they'll be inherited from [default]. But for
consistency each bodyfont size should have 'x' and 'xx' sizes matching
those from ConTeXt, and these vary with bodyfont size. That means
looking them up in 'font-pre.mkiv', a little math, and remembering to
do it every time you switch sizes. And that's ignoring the fact that
'\definebodyfont' can also override these sizes. I think using a macro
is simpler.
___________________________________________________________________________________
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : http://contextgarden.net
___________________________________________________________________________________

      reply	other threads:[~2019-01-19 17:50 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-16 20:56 User 19087
2019-01-16 21:24 ` Wolfgang Schuster
2019-01-16 23:29   ` User 19087
2019-01-17 12:39   ` User 19087
2019-01-17 13:30   ` User 19087
2019-01-18 11:47     ` Wolfgang Schuster
2019-01-18 21:44       ` User 19087
2019-01-19  8:42         ` User 19087
2019-01-19  8:59           ` Wolfgang Schuster
2019-01-19 17:50             ` User 19087 [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='CANJfosFt_=0VMFcdVyNoM+TQO=-puCJhPD=esPU5D-0Dk79KXA@mail.gmail.com' \
    --to=se.user19087@gmail.com \
    --cc=ntg-context@ntg.nl \
    --cc=wolfgang.schuster.lists@gmail.com \
    /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).