[lucida] Odd bug with Lucida Bright Math OT, icomma and TeX Live 2015

Vincent Goulet vincent.goulet at me.com
Wed Sep 9 15:42:25 CEST 2015


> Le 2015-09-09 à 04:17, Bruno Voisin <bvoisin at me.com> a écrit :
> 
>> Le 9 sept. 2015 à 09:44, Bruno Voisin <bvoisin at me.com> a écrit :
>> 
>> First thing: testing more thoroughly today, it appears the problem goes away if icomma is loaded after fontspec and unicode-math.
>> 
>> [...]
>> 
>> Also, the nice thing with both fontspec and unicode-math is that you don't have to care whether you're using XeLaTeX or LuaLaTeX. The packages include macro definitions for both (such as unicode-math-xetex.sty and unicode-math-luatex.sty for unicode-math.sty); at runtime the packages detect the engine they're run with, and pick up the appropriate set of definitions.
>> 
>> Having lualatex-math specific to LuaLaTeX (and maybe one day a similar xelatex-math) breaks this philosophy and makes things engine-specific, which is a bit unfortunate.
>> 
>> [...]
> 
> Well, I should have looked more closely: unicode-math, when used with LuaLaTeX, calls lualatex-math (there's a \RequirePackage{lualatex-math} at the beginning of unicode-math-luatex.sty). So whatever needs to be done, is done already; the user is not supposed to call lualatex-math herself.
> 
> The outcome seems to be that icomma should come at the end of the package list in the preamble, not first. Sadly, it's not the only package to be like this: hyperref etc., all those that redefine macros introduced by other packages.
> 
> Bruno

Thanks Bruno for your extensive testing!

As mentioned in my original post, the more recent (and flexible) package ncccomma works correctly whenever it is loaded. I may just switch to using this package after all.

v.


More information about the lucida mailing list