Lucida doesn't work in TL 2013 / latest ConTeXt
Hi, in TL 2013 neither \setupbodyfont[lucida] nor \setupbodyfont[lucidanova] works. The first one gives: !LuaTeX error: Invalid local font in font lbr! ==> Fatal error occurred, no output PDF file produced! and the other one complains about ! Math error: parameter \Umathquad\displaystyle is not set. (I've set "export TEXMFLOCAL=/path/to/texmf/with/both/lucidas".) When trying the same with latest distribution I get ! LuaTeX error .../context/tex/texmf-context/tex/context/base/math-act.lua:101: attempt to perform arithmetic on field 'size' (a nil value) stack traceback: .../context/tex/texmf-context/tex/context/base/math-act.lua:101: in function 'mathematics_checkprivateparameters' [string "local mathematics_initializeparameters = math..."]:10: in function 'runner' .../context/tex/texmf-context/tex/context/base/math-act.lua:39: in function 'assignmathparameters' .../context/tex/texmf-context/tex/context/base/math-vfu.lua:917: in function <.../context/tex/texmf-context/tex/context/base/math-vfu.lua:537> (...tail calls...) .../context/tex/texmf-context/tex/context/base/font-def.lua:423: in function 'read' .../context/tex/texmf-context/tex/context/base/font-ctx.lua:947: in function 'definefont_two' [string "\directlua "]:1: in main chunk. system > tex > error on line 52 in file /Users/mojca/context/gnuplot/mojca/texmf/doc/context/third/gnuplot/gnuplot-context-doc.tex: LuaTeX error ... and with lucidanova I get the same error as in TeX Live. I'm using \sometxt{} inside metapost code to draw labels, so maybe that's connected. Mojca
I'm sorry. I was pointing TEXMFLOCAL to the wrong (older) version of fonts without OT in the filename. However, the Type1 fonts still don't work. Mojca On Fri, Apr 19, 2013 at 1:31 PM, Mojca Miklavec wrote:
Hi,
in TL 2013 neither \setupbodyfont[lucida] nor \setupbodyfont[lucidanova] works.
The first one gives:
!LuaTeX error: Invalid local font in font lbr!
==> Fatal error occurred, no output PDF file produced!
and the other one complains about
! Math error: parameter \Umathquad\displaystyle is not set.
(I've set "export TEXMFLOCAL=/path/to/texmf/with/both/lucidas".)
When trying the same with latest distribution I get
! LuaTeX error .../context/tex/texmf-context/tex/context/base/math-act.lua:101: attempt to perform arithmetic on field 'size' (a nil value) stack traceback: .../context/tex/texmf-context/tex/context/base/math-act.lua:101: in function 'mathematics_checkprivateparameters' [string "local mathematics_initializeparameters = math..."]:10: in function 'runner' .../context/tex/texmf-context/tex/context/base/math-act.lua:39: in function 'assignmathparameters' .../context/tex/texmf-context/tex/context/base/math-vfu.lua:917: in function <.../context/tex/texmf-context/tex/context/base/math-vfu.lua:537> (...tail calls...) .../context/tex/texmf-context/tex/context/base/font-def.lua:423: in function 'read' .../context/tex/texmf-context/tex/context/base/font-ctx.lua:947: in function 'definefont_two' [string "\directlua "]:1: in main chunk.
system > tex > error on line 52 in file /Users/mojca/context/gnuplot/mojca/texmf/doc/context/third/gnuplot/gnuplot-context-doc.tex: LuaTeX error ...
and with lucidanova I get the same error as in TeX Live.
I'm using \sometxt{} inside metapost code to draw labels, so maybe that's connected.
Mojca
On 4/19/2013 2:04 PM, Mojca Miklavec wrote:
I'm sorry. I was pointing TEXMFLOCAL to the wrong (older) version of fonts without OT in the filename.
However, the Type1 fonts still don't work.
Did we change something with the type 1? In mkiv ... we probably never finished the mappings ... waste of time now that we have otf. Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------
Did we change something with the type 1? In mkiv ... we probably never finished the mappings ... waste of time now that we have otf.
This makes me believe that I will eventually HAVE to purchase (and by "purchase" I really mean "re-purchase) the OTF versions in order to use my Lucida fonts. This is a bit discouraging. Troy
On Fri, Apr 19, 2013 at 09:12:48AM -0500, Troy Henderson wrote:
Did we change something with the type 1? In mkiv ... we probably never finished the mappings ... waste of time now that we have otf.
This makes me believe that I will eventually HAVE to purchase (and by "purchase" I really mean "re-purchase) the OTF versions in order to use my Lucida fonts. This is a bit discouraging.
Given the amount of re-work that went into Lucida OT, a re-purchase is justified ;) Regards, Khaled
Given the amount of re-work that went into Lucida OT, a re-purchase is justified ;)
That all depends on how it is being used. I'm not sure what advantage the OT version of the font would have to me over the Type1 version. If a reasonable justification could convince me, then I might agree. Troy
On 4/19/2013 4:35 PM, Troy Henderson wrote:
Given the amount of re-work that went into Lucida OT, a re-purchase is justified ;)
That all depends on how it is being used. I'm not sure what advantage the OT version of the font would have to me over the Type1 version. If a reasonable justification could convince me, then I might agree.
- kerning, corrections etc etc across the whole font (multiple type 1 fonts are isolated) - more and improved glyphs, more alphabets - more extensive latin support + precomposed - alternate shapes - more advanced extensibles - more efficient pdf files - cut and paste from pdf - cleaner implementation at the tex end - all benefits that come with mkiv Hans -- ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------
On 4/19/2013 4:12 PM, Troy Henderson wrote:
Did we change something with the type 1? In mkiv ... we probably never finished the mappings ... waste of time now that we have otf.
This makes me believe that I will eventually HAVE to purchase (and by "purchase" I really mean "re-purchase) the OTF versions in order to use my Lucida fonts. This is a bit discouraging.
The problem is that in mkiv we make a virtual unicode font on the fly and for that we need vectors and lucida has a bad history: when I started supporting it, we coul duse the original B&H / Y&Y vectors but when tug took over, these were dropped in favor of some latex encoding. So, in mkii it does work, but you need the original tfm files. In mkiv we need special vectors as well because lucida's internal mapping is still non-tex and someone has to do all that checking. Now, given that we have proper otf fonts (relatively cheap for a font as tug paid for conversion) it makes no sense in mkiv to spent time on the old fonts (1: I don't use them, 2: I have no fun in doing that, 3: Nor time, 4: we have an alternative). Keep in mind that a virtual type1 based lucida is never as good and complete as the newer otf. Concerning 'repurchase' .. the lucida set is a bargain, definitely if you compare it to other fonts in that quantities. Of course you can also consider xits, pagella, termes etc Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------
On Fri, Apr 19, 2013 at 11:12 AM, Troy Henderson
Did we change something with the type 1? In mkiv ... we probably never
finished the mappings ... waste of time now that we have otf.
This makes me believe that I will eventually HAVE to purchase (and by "purchase" I really mean "re-purchase) the OTF versions in order to use my Lucida fonts. This is a bit discouraging.
Troy
We just purchased the OTF versions. I'd rather have TeX developers focus on getting OTF support right than preserving legacy capabilities. For years we have been able to format old docs with current TeX systems. Now I just hope the old docs will work without too many changes using OTF versions of the fonts.
___________________________________________________________________________________ If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context webpage : http://www.pragma-ade.nl / http://tex.aanhet.net archive : http://foundry.supelec.fr/projects/contextrev/ wiki : http://contextgarden.net
___________________________________________________________________________________
--
George N. White III
On 4/19/2013 8:16 PM, George N. White III wrote:
On Fri, Apr 19, 2013 at 11:12 AM, Troy Henderson
mailto:thenders@gmail.com> wrote: Did we change something with the type 1? In mkiv ... we probably never finished the mappings ... waste of time now that we have otf.
This makes me believe that I will eventually HAVE to purchase (and by "purchase" I really mean "re-purchase) the OTF versions in order to use my Lucida fonts. This is a bit discouraging.
Of course Troy could complete the existing lucida mkiv vectors in lucida-typeone-math.lfg -)
Troy
We just purchased the OTF versions. I'd rather have TeX developers focus on getting OTF support right than preserving legacy capabilities.
In luatex we're 'mostly' compatible with the old tex engine but as opentype math support is more advanced, the focus is on supporting that as good as possible. Also, as opentype math originates at MS/word with cambria as benchmark that's mostly setting the baseline. Of course, in context mkiv we can go a bit beyond that (and there is already some in place). We can also
For years we have been able to format old docs with current TeX systems. Now I just hope the old docs will work without too many changes using OTF versions of the fonts.
In principle regular math should work ok. At some point we might benefit from the opening up of math parameters (quite some was hard coded in the traditional tex engine, much has been moved to the font parameters and luatex also provides more control). Some constructs (like radicals and accents) are more native now and less depend on macro magic. There will never be full visual compatibility, if only because open type doesn't have the (dimensional) limits of tfm (that made sense at the time). Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------
On 4/19/2013 1:31 PM, Mojca Miklavec wrote:
Hi,
in TL 2013 neither \setupbodyfont[lucida] nor \setupbodyfont[lucidanova] works.
The first one gives:
!LuaTeX error: Invalid local font in font lbr!
==> Fatal error occurred, no output PDF file produced!
and the other one complains about
! Math error: parameter \Umathquad\displaystyle is not set.
normally that means that the font is not found
(I've set "export TEXMFLOCAL=/path/to/texmf/with/both/lucidas".)
When trying the same with latest distribution I get
! LuaTeX error .../context/tex/texmf-context/tex/context/base/math-act.lua:101: attempt to perform arithmetic on field 'size' (a nil value) stack traceback:
i can intercept that one
..../context/tex/texmf-context/tex/context/base/math-act.lua:101: in function 'mathematics_checkprivateparameters' [string "local mathematics_initializeparameters = math..."]:10: in function 'runner' ..../context/tex/texmf-context/tex/context/base/math-act.lua:39: in function 'assignmathparameters' ..../context/tex/texmf-context/tex/context/base/math-vfu.lua:917: in function <.../context/tex/texmf-context/tex/context/base/math-vfu.lua:537> (...tail calls...) ..../context/tex/texmf-context/tex/context/base/font-def.lua:423: in function 'read' ..../context/tex/texmf-context/tex/context/base/font-ctx.lua:947: in function 'definefont_two' [string "\directlua "]:1: in main chunk.
system > tex > error on line 52 in file /Users/mojca/context/gnuplot/mojca/texmf/doc/context/third/gnuplot/gnuplot-context-doc.tex: LuaTeX error ...
and with lucidanova I get the same error as in TeX Live.
I'm using \sometxt{} inside metapost code to draw labels, so maybe that's connected.
minimal example ... tex processing doesn't happen in mp so an error means that at the tex end there is an issue Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------
participants (5)
-
George N. White III
-
Hans Hagen
-
Khaled Hosny
-
Mojca Miklavec
-
Troy Henderson