ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Adam Lindsay" <atl@comp.lancs.ac.uk>
Subject: Re: notes on TeXLive and Truetype fonts
Date: Wed, 9 Apr 2003 23:44:40 +0100	[thread overview]
Message-ID: <20030409224440.9129@news.comp.lancs.ac.uk> (raw)
In-Reply-To: <20030410001009.00131b24.morawski@gmx.net>

Jens-Uwe Morawski said this at Thu, 10 Apr 2003 00:10:09 +0200:

>The problem is, for example, how can one declare a bold-italic small-caps
>font in ConTeXT. AFAIK i can define
>\definefontsynonym[SerifBoldItalicCaps][AFont-BoldItalicCaps]
>
>but there seems no standard way to access it (\bfitsc or {\bf{\it{\sc...}}})
>ConTeXt lacks a complete standard set of font attributes and how they
>have to be used. LaTeX has them defined, thus it is easier to create
>FDs than typescript. Even how to name typescript-files is nowhere defined.

I was dealing with the problem of a bold italic smallcaps font this
weekend, and I was running into some sort of limits within ConTeXt in
terms of the number of \tfa \tfb \sc font strategies (is that the right
term?) that I could define without running out of room.

I suspect it's *possible* to have a complete set of font attributes, but
there are some architectural and practical limits at the moment.

Anyone who can comment further?

adam
-- 
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
 Adam T. Lindsay                      atl@comp.lancs.ac.uk
 Computing Dept, Lancaster University   +44(0)1524/594.537
 Lancaster, LA1 4YR, UK             Fax:+44(0)1524/593.608
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

  reply	other threads:[~2003-04-09 22:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-09 19:57 Bill McClain
2003-04-09 20:09 ` Bruce D'Arcus
2003-04-09 20:36   ` Bill McClain
2003-04-09 21:04     ` Bruce D'Arcus
2003-04-09 22:10       ` Jens-Uwe Morawski
2003-04-09 22:44         ` Adam Lindsay [this message]
2003-04-15 23:49         ` Adam Lindsay
2003-04-09 21:27     ` Jens-Uwe Morawski
2003-04-10 12:09       ` Bill McClain

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=20030409224440.9129@news.comp.lancs.ac.uk \
    --to=atl@comp.lancs.ac.uk \
    --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).