ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Mojca Miklavec <mojca.miklavec.lists@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Bold small caps
Date: Fri, 23 May 2014 18:46:16 +0200	[thread overview]
Message-ID: <CALBOmsYDHYho95_WXzyfOJDCtG83O13_ZQG274kvEOAzdTY+4Q@mail.gmail.com> (raw)
In-Reply-To: <0B2917FD-A806-402B-8251-746C61BA6DD6@gmail.com>

On Fri, May 23, 2014 at 6:11 PM, Wolfgang Schuster wrote:
> Am 23.05.2014 um 17:55 schrieb Mojca Miklavec:
>
>> Would it make sense to fix this for the default LM setup as well?
>
> This need to be done by the font designers because Latin Modern
> uses a separate font for the small capitals and the \setff (better use
> \feature) has no effect in this case.

For some reason I thought that they did both (supported all the small
cap glyphs as well as released a separate font).

But now I remembered that LM doesn't have bold small caps at all.

But apart from fixing the font: would creating some kind of a "virtual
font" with small cap glyphs taken from the other small cap font(s)
(where they exist) be feasible/doable? From what I see there are four
small caps fonts: regular and italic for both the roman and typewriter
style. No bold and no sans.

Mojca
___________________________________________________________________________________
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
___________________________________________________________________________________


  reply	other threads:[~2014-05-23 16:46 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 [this message]
2014-05-23 16:52     ` Hans Hagen
2014-05-23 16:49 ` Hans Hagen
  -- 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=CALBOmsYDHYho95_WXzyfOJDCtG83O13_ZQG274kvEOAzdTY+4Q@mail.gmail.com \
    --to=mojca.miklavec.lists@gmail.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).