| View previous topic :: View next topic |
| Author |
Message |
jautschbach
Joined: 17 Mar 2006 Posts: 11
|
Posted: Fri Apr 28, 2006 12:51 pm Post subject: lucidacal option seems to cause problems with Y&Y tex |
|
|
Hi there
I tried using the "lucidacal" option of mtpro2 with Y&Y tex. The problem is:
(c:/localtexmf/tex/latex/mtpro2/omslbm.fd)
! Font OMS/lbm/m/n/10.95=hlcry at 9.85492pt not loadable: Metric (TFM) file not
found
(TEXNANSI=C:\YANDY\FONTS\TFM\TEXNANSI\TFM;C:\YANDY\FONTS\TFM\NONTEXT\;C:\YAND
Y\FONTS\TFM\TEXNANSI\;c:\localtexmf\fonts\\).
I used
\usepackage[LY1]{fontenc}
\usepackage{textcomp}
\usepackage{times}
\usepackage[subscriptcorrection,nofontinfo,lucidacal]{mtpro2}
I think there is a problem here with the lucida font naming scheme. Y&Y expects the original names.
Jochen |
|
| Back to top |
|
 |
WaS
Joined: 07 Feb 2006 Posts: 27 Location: Erlangen, Germany
|
Posted: Fri Apr 28, 2006 5:33 pm Post subject: |
|
|
mtpro expects the font (TFM) name that is used in the new Lucida
distribution. If you get the "new Lucida" to work on Y&Y TeX, the
lucidacal option for mtpro will work, too. |
|
| Back to top |
|
 |
jautschbach
Joined: 17 Mar 2006 Posts: 11
|
Posted: Thu May 04, 2006 11:18 am Post subject: |
|
|
| WaS wrote: | mtpro expects the font (TFM) name that is used in the new Lucida
distribution. If you get the "new Lucida" to work on Y&Y TeX, the
lucidacal option for mtpro will work, too. |
I have no idea what exactly I'm doing here but this simple change in "omslbm.fd" of the mtpro2 package seems to work, both with Y&Y and with MiKTeX
<snip>
\DeclareFontFamily{OMS}{lbm}{\skewchar\font48}
%original \DeclareFontShape{OMS}{lbm}{m}{n}{<->s * [.9]hlcry}{}
%original \DeclareFontShape{OMS}{lbm}{b}{n}{<->s * [.9]hlcdy}{}
% modified: the following uses the old Y&Y font names instead
\DeclareFontShape{OMS}{lbm}{m}{n}{<->s * [.9]lbms}{}
\DeclareFontShape{OMS}{lbm}{b}{n}{<->s * [.9]lbmsd}{}
\endinput
<snip>
Jochen |
|
| Back to top |
|
 |
|