Thread View: comp.lang.postscript
2 messages
2 total messages
Started by Kevin Kells
Sun, 27 Sep 1992 07:08
is tilde character broken?
Author: Kevin Kells
Date: Sun, 27 Sep 1992 07:08
Date: Sun, 27 Sep 1992 07:08
23 lines
1330 bytes
1330 bytes
Hi folks, sorry if this is a repeat question. I use TeX/LaTeX to create text with the Spanish n-tilde character (\~n). When I use the PostScript Times-Roman font, the n-tilde doesn't look like an n with a little tilde over it; the tilde is printed larger-than-normal _inside_ the n instead of on top. My assessment of the problem is that TeX expects the tilde character to be small and properly positioned for the corresponding "x" character in a given font. Apparently, the PostScript tilde is larger and centered and expects to be miniaturized and raised to form the tilde "accent" for the "x" character. Who is correct? How can I fix/hack this so that it works? Please e-mail and I'll post if there is enough interest. Thanks, Kevin -- Kevin Kells <kells@iis.ethz.ch> telephone: +41-1-256-5746 Integrated Systems Laboratory, ETH-Zentrum, CH-8092 Zurich, Switzerland
Re: is tilde character broken?
Author: Berthold K.P. Horn
Date: Mon, 28 Sep 1992 12:16
Date: Mon, 28 Sep 1992 12:16
65 lines
2856 bytes
2856 bytes
In article <kells.717577699@iis> kells@iis.ethz.ch (Kevin Kells) writes:
Hi folks, sorry if this is a repeat question.
I use TeX/LaTeX to create text with the Spanish n-tilde character
(\~n). When I use the PostScript Times-Roman font, the n-tilde doesn't
look like an n with a little tilde over it; the tilde is printed
larger-than-normal _inside_ the n instead of on top.
My assessment of the problem is that TeX expects the tilde character to
be small and properly positioned for the corresponding "x" character
in a given font. Apparently, the PostScript tilde is larger and centered
and expects to be miniaturized and raised to form the tilde "accent"
for the "x" character.
Who is correct? How can I fix/hack this so that it works?
Please e-mail and I'll post if there is enough interest.
plain TeX and LaTeX have hard-wired positions for accents based
on where they are in Computer Modern. Here is the relevant part of
plain.tex:
\def\acute{\mathaccent"7013 }
\def\grave{\mathaccent"7012 }
\def\ddot{\mathaccent"707F }
\def\tilde{\mathaccent"707E }
\def\bar{\mathaccent"7016 }
\def\breve{\mathaccent"7015 }
\def\check{\mathaccent"7014 }
\def\hat{\mathaccent"705E }
\def\vec{\mathaccent"017E }
\def\dot{\mathaccent"705F }
\def\widetilde{\mathaccent"0365 }
\def\widehat{\mathaccent"0362 }
If you use fonts other than CM you have to redefine these macros, or
reencode these fonts to use the same encoding scheme as CM.
For example, if you use `texannew' encoding you'll want to use instead:
\def\acute{\mathaccent"70B4 } % acute
\def\grave{\mathaccent"7060 } % grave
\def\ddot{\mathaccent"70A8 } % dieresis
\def\tilde{\mathaccent"7098 } % tilde
\def\bar{\mathaccent"70AF } % macron
\def\breve{\mathaccent"70C6 } % breve
\def\check{\mathaccent"708D } % caron
\def\hat{\mathaccent"7088 } % circumflex
\def\dot{\mathaccent"70C7 } % dotaccent
What is happening to you without this change is the result of the fact that
Computer Modern has the character `circumflex', a small raised glyph
suitable for us as an accent in the position where Type 1 fonts have
`asciicircum', a large glyph that sits on the baseline, as you discovered.
Similarly, CM text fonts have `tilde', where Type 1 fonts have
`asciitilde'.
Read my diatribe on font encoding (:-) for more details.
Berthold K.P. Horn
Cambridge, Massachusetts, USA
Thread Navigation
This is a paginated view of messages in the thread with full content displayed inline.
Messages are displayed in chronological order, with the original post highlighted in green.
Use pagination controls to navigate through all messages in large threads.
Back to All Threads