I just bought the new Lucida font from TUG and installed it in my local texmf under fonts/opentype/bh/lucidaot/ Then I did: mtxrun --generate mtxrun --script font --reload to be sure the new install will be picked up by ConTeXt mkiv. I think I did read somewhere that mkiv will prefer otf above pfb files, if these otfs are present. However, after running \setupbodyfont[lucida,10pt] the log shows the old pfb's used: instead of an otf? What could have happended? What am I doing wrong? By the way I do not see the lucida math fonts in the package. Are these missing? Hans van der Meer
Am 19.03.2012 um 09:38 schrieb Meer, H. van der:
I just bought the new Lucida font from TUG and installed it in my local texmf under fonts/opentype/bh/lucidaot/ Then I did: mtxrun --generate mtxrun --script font --reload to be sure the new install will be picked up by ConTeXt mkiv.
I think I did read somewhere that mkiv will prefer otf above pfb files, if these otfs are present.
It’s the users decision which font should be chosen because each font has a unique name and when you want a automatic replacement (like for latin modern and computer modern in mkii) you have to tell this the system.
However, after running \setupbodyfont[lucida,10pt] the log shows the old pfb's used: instead of an otf?
What could have happended? What am I doing wrong?
By the way I do not see the lucida math fonts in the package. Are these missing?
The new version of the lucida fonts use different names for the typescript, we have now: - “lucida” for the old type1 version, - “lucidaot” for the new opentype version and - “lucidanova” as alternative name for the opentype version. Wolfgang
On 19 mrt. 2012, at 10:01, Wolfgang Schuster wrote: The new version of the lucida fonts use different names for the typescript, we have now: - “lucida” for the old type1 version, - “lucidaot” for the new opentype version and - “lucidanova” as alternative name for the opentype version. The "lucidaot" works. But I have observed the following, which might be caused by a naming difference. I am using ConTexT version 2012.03.13 21:26 MKIV; the latest I can download. The example is: \setuppapersize[A5][A5] \setuppagenumbering[state=off] \setupbodyfont[lucidaot,sans,10pt] \starttext sans {\it sans italic}. \stoptext But "sans italic" is not typeset in italic, see the output pdf below. In the log I see a message about a missing lucidanova.lfg. Present in a more recent beta perhaps In the opentype font list I do not find LucidaSansOT-Oblique but I do see LucidaSansOT-Italic. Could it be something should be changed in a typescript? Hans van der Meer In the log: ConTeXt ver: 2012.03.13 21:26 MKIV fmt: 2012.3.19 int: english/english system > cont-new.mkiv loaded (/Users/hans/TeX/context-new/tex/texmf-context/tex/context/base/cont-new.mkiv system > beware: some patches loaded from cont-new.mkiv ) system > test.top loaded (test.top) fonts > latin modern fonts are not preloaded languages > language en is active fonts > typescripts > unknown: library 'loc' (/Users/hans/TeX/context-new/tex/texmf-context/tex/context/base/type-imp-lucida-opentype.mkiv) fonts > goodies > goodie file 'lucidanova-math.lfg' is not found {/Users/hans/TeX/context-new/tex/texmf-context/fonts/map/pdftex/context/mkiv-base.map} fonts > defining > forced type otf of LucidaSansOT-Oblique not found fonts > defining > font with asked name 'LucidaSansOT-Oblique' is not found using lookup 'file' fonts > defining > unknown font LucidaSansOT-Oblique, loading aborted fonts > defining > unable to define LucidaSansOT-Oblique.otf as [lucidaot-10pt-ss-it-0--0] backend > xmp > using file '/Users/hans/TeX/context-new/tex/texmf-context/tex/context/base/lpdf-pdx.xml' pages > flushing realpage 1, userpage 1, subpage 1 )
Am 19.03.2012 um 11:12 schrieb Meer, H. van der:
On 19 mrt. 2012, at 10:01, Wolfgang Schuster wrote:
The new version of the lucida fonts use different names for the typescript, we have now:
- “lucida” for the old type1 version, - “lucidaot” for the new opentype version and - “lucidanova” as alternative name for the opentype version.
The "lucidaot" works. But I have observed the following, which might be caused by a naming difference. I am using ConTexT version 2012.03.13 21:26 MKIV; the latest I can download.
The example is: \setuppapersize[A5][A5] \setuppagenumbering[state=off]
It’s “state=stop” and works here only because context checks only the “state=start” case.
\setupbodyfont[lucidaot,sans,10pt] \starttext sans {\it sans italic}. \stoptext
But "sans italic" is not typeset in italic, see the output pdf below. In the log I see a message about a missing lucidanova.lfg. Present in a more recent beta perhaps In the opentype font list I do not find LucidaSansOT-Oblique but I do see LucidaSansOT-Italic.
Could it be something should be changed in a typescript?
Can you try to attached typescript file, I replaced the files for italic and bolditalic fonts for the sans style with the names from the latex example document. The slanted and boldslanted alternatives for the sans style are also fixed. Wolfgang
Le 19/03/2012 11:36, Wolfgang Schuster a écrit :
Can you try to attached typescript file, I replaced the files for italic and bolditalic fonts for the sans style with the names from the latex example document. The slanted and boldslanted alternatives for the sans style are also fixed.
Wolfgang
+Small Caps support: 38,42d37 < \starttypescript [\s!serif] [lucidanova,lucidaot,otlucida] < \definefontsynonym [\s!SerifCaps] [\s!Serif] [\s!features=smallcaps] < %definefontsynonym [\s!SerifBoldCaps] [\s!SerifBold] [\s!features=smallcaps] < \stoptypescript < The SerifBoldCaps line is commented out since I get an error at processing… and can't figure why… Renaud
Am 24.03.2012 um 01:58 schrieb Renaud AUBIN:
Le 19/03/2012 11:36, Wolfgang Schuster a écrit :
Can you try to attached typescript file, I replaced the files for italic and bolditalic fonts for the sans style with the names from the latex example document. The slanted and boldslanted alternatives for the sans style are also fixed.
Wolfgang
+Small Caps support: 38,42d37 < \starttypescript [\s!serif] [lucidanova,lucidaot,otlucida] < \definefontsynonym [\s!SerifCaps] [\s!Serif] [\s!features=smallcaps] < %definefontsynonym [\s!SerifBoldCaps] [\s!SerifBold] [\s!features=smallcaps] < \stoptypescript <
The SerifBoldCaps line is commented out since I get an error at processing… and can't figure why…
For smallcaps you can use the following command in your document: \unexpanded\def\sc{\setff{smallcaps}} With this you can get also smallcaps for the bold or italic style while with the definition in the typescript (as in your patch) smallcaps are a font switch and you can only get smallcaps for the regular style. Bold doesn’t work because the typescript use a wrong name for the files and Hans hasn’t released a new beta yet with the correct names. Wolfgang
participants (3)
-
Meer, H. van der -
Renaud AUBIN -
Wolfgang Schuster