From: David Wooten <dw@trichotomic.net>
Subject: Re: Font encoding: \uppercased
Date: Fri, 8 Apr 2005 20:06:08 -0700 [thread overview]
Message-ID: <7465a5f0737d95169d5e8c317e61d7e7@trichotomic.net> (raw)
In-Reply-To: <4245B97D.8040602@seznam.cz>
Greetings Vit, all,
Thanks for the response.
I'm finally getting around to looking into this again. My first
attempts haven't yielded any good results. Could you (or someone) say a
little more (newbie-explicit)? I assume that the enco-*.tex files
you're referring to are in .../context/base/, where there are a series
of 30 or so such files. It isn't clear to me which one to use. Does the
encoding refer to font encoding? \x1f—in which case there is no
"enco-8r.tex"\x1f— or to something else? — enco-pdf.tex for example.
Thanks very much,
David Wooten
On Mar 26, 2005, at 11:35 AM, Vit Zyka wrote:
> David Wooten wrote:
>> Greetings all,
>> Taco mentioned the command \uppercased{to get all uppercase letters},
>> and it works just fine…until I try to use my self-installed fonts.
>> The quirks come up with diacritics, and this leads me to believe that
>> there is an [encoding] or [regime]/ /issue here, as I had similar
>> issues
>
> Yes, \uccode and \lccode are encoding-dependent and are defined in
> enco-*.tex files. So, look into the encoding file you are using and
> add the their definition between
> \startmapping[st1]
> \definecasemap 152 184 152
> \stopmapping
> with meaning: character 152 has lower counterpart 184 and upper one
> 152 (152 is uppercase letter).
>
> (or for continuous sequence there is abbreviation
> \definecasemaps 160 to 188 lc +32 uc 0
> with meaning:
> \definecasemap 160 182 160
> \definecasemap 161 183 161
> ...
> \definecasemap 188 220 188
> )
>
> vit
next prev parent reply other threads:[~2005-04-09 3:06 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 [this message]
2005-04-09 15:00 ` Vit Zyka
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=7465a5f0737d95169d5e8c317e61d7e7@trichotomic.net \
--to=dw@trichotomic.net \
--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).