It is my understanding that output of ~ and ^ is not being handled
correctly.
LyX outputs ~ as \~, and ^ as \^. However, it is my understanding that
\^ is really \^{}, to be used to put above a latter in \^{a}. Same with
~.
I believe the proper output of ~ is \textasciitilde, and ^ is
\textasciicircum.
Attached are two e-mail messages I sent to the teTeX maintainer. The
e-mails describe a problem I had with non-TeX fonts where there was no
symbol for \~, while there was one for \textasciitilde.
---------------------------------------------------------------------------
A week ago, I asked a question about afm2tfm, and I have it working
great now. Thanks. Nice to have 500 fonts to choose from.
I am afraid I have one more problem. For some reason, the caret (^) and
tilde (~) symbols will not print in any of my fonts. I have fonts from
three foundries, and they call don't print carets or tildes. I am
printing them as \~{} and \^{}.
I tested the other characters on my keyboard on top of the number from 1
to 0, and they all print, except caret and tilde.
My latex log shows:
Missing character: There is no ^^B in font p052003l!
for caret symbol, and
Missing character: There is no ^^C in font p052003l!
for tilde font.
I see \textasciitilde and \textasciicircum as I will looking around
dejanews, and I am totally shocked that they work, and look fine. Now,
I don't understand why, because the stock palatino tfm/vf fonts use \~{}
and \^{} directly. Is \~{} accessing a different font I don't have,
while I do have \textasciitilde?
Was some special hand-coding done in the stock font files for these
symbols? Seems they weren't in computer modern in a standard way, and
that is why there may be a problem with them for me. Are there any
other weird characters I should know about?
The strange thing is that many other more exotic symbols do print, and I
am using many of them. Symbols like the n-dash, and the (c) copyright
symbol print fine, so I must be doing something right with these fonts.
When using the supplied palatino font tfm/vf files, the ~ and ^ print
fine, but the (c) and n-dash don't print in PDF files, meaning the
standard palatino tfm/vf files do not match my encoding, while the
encodings I created with afm2tfm and vptovf did enable me to print these
in PDF files.
---------------------------------------------------------------------------
> A week ago, I asked a question about afm2tfm, and I have it working
> great now. Thanks. Nice to have 500 fonts to choose from.
>
> I am afraid I have one more problem. For some reason, the caret (^) and
> tilde (~) symbols will not print in any of my fonts. I have fonts from
> three foundries, and they call don't print carets or tildes. I am
> printing them as \~{} and \^{}.
OK, I read this on DejaNews. Seems that \~{} and \textasciitilde are
different, and I don't have \~{} in my font. Is this person right?
---------------------------------------------------------------------------
CM fonts use an encoding (TeX text or OT1) that has circumflex accent
where ASCII has asciicircumflex and tilde accent where ASCII has asciitilde.
When you use something like \~{} you get the tilde accent. When you use
$\sim$ you get a mathematical relation, not asciitilde.
Use \textasciitilde and \textasciicircum - of course this requires a font
that has those glyphs (like any of the thousands of fonts in Type 1 format)
and an encoding that provides access to it (like T1, LY1, or LM1).
The asciitilde and asciicircum in EC are kind of a compromise - not quite
accents, but not quite low enough and large enough...
--
Bruce Momjian | http://www.op.net/~candle
[EMAIL PROTECTED] | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
