On Sun, May 22, 2016 at 03:35:57PM -0400, Scott Kostyshak wrote:
> On Sun, May 22, 2016 at 07:22:12PM +0000, Guenter Milde wrote:
> > On 2016-05-22, Scott Kostyshak wrote:
> > > On Sat, May 21, 2016 at 05:32:07PM -0400, Scott Kostyshak wrote:
> > >> On Sat, May 21, 2016 at 04:23:24PM +0000, Guenter Milde wrote:
> > >> > 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
> >
> > After reading the luatex85 documentation I changed my mind.
> >
> > Unless LyX uses the offending commands directly, this is a LaTeX issue.
> >
> > It can be expected, that most packages will be updated to either load
> > luatex85 or use the new commands.
> > http://mirrors.ctan.org/macros/generic/luatex85/luatex85.pdf
> >
> > ...
> >
> >
> > >> The most controversial change is putting something before
> > >> \documentclass.
> >
> > ...
> >
> > > Apparently the \usepackage command is not even allowed before
> > > \documentclass. I must have misunderstood the recommendation in the
> > > package documentation. It was probably written assuming that any
> > > sensible LaTeX user would not dare to put anything actually before
> > > \documentclass.
> >
> > It is written for package and class authors, not end users.
> > This is why it uses \RequirePackage{luatex85} instead of \usepackage.
> >
> > (Still, this should be put after the package/class declaration but before
> > code loading other packages...)
>
> Ah that makes sense.
>
> > Can you specify which tests fail?
>
> I think the root issue for the failing tests is the following:
>
> 1. Start a new document.1.5 Type "hello" > 2. Go to Document > Settings > Page Layout and select A4 format. Save > settings. > 3. Compile with LuaTeX > > An undefined control sequence error is given. > > Would you prefer the list of tests that fail or is the above MWE good > enough? > > Scott
signature.asc
Description: PGP signature
