From: "Adam Lindsay" <atl@comp.lancs.ac.uk>
Subject: Re: Capitalized headings
Date: Tue, 3 May 2005 23:58:56 +0100 [thread overview]
Message-ID: <20050503235856.24135@mail.comp.lancs.ac.uk> (raw)
In-Reply-To: <98D0564335EC4848A87BEDEFF4EA056B55C2@posti.kpatents.com>
Ville Voipio said this at Wed, 4 May 2005 00:32:59 +0300:
>As \uppercase is a plain TeX macro, fixing it is not a good
>choice, especially because it is known to be bad. However,
>if \WORD could be built on \cap but without the font size
>changing, it would work fine. The odd behaviour of \uppercased
>(and the reasons to use it instead of the other choices) remains
>unclear to me.
I'm not entirely sure what's going on here, either, but as you've
observed, the smallcaps mechanism handles these things very robustly. I
was mucking about in this area recently, so here's a hack that hooks into
that mechanism (hopefully without ruining the rest of the smallcaps).
Insert disclaimers here ;)
\unprotected
\def\useallcaps
{\def\cap@@uppercase{\the\everyuppercase\uppercased}%
\def\cap@@lowercase{\the\everylowercase\lowercased}%
\def\cap@@visualize{}}
\protected
\def\CAPITALIZED#1{\bgroup\useallcaps\smallcapped{#1}\egroup}
\CAPITALIZED{abcABCåäöÅÄÖ}
\smallcapped{abcABCåäöÅÄÖ}
\userealcaps
\smallcapped{abcABCåäöÅÄÖ}
This is new stuff to me, so I can't really articulate what's happening at
the moment. The code in core-fnt.tex isn't too tough to follow, though,
if you want to examine further.
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Adam T. Lindsay, Computing Dept. atl@comp.lancs.ac.uk
Lancaster University, InfoLab21 +44(0)1524/510.514
Lancaster, LA1 4WA, UK Fax:+44(0)1524/510.492
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
next prev parent reply other threads:[~2005-05-03 22:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-03 21:32 Ville Voipio
2005-05-03 22:58 ` Adam Lindsay [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-05-03 16:56 Ville Voipio
2005-05-02 17:49 Ville Voipio
2005-05-02 22:53 ` Adam Lindsay
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=20050503235856.24135@mail.comp.lancs.ac.uk \
--to=atl@comp.lancs.ac.uk \
--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).