From: Aditya Mahajan <adityam@umich.edu>
Subject: Re: typeface question: no small capped
Date: Fri, 18 Aug 2006 00:12:18 -0400 (EDT) [thread overview]
Message-ID: <Pine.WNT.4.63.0608172345500.2264@nqvgln> (raw)
In-Reply-To: <19AAF825-FB2C-4AEF-92D3-E8F01B9CADB2@uni-bonn.de>
On Thu, 17 Aug 2006, Thomas A. Schmitz wrote:
>
> On Aug 16, 2006, at 11:27 PM, Aditya Mahajan wrote:
>
>>
>> I want to write a conference paper according to IEEE (latex) format,
>> and this involves copying all the bad font choices in IEEEtran.cls
>> (Times text, cm math, ughh...). I need smallcaps only for section
>> titles, so right now I am doing a local switch to latin modern for the
>> section titles. This is what IEEEtran.cls also does. Do you think that
>> faking smallcaps from Times will look better? If so, how can I fake
>> smallcaps?
>>
>> Thanks,
>> Aditya
>
> Faking is already implemented: \kap{foo} (see cont-eni, chapter 5.7).
Why is there no "true" faking. I mean with \kap (or \cap or
\smallcapped, all of which are the same), the faked text does not look
like small caps. Compare the output of
{\sc Introduction Again}
\smallcapped{Introduction Again}
Why is there nothing along the lines of the following (unless I missed
something in core-fnt.tex)
\def\mysmallcapped{\let\processword\domysmallcapped\processwords}
\def\domysmallcapped#1{\startdomysmallcapped#1\stopdomysmallcapped}
\def\startdomysmallcapped#1#2\stopdomysmallcapped{\cap{#1\cap{#2}}}
\mysmallcapped{Introduction Again}
I agree that this does not look great, but does look better than using
lm small caps with times text.
> You decide if this is uglier than using latin modern for section
> titles. I have actually bought a couple of professional fonts, and
> once you've seen the real McCoy, you'll find the fake ones repulsive.
> But most people won't even realize, I guess.
Sad but true. Hopefully the STIX fonts will be released[1] and I will
be able to use real small caps with a times like font.
Aditya
[1] I checked their website and it was updated yesterday. Looks like
they will finally make a release :)
prev parent reply other threads:[~2006-08-18 4:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-16 18:42 Aditya Mahajan
2006-08-16 19:22 ` Thomas A. Schmitz
2006-08-16 21:27 ` Aditya Mahajan
2006-08-17 5:41 ` Thomas A. Schmitz
2006-08-18 4:12 ` Aditya Mahajan [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=Pine.WNT.4.63.0608172345500.2264@nqvgln \
--to=adityam@umich.edu \
--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).