ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Bold small caps
Date: Fri, 23 May 2014 18:49:32 +0200	[thread overview]
Message-ID: <537F7C1C.9030005@wxs.nl> (raw)
In-Reply-To: <CALBOmsYLqJ7vs+fqnDFt_n6_JH+PkmF5ia0sNFQKQEqy0cjK1w@mail.gmail.com>

On 5/23/2014 5:55 PM, Mojca Miklavec wrote:
> Hi,
>
> I always forget how to use bold or italic small caps (I keep mixing
> addff/setff and smcp/+smcp/smallcaps etc.). In ideal world it could be
> nice if simply
>      {\sc Normal and \bf Bold Small Caps} or
>      {\bf\sc Bold Small Caps}
> would work out-of-the-box.
>
> The first hit on the wiki was
>      http://wiki.contextgarden.net/Bold_small_caps
> which contained just the MKII example. I added a MKIV example
>      {\setff{smallcaps} Normal and \bf bold Small Caps.}
> but the problem is that this example only works with <put any font
> name here> except for the default Latin Modern setup.
>
> Would it make sense to fix this for the default LM setup as well?

I don't know .. I'd rather see lm shipped with the smallcaps in the 
regular font instead of separate.

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
___________________________________________________________________________________


  parent reply	other threads:[~2014-05-23 16:49 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-23 15:55 Mojca Miklavec
2014-05-23 16:11 ` Wolfgang Schuster
2014-05-23 16:46   ` Mojca Miklavec
2014-05-23 16:52     ` Hans Hagen
2014-05-23 16:49 ` Hans Hagen [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-04-03  7:07 bold " Peter Münster via ntg-context
2023-04-03  9:34 ` Hans Hagen via ntg-context
2023-04-03 21:33 ` Pablo Rodriguez via ntg-context
2013-06-25 12:59 Bold Small Caps Malte Stien
2013-06-25 13:08 ` Wolfgang Schuster
2013-06-25 13:34   ` Malte Stien
2013-06-25 17:39     ` Sietse Brouwer
2010-12-11 22:40 bold small caps Peter Münster
2010-12-11 22:57 ` Florian Wobbe
2010-12-11 23:12   ` Peter Münster
2010-12-12  8:30     ` Wolfgang Schuster
2010-12-12 15:22       ` Marco
2010-12-12 16:07         ` Wolfgang Schuster
2010-12-12 19:39           ` Peter Münster
2010-12-15 11:43             ` Hans Hagen
2010-12-13 10:38           ` Marco
2004-01-09 21:33 Peter Münster

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=537F7C1C.9030005@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).