From: Marco <netuse@lavabit.com>
To: ntg-context@ntg.nl
Subject: Re: \nocap does not work
Date: Mon, 12 Apr 2010 21:23:02 +0200 [thread overview]
Message-ID: <20100412212302.19bd16f5@vorbis> (raw)
In-Reply-To: <4BC357C5.2080302@googlemail.com>
> With MkIV \cap and \nocap is no longer necessary when you have a
> opentype font
> with the smcp (smallcapitals) and c2sc (capitals to smallcapitals)
> features.
Thanks for your explanation. But why doesn't your example work with the
latin modern fonts? Don't they have these features? I'd be surprised
when they don't have small caps.
I'm against wikifying MKII stuff. Maybe I'll add a MKII-only note. When
I'm not completely mistaken I think its use should fade away in the near
future. So creating documentation for MKII is a waste of time.
Why are non-working commands like this not removed in MKIV? An undefined
control sequence is easier debuggable than weird behaviour in my opinion.
marco
___________________________________________________________________________________
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:[~2010-04-12 19:23 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-12 13:47 Marco
2010-04-12 17:26 ` Wolfgang Schuster
2010-04-12 19:00 ` Hans Hagen
2010-04-12 19:23 ` Marco [this message]
2010-04-12 19:43 ` Khaled Hosny
2010-04-12 21:41 ` Hans Hagen
2010-04-12 22:58 ` Khaled Hosny
2010-04-13 10:13 ` Hans Hagen
2010-04-13 10:48 ` Arthur Reutenauer
2010-04-13 11:18 ` Khaled Hosny
2010-04-13 11:49 ` Hans Hagen
2010-04-13 11:54 ` Arthur Reutenauer
2010-04-13 12:04 ` Hans Hagen
2010-04-13 11:03 ` Khaled Hosny
2010-04-13 11:06 ` Arthur Reutenauer
2010-04-13 17:19 ` Khaled Hosny
2010-04-13 17:37 ` Taco Hoekwater
2010-04-13 18:03 ` Khaled Hosny
2010-04-13 17:51 ` Arthur Reutenauer
2010-04-13 18:07 ` Khaled Hosny
2010-04-13 19:17 ` Arthur Reutenauer
2010-04-14 11:19 ` Khaled Hosny
2010-04-14 14:21 ` Hans Hagen
2010-04-14 15:16 ` Khaled Hosny
2010-04-14 15:38 ` Arthur Reutenauer
2010-04-13 12:00 ` Hans Hagen
2010-04-13 17:16 ` Khaled Hosny
2010-04-13 17:33 ` Thomas A. Schmitz
2010-04-13 18:00 ` Khaled Hosny
2010-04-12 23:21 ` Marco
2010-04-13 11:19 ` Wolfgang Schuster
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=20100412212302.19bd16f5@vorbis \
--to=netuse@lavabit.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).