From: Taco Hoekwater <taco.hoekwater@wkap.nl>
Cc: ntg-context@ntg.nl
Subject: Re: \sterling doesn't work in font-pos
Date: Wed, 28 Jul 1999 13:17:31 +0000 (GMT) [thread overview]
Message-ID: <14239.747.787406.26560@PC709.wkap.nl> (raw)
In-Reply-To: <000501bed8d6$1e72e600$0c01a8c1@loginbv.com>
>>>>> "Gilbert" == Gilbert van den Dobbelsteen <gilbert@login-bv.com> writes:
Gilbert> Hi there,
Gilbert> The macro \sterling results in {\it\$} which is an italics dollar sign ($)
Gilbert> when I use:
Gilbert> \setupbodyfont[pos]
Gilbert> Currently I solved it by saying: \char163, but that's not portable in any
Gilbert> way.
Agree. There are more chars affected by this.
Hans, I think the best thing we can do is add lines to enco-* for the
next update:
% [\redefinecharacter sterling]
\startencoding[texnansi]
\definecharacter sterling 163
....
\stopencoding
There are many more of these things (\paragraph,\dagger,\cent etc.),
and almost all of these text symbols do depend on font encoding.
Taco
prev parent reply other threads:[~1999-07-28 13:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-07-28 8:49 Gilbert van den Dobbelsteen
1999-07-28 13:17 ` Taco Hoekwater [this message]
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=14239.747.787406.26560@PC709.wkap.nl \
--to=taco.hoekwater@wkap.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).