Skip to content

# wspr/fontspec

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

# fontspec cannot be loaded after babel any longer #312

Closed
opened this issue Nov 6, 2017 · 2 comments

## Comments

Projects
None yet
2 participants

### ralessi commented Nov 6, 2017

 With the latest versions of both babel and fontspec, this mwe compiled with lualatex: \documentclass{article} \usepackage[english]{babel} \usepackage{fontspec} \begin{document} Hello world. \end{document}  gives me this error: ERROR: LaTeX error: "kernel/command-already-defined" --- TeX said --- ! ! Control sequence \latinencoding already defined. ! ! See the LaTeX3 documentation for further information. ! ! For immediate help type H . !............................................... l.121 \tl_new:N \latinencoding  pointing to l. 121 of fontspec-luatex.sty If fontspec is loaded before babel, the mwe compiles. Are we now supposed to mind the load order of the two packages?
Owner

### wspr commented Nov 6, 2017

 Apologies, this is an oversight. Thanks for letting me know. Until I fix the bug and make a new release, you can work around the issue as follows: \usepackage[english]{babel} \let\latinencoding\relax \usepackage{fontspec} (or revert to the previous version)
Author

### ralessi commented Nov 6, 2017

 Many thanks! I already did \let\latinencoding\relax: everything is now back to normal.

Closed

### wspr closed this in  3ffed8d Nov 9, 2017

to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.