ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
Cc: ntg-context@ntg.nl
Subject: Re: kap: real?
Date: Fri, 30 Oct 1998 17:00:03 +0100	[thread overview]
Message-ID: <3639E283.CFFCF267@wxs.nl> (raw)

Frans Goddijn wrote:

>  HH> Well, in a decent small caps font, the uppercase are just the
>  HH> normal uppercase and the lowercase become smaller uppercase. So, if
>  HH> you got a strange character, your font is wrong.
> 
> Are you sure? I am convinced that in the expert set that I bought, there
> are small caps, which I get when I use \sc and there are just these small
> caps in the expert set with oldstyle numbers too, but no "lower case" and
> "upper case" small caps.

Hm. 

>  HH> \unexpanded\def\mykap#1{{\sc\lowercase{#1}}}
> 
> That's slightly longer than Taco's example so I guess it's more deluxe?
> What does the \unexpanded do here?

It makes tests possible, like in \doifelse{whatever \myka{...}
...}{Frans} ....
For the moment, forget about it. E-tex (taco-tex) us supposed to solve
this -).

Hans

-----------------------------------------------------------------
                                          Hans Hagen | PRAGMA ADE
              Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
    tel: 038 477 53 69 | fax: 038 477 53 74 | mail: pragma@wxs.nl
-----------------------------------------------------------------


             reply	other threads:[~1998-10-30 16:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-10-30 16:00 Hans Hagen [this message]
  -- strict thread matches above, loose matches on Subject: below --
1998-10-30 13:59 Frans Goddijn
1998-10-30  8:15 Taco Hoekwater
1998-10-30  7:59 Hans Hagen
1998-10-29 15:40 Frans Goddijn
1998-10-29 13:52 Hans Hagen
1998-10-29 13:15 Frans Goddijn

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=3639E283.CFFCF267@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).