Re: Problem with ~ and ^

[Richard Tietjen <rtietjen@kale.connix.com>]

Aren't \^ and \~ accent codes in LaTeX?  They are supposed to be
followed by a character to accent and it's normal that by themselves
do nothing.

Bruce Momjian <root@candle.pha.pa.us> writes:

> I am having some trouble installing my own fonts into LaTeX using
> psnfss.  I have read dvips.dvi and gotten the needed commands.
> 
> For some reason, the caret (^) and tilde (~) symbols will not print in
> any of my fonts.  I have fonts from three foundries, and they all 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?
> 
> Seems that \~{} and \textasciitilde are different, and I don't have \~{}
> in my font.
> 
> 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.
> 
> I am now using:
> 	
> 	\def\atilde{\raisebox{.5ex}{\em\textasciitilde}\,}
> 	\def\acircum{\textasciicircum\,}
> 	
> 	\renewcommand{\~}{\atilde}
> 	\renewcommand{\^}{\acircum}
> 
> These work fine because I am redefining \~ to a raised \textasciitilde.
> 
> -- 
>   Bruce Momjian                        |  http://www.op.net/~candle
>   root@candle.pha.pa.us                |  (610) 853-3000
>   +  If your life is a hard drive,     |  830 Blythe Avenue
>   +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026
> 
> 
> 
> -- 
>   Bruce Momjian                        |  http://www.op.net/~candle
>   root@candle.pha.pa.us                |  (610) 853-3000
>   +  If your life is a hard drive,     |  830 Blythe Avenue
>   +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026
> 
> 

-- 
==-==-==-==-==-==-==-==-==-==-==-==-==-==-==-==-==-==-==-==-==
Richard Tietjen                            rtietjen@connix.com
       "Irony is what they make two-edged swords from."