From: Thomas A.Schmitz <thomas.schmitz@uni-bonn.de>
Subject: Re: small caps
Date: Wed, 2 Mar 2005 11:33:11 +0100 [thread overview]
Message-ID: <a3506e0135156ef35b7f3daa7dcd6d2b@uni-bonn.de> (raw)
In-Reply-To: <20050302095914.3272@mail.comp.lancs.ac.uk>
On Mar 2, 2005, at 10:59 AM, Adam Lindsay wrote:
> Hold on one minute... we're talking about encodings for alternate
> glyphs,
> right? That's orthogonal to what Unicode is about. 'a' and 'Asmall'
> pretty much take up the same unicode "slot". Only 'a' appears in the
> .cmap.xml file.
>
No, of course you're right. I thought that they were given a value in
the FFxx range, but that's not right; they don't appear in the cmap,
only in the afm. So the only thing I can think of: there are only so
many ways to refer to small caps, Xsmall or X.small or X_small or even
X-small. We could provide alternatives for that in perl, making
additions as we go. It's a brute-force attack, kind of aiming with a
machine gun, but since fonts are such moving targets...
> Now that would be a useful thing, regardless. I don't know, but I'll
> have
> a look. I suspect we'll have to create one ourselves. An idle thought
> (with the corresponding devilishness) occurs to me: all that
> information
> is in ConTeXt already. Hmm...
>
> What form would be the best? Some simple XML? A perl-friendly list?
For the time being, I'm thinking of a very simple list that could just
serve as a pattern for arranging the lines I get from processing the
cmap.xml. I'm just thinking, not writing code yet...
Best
Thomas
next prev parent reply other threads:[~2005-03-02 10:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-26 9:13 Thomas A.Schmitz
2005-02-26 23:34 ` Adam Lindsay
2005-02-27 7:57 ` Thomas A.Schmitz
2005-02-27 9:39 ` Adam Lindsay
2005-03-02 6:18 ` Thomas A.Schmitz
2005-03-02 9:59 ` Adam Lindsay
2005-03-02 10:33 ` Thomas A.Schmitz [this message]
2005-03-02 10:54 ` Hans Hagen
2005-03-02 10:58 ` Adam Lindsay
2005-02-27 17:58 ` h h extern
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=a3506e0135156ef35b7f3daa7dcd6d2b@uni-bonn.de \
--to=thomas.schmitz@uni-bonn.de \
--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).