From: Vit Zyka <vit.zyka@seznam.cz>
Subject: Re: Font encoding: \uppercased
Date: Sat, 09 Apr 2005 17:00:42 +0200 [thread overview]
Message-ID: <4257EE1A.9000500@seznam.cz> (raw)
In-Reply-To: <7465a5f0737d95169d5e8c317e61d7e7@trichotomic.net>
David Wooten wrote:
> so such files. It isn't clear to me which one to use. Does the encoding
> refer to font encoding?
Yes. It describes where the glyph name is presented in the font.
> \x1f—in which case there is no "enco-8r.tex"\x1f— or
> to something else? — enco-pdf.tex for example.
I think you are looking for enco-ans.tex: texnansi encoding.
Vit
next prev parent reply other threads:[~2005-04-09 15:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-26 1:30 David Wooten
2005-03-26 19:35 ` Vit Zyka
2005-04-09 3:06 ` David Wooten
2005-04-09 15:00 ` Vit Zyka [this message]
2005-04-11 0:24 ` Font encoding: \uppercased: \WORD David Wooten
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=4257EE1A.9000500@seznam.cz \
--to=vit.zyka@seznam.cz \
--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).