From: Taco Hoekwater <taco@elvenkind.com>
Subject: Re: problems with bold small caps
Date: Tue, 13 Dec 2005 11:14:41 +0100 [thread overview]
Message-ID: <439E9F11.4070706@elvenkind.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0512121842140.3610@gaston.free.fr>
Peter Münster wrote:
> On Mon, 12 Dec 2005, Taco Hoekwater wrote:
>
> \starttext
> {\sc Normal and \bf bold Small-Caps. Accents: àÉßöÜ}
> \stoptext
Hi Peter,
> And here are my problems:
>
> 1.) I get bold sc font, but the normal \sc is now the normal font.
\sc and \bf are defined at the same level in ConTeXt, so they (normally)
exclude each other. My guess is that it is very unlikely that this will
be fixed, but I assume it would be possible to do something using the
\variants mechanism (note: I am not sure and would not know how)
> 2.) Accented characters are not correct.
My guess is that maybe the regime also switches the font encoding?
The ecXXXX fonts definately only exist in EC encoding.
Cheers, Taco
next prev parent reply other threads:[~2005-12-13 10:14 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-05 19:22 bold \tt and pdf-output Peter Münster
2005-12-06 8:18 ` Hans Hagen
2005-12-06 9:19 ` Taco Hoekwater
2005-12-06 17:30 ` Peter Münster
2005-12-06 19:35 ` Hans Hagen
2005-12-10 11:32 ` Peter Münster
2005-12-12 9:34 ` Taco Hoekwater
2005-12-12 11:34 ` Vit Zyka
2005-12-12 17:48 ` problems with bold small caps (was: Re: bold \tt and pdf-output) Peter Münster
2005-12-13 10:14 ` Taco Hoekwater [this message]
2005-12-13 10:57 ` problems with bold small caps Taco Hoekwater
2005-12-13 12:24 ` Adam Lindsay
2005-12-13 11:01 ` Hans Hagen
2005-12-13 11:46 ` Vit Zyka
2005-12-12 10:52 ` bold \tt and pdf-output Hans Hagen
-- strict thread matches above, loose matches on Subject: below --
2005-12-05 19:19 problems with bold small caps 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=439E9F11.4070706@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).