From: Taco Hoekwater <taco@elvenkind.com>
Subject: Re: extra space after variant
Date: Fri, 02 Dec 2005 21:13:56 +0100 [thread overview]
Message-ID: <4390AB04.1000403@elvenkind.com> (raw)
In-Reply-To: <43909F12.2000709@comp.lancs.ac.uk>
Adam Lindsay wrote:
> Taco Hoekwater wrote:
>
>> I can't get the example to compile. Whatever I do, context insists
>> on creating SerifRegular.tfm through mktextfm (sigh). I'm too lazy
>> to figure out what is going on right now, so can someone create a
>> full minimal example, please? I'd like to check this with all
>> tracing on, because it hints are a problem deeper down somewhere.
>
>
> I hope you're caught up with your fonts. Variants aren't defined with
> many, but they are here:
Ok, got it. At first, I completely misunderstood the problem (but now I
understand). I believe removing the space is better than forcing ugly
input, in this case.
I generally dislike auto-removed spaces, but since that happens often
anyway (esp after ]'s), it will not be a big surprise to anybody.
Cheers,
Taco
next prev parent reply other threads:[~2005-12-02 20:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-01 14:04 Hans van der Meer
2005-12-02 13:57 ` Hans Hagen
2005-12-02 18:35 ` Taco Hoekwater
2005-12-02 19:22 ` Adam Lindsay
2005-12-02 20:13 ` Taco Hoekwater [this message]
2005-12-04 21:03 ` Hans Hagen
2005-12-05 12:36 ` Adam Lindsay
2005-12-02 18:48 ` Adam Lindsay
2005-12-04 21:05 ` 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=4390AB04.1000403@elvenkind.com \
--to=taco@elvenkind.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).