New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Suspicious errors when running babel tests #848

Closed
tkw1536 opened this Issue Jul 9, 2017 · 4 comments

Comments

Projects
None yet
4 participants
@tkw1536
Contributor

tkw1536 commented Jul 9, 2017

Whenever I run the t/81_babel.t tests, I get the following errors:

> perl t/81_babel.t
1..6
ok 1 - use LaTeXML::Core;

Error:undefined:\@nil The token T_CS[\@nil] is not defined.
	at /usr/local/texlive/2017/texmf-dist/tex/generic/babel/babel.sty; line 380 col 7
	Defining it now as <ltx:ERROR/>
	In Core::Stomach[@0x7ff46a6fd7c0] at /usr/local/texlive/2017/texmf-dist/tex/generic/babel/babel.sty; line 380 col 7
	 <= Core::Gullet[@0x7ff46a6fd8e0] <= Core::Definition::Constructor[\usepac... <= Core::Stomach[@0x7ff46a6fd7c0] <= ...
ok 2 - t/babel/french

Error:undefined:\@nil The token T_CS[\@nil] is not defined.
	at /usr/local/texlive/2017/texmf-dist/tex/generic/babel/babel.sty; line 380 col 7
	Defining it now as <ltx:ERROR/>
	In Core::Stomach[@0x7ff46af19860] at /usr/local/texlive/2017/texmf-dist/tex/generic/babel/babel.sty; line 380 col 7
	 <= Core::Gullet[@0x7ff46f286168] <= Core::Definition::Constructor[\usepac... <= Core::Stomach[@0x7ff46af19860] <= ...
ok 3 - t/babel/german

Error:undefined:\@nil The token T_CS[\@nil] is not defined.
	at /usr/local/texlive/2017/texmf-dist/tex/generic/babel/babel.sty; line 380 col 7
	Defining it now as <ltx:ERROR/>
	In Core::Stomach[@0x7ff469c078c0] at /usr/local/texlive/2017/texmf-dist/tex/generic/babel/babel.sty; line 380 col 7
	 <= Core::Gullet[@0x7ff46aecdf90] <= Core::Definition::Constructor[\usepac... <= Core::Stomach[@0x7ff469c078c0] <= ...
ok 4 - t/babel/greek
ok 5 - t/babel/numprints

Error:undefined:\@nil The token T_CS[\@nil] is not defined.
	at /usr/local/texlive/2017/texmf-dist/tex/generic/babel/babel.sty; line 380 col 7
	Defining it now as <ltx:ERROR/>
	In Core::Stomach[@0x7ff471613800] at /usr/local/texlive/2017/texmf-dist/tex/generic/babel/babel.sty; line 380 col 7
	 <= Core::Gullet[@0x7ff471611ad0] <= Core::Definition::Constructor[\usepac... <= Core::Stomach[@0x7ff471613800] <= ...
ok 6 - t/babel/page545

The tests themselves still pass (and thus appear to produce the exact xml required).

I am running the latest latexmlc from master (with dependencies installed via cpanm) along with TexLive 2017. I have been getting these errors both on my MacBook and my archlinux setup.

@swalter62

This comment has been minimized.

swalter62 commented Jul 9, 2017

I get the same error on debian testing. In addition, latexml throws an
Error:undefined:@nil
on a simple test file with the babel package. The output does not appear to be affected, but the error is picked up by my scripts, and is a nuisance.
Here's a minimal test file testme.tex:

\usepackage[english]{babel}
\begin{document}
This is a test.
\end{document}

And here's the output of latexml with no parameters:

latexml (LaTeXML version 0.8.2; revision e581ef5e)
processing started Sun Jul  9 22:25:12 2017

(Digesting TeX testme...
(Loading /usr/local/share/perl/5.24.1/LaTeXML/Package/TeX.pool.ltxml...
(Loading /usr/local/share/perl/5.24.1/LaTeXML/Package/eTeX.pool.ltxml... 0.00 sec)
(Loading /usr/local/share/perl/5.24.1/LaTeXML/Package/pdfTeX.pool.ltxml... 0.01 sec) 0.11 sec)
(Processing content /home/pub/test/testme.tex...
(Loading /usr/local/share/perl/5.24.1/LaTeXML/Package/LaTeX.pool.ltxml... 0.13 sec)
(Loading /usr/local/share/perl/5.24.1/LaTeXML/Package/article.cls.ltxml... 0.01 sec)
(Loading /usr/local/share/perl/5.24.1/LaTeXML/Package/babel.sty.ltxml...
(Processing definitions /usr/share/texlive/texmf-dist/tex/generic/babel/babel.sty...
(Processing definitions /usr/share/texlive/texmf-dist/tex/generic/babel/switch.def... 0.04 sec)
Error:undefined:\@nil The token T_CS[\@nil] is not defined.
	at /usr/share/texlive/texmf-dist/tex/generic/babel/babel.sty; line 380 col 7
	Defining it now as <ltx:ERROR/>
	In Core::Stomach[@0x55b664cff5f8] at /usr/share/texlive/texmf-dist/tex/generic/babel/babel.sty; line 380 col 7
	 <= Core::Gullet[@0x55b6652e3a58] <= Core::Definition::Constructor[\usepac... <= Core::Stomach[@0x55b664cff5f8] <= ...

(Processing definitions /usr/share/texlive/texmf-dist/tex/generic/babel-english/english.ldf...
(Loading /usr/local/share/perl/5.24.1/LaTeXML/Package/babel.def.ltxml...
(Processing definitions /usr/share/texlive/texmf-dist/tex/generic/babel/babel.def...
(Processing definitions /var/lib/texmf/tex/generic/config/language.def... 0.03 sec) 0.51 sec) 0.56 sec) 0.74 sec) 1.23 sec) 1.36 sec) 1.56 sec) 1.69 sec)
(Building...
(Loading compiled schema /usr/local/share/perl/5.24.1/LaTeXML/resources/RelaxNG/LaTeXML.model... 0.01 sec). 0.05 sec)
(Rewriting... 0.00 sec)
(Finalizing... 0.00 sec)
Conversion complete: 1 error; 1 undefined macro[\@nil].
processing finished Sun Jul  9 22:25:13 2017
<?xml version="1.0" encoding="UTF-8"?>
<?latexml searchpaths="/home/pub/test"?>
<?latexml class="article"?>
<?latexml package="babel" options="english"?>
<?latexml RelaxNGSchema="LaTeXML"?>
<document xmlns="http://dlmf.nist.gov/LaTeXML">
  <resource src="LaTeXML.css" type="text/css"/>
  <resource src="ltx-article.css" type="text/css"/>
  <para xml:id="p1">
    <p>This is a test.</p>
  </para>
</document>

I'm guessing this error is due to a change in babel. Am I right, Bruce?

@brucemiller

This comment has been minimized.

Owner

brucemiller commented Jul 10, 2017

@swalter62 , I suspect you are. I'll look into it soon as I get back to a machine.

@brucemiller

This comment has been minimized.

Owner

brucemiller commented Aug 3, 2017

It was revealed by a change to babel.sty, which started using a macro for class options that we hadn't bothered to set. Should work now; thanks for the report!

@brucemiller brucemiller closed this Aug 3, 2017

@swalter62

This comment has been minimized.

swalter62 commented Aug 3, 2017

It does indeed work now. Problem solved, thanks a million Bruce!

@dginev dginev added this to the LaTeXML-0.8.3 milestone Jan 6, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment