On 2016-05-20, Guillaume Munch wrote:
> Le 20/05/2016 19:26, Scott Kostyshak a écrit :
>> On Fri, May 20, 2016 at 04:06:22PM +0000, Guenter Milde wrote:
>>> On 2016-05-20, Jean-Marc Lasgouttes wrote:
>>>> Le 20/05/2016 à 13:17, Guenter Milde a écrit :
>>>>> On 2016-05-20, Scott Kostyshak wrote:
>>>>>> There have been some changes in the luatex engine that will be
>>>>>> shipped with TeX Live 2016 that cause many of our tests to fail
>>>>>> (500 something instead of 100 something on TL 2015). The root
>>>>>> issue is discussed on the LuaTeX mailing list at [1].
>>>>>> There is a transitional package available, luatex85, that should
>>>>>> make our current LuaTeX code work. A reasonable approach for now
>>>>>> would be to use the package if it is available and to not use it
>>>>>> if not, keeping the rest of our LuaTeX export code the same.
...
>>>>> We could just add
...
>>>> \IfFileExists{luatex85.sty}{\usepackage{luatex85}}{}
...
>> Should we do this only when we use code that we think needs it? Or
>> should we just add it to all of our LuaTeX exports?
I propose to do this with every LuaTeX export
+3 simple (no LyX-logic required)
+1 no risk of LyX getting it wrong
-1 eventually spurious package loading
> For 2.2 this could be shipped as a module, to be deprecated and updated
> into an empty module once LyX decides to adopt the new luatex syntax.
I'd rather keep this simple as well: insert
\IfFileExists{luatex85.sty}{\usepackage{luatex85}}{}
with every LuaTeX export for the next years to come untill we can be safe
every user has the new version and can start using the new syntax in our
export.
Günter
