ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
To: ntg-context@ntg.nl
Subject: Re: bug in \definefontfamily?
Date: Mon, 20 Mar 2017 13:59:17 +0100	[thread overview]
Message-ID: <1c65daf8-715c-6f0c-47e6-5e00625e93d8@wxs.nl> (raw)
In-Reply-To: <6bb00b67-4c9d-0a85-1779-29f287de3255@gmx.es>

On 3/19/2017 10:08 PM, Pablo Rodriguez wrote:
> On 03/19/2017 09:58 PM, Wolfgang Schuster wrote:
>>> Pablo Rodriguez 19. März 2017 schrieb:
>>> But [features={none, quality}] disables everything and I canot enable
>>> protrusion plus expansion only.
>>>
>>> At least, it doesn’t work with \definefontfamily. I haven’t tested this
>>> with \setupfontfamily.
>>
>> \definefontfamily[mainface][mono][Latin Modern Mono Prop][features=quality]
>
> Yes, this might work, but I’m afraid I need to disable other default
> features such as ligatures (not only liga, but TeX ligatures).
>
> I had this problem typesetting XML sources and I didn’t know how to
> disable the other features.
>
> My main interest in having mono with quality are standard paragraphs
> with Roman text. Expansion and protrusion enable better line breaking.

not true

expansion can make excessive spacing less excessive
protrusion is an esthetic feature

esp protrusion also adds constraints (i.e. one cannot selectively 
protrude a hyphen in one line and not in the next one for instance) so 
the solutionspace doesn't become much better

(fwiw, personally i never use expansion but occasionally i use protrusion)

> And if mono doesn’t get protrusion, you may find wrong optical margins
> (protrusion), because the lack of it only on the mono face.
>
> Many thanks for your help,
>
> Pablo
>


-- 

-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
        tel: 038 477 53 69 | www.pragma-ade.nl | 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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : http://contextgarden.net
___________________________________________________________________________________

  parent reply	other threads:[~2017-03-20 12:59 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-18 22:05 OT salt feature not working? Pablo Rodriguez
2017-03-19 10:11 ` Pablo Rodriguez
     [not found]   ` <58ce6920.42ba1c0a.ea8e8.7871@mx.google.com>
2017-03-19 12:38     ` bug in \definefontfamily? (was: Re: OT salt feature not working?) Pablo Rodriguez
2017-03-19 19:38       ` bug in \definefontfamily? Wolfgang Schuster
2017-03-19 20:07         ` Pablo Rodriguez
2017-03-19 20:32           ` Wolfgang Schuster
2017-03-19 20:40             ` Pablo Rodriguez
2017-03-19 20:46               ` Wolfgang Schuster
2017-03-19 20:58               ` Wolfgang Schuster
2017-03-19 21:08                 ` Pablo Rodriguez
2017-03-19 21:22                   ` Wolfgang Schuster
2017-03-20 12:59                   ` Hans Hagen [this message]
2017-03-20 12:55       ` Hans Hagen

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=1c65daf8-715c-6f0c-47e6-5e00625e93d8@wxs.nl \
    --to=pragma@wxs.nl \
    --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).