Problem with Norman Fonts
fsnow at INAME.COM
Tue Nov 18 07:48:45 UTC 1997
The Norman font uses #160 for lowercase t with dot under. This is where
Windows expects the non-breaking space to be. AFAIK, there is no good
solution other than to switch to a different font encoding.
fsnow at iname.com
From: Francois Voegeli <l50948 at SAKURA.KUDPC.KYOTO-U.AC.JP>
>It seems that the latest version of Word in the Office suite does not
>recognize the non-breakable space when I use these fonts, a thing which
>has very bad side effects.
More information about the INDOLOGY