From: David Wooten <dw@trichotomic.net>
Subject: Font encoding: \uppercased
Date: Fri, 25 Mar 2005 17:30:19 -0800 [thread overview]
Message-ID: <4c055ecc6f80aa11c2437e20700c3d30@trichotomic.net> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 526 bytes --]
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
earlier with the font in general. For example, with \uppercased{Krübel}
I receive: KRüBEL.
Do I need to "make a statement of my intent" in a typescript file or
somewhere else to resolve this?
Kind regards,
David
[-- Attachment #1.2: Type: text/enriched, Size: 546 bytes --]
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]<italic> </italic>issue here, as I
had similar issues earlier with the font in general. For example, with
\uppercased{Krübel} I receive: KRüBEL.
Do I need to "make a statement of my intent" in a typescript file or
somewhere else to resolve this?
Kind regards,
David
[-- Attachment #2: Type: text/plain, Size: 139 bytes --]
_______________________________________________
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
next reply other threads:[~2005-03-26 1:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-26 1:30 David Wooten [this message]
2005-03-26 19:35 ` Vit Zyka
2005-04-09 3:06 ` David Wooten
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=4c055ecc6f80aa11c2437e20700c3d30@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).