From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: odd end-of-line error w/ Minion Pro
Date: Fri, 11 Feb 2011 12:44:46 +0100 [thread overview]
Message-ID: <4D55212E.1000902@wxs.nl> (raw)
In-Reply-To: <211C2DB4-4383-4FB4-A431-C4854AC88F00@storytotell.org>
On 11-2-2011 9:26, Daniel Lyons wrote:
> Hi,
>
> I'm seeing a strange behavior with Minion Pro in OTF and the simplefont package. I'm not sure if it only happens with simplefont because I don't know how to set up a typescript. In any case, in breaking a line between roman and italic text, ConTeXt is losing a bit of space at the end of line. I thought it might be related to using hz or hanging alignment, or the quality option for protrusion and expansion, but it seems to happen even with these features disabled. Very unclear what could be causing this. Is it a known issue? What is this kind of bad behavior called?
>
> I've attached an image to which I've added a red line to show where the 'a' is leaving extra space before the newline.
hard to say without the input ... could be a spurious space
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
___________________________________________________________________________________
next prev parent reply other threads:[~2011-02-11 11:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-11 8:26 Daniel Lyons
2011-02-11 11:44 ` Hans Hagen [this message]
2011-02-11 11:49 ` Christian
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=4D55212E.1000902@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).