Using XeLaTeX in TeX Live 2015 seems to break classic LaTeX quotations (or force unicode entry, depending on how one looks at it).


TeX Live 2014

fontspec.sty 2015/03/14 v2.4c Font selection for XeLaTeX and LuaLaTeX

``something quoted'' appears as “something quoted”

TeX Live 2015

fontspec.sty 2016/01/30 v2.5 Font selection for XeLaTeX and LuaLaTeX

``something quoted'' appears as ``something quoted''.

Is this normal? I saw this question: Left and right quotation marks aren't correct when using fontspec, but nothing has changed in my source code. Adding Ligatures=TeX as a parameter to \setmainfont seems to fix the issue, but why just in TeX Live 2015?

\setmainfont{DejaVu Sans}
``check it out''
“check it out”

Release Notes for fontspec


v2.5a (2016/02/01) "bugs fixed"

  • Rather embarrassing bug fix! (unicode-math was broken.)
  • Remember to add the fontspec.cfg file to the distribution.
  • Remove +trep from Ligatures=TeX (no longer necessary).
  • Add some basic tests using l3build; more to come.
  • Simplify some internal Lua code and package loading code.

v2.5 (2016/01/30) "TL2016 re­lease"

  • Provide a new Unicode font encoding ("TU") to replace EU1/EU2 and xunicode. If this causes problems, load fontspec with the [euenc] option to revert to the old behaviour.
  • New command \emfontdeclare for defining font shapes when arbitrarily nesting the \emph command.
  • Allow slanted small caps and better internal methods for "combining" font shapes; this fixes a few bugs.
  • Incorporate "new" font script tags for Indic fonts. E.g., when selecting Script=Bengali, fontspec will first query the font for the bng2 OpenType script, and if not found select beng.
  • Restrict some font features from being able to be used within \addfontfeatures that were causing some font-loading confusion.
  • Fixed behaviour in which \baselineskip and \f@size would (possibly) change values after loading the packge.
  • Remove copy of fixltx2e's code for footnote symbols; handled by LaTeX2e now.
  • Deprecate ExternalLocation for the simpler (and identical) Path option.
  • Improvement to some warnings/info messages.
  • Improve structure of code.

closed as off-topic by egreg, Jonathan Komar, user13907, Jesse, ChrisS Feb 5 '16 at 10:29

  • This question does not fall within the scope of TeX, LaTeX or related typesetting systems as defined in the help center.
If this question can be reworded to fit the rules in the help center, please edit the question.

  • I get exactly the same for the two lines with an up-to-date TL 2015. What fonts are included in your pdf? It should be LMRoman10-Regular-Identity-H CID Type 0C – user2478 Feb 5 '16 at 7:03
  • 1
    Version 2.5 forgot to add fontspec.cfg, where Ligatures=TeX is specified as default feature. See chat.stackexchange.com/transcript/41?m=27244271#27244271 – egreg Feb 5 '16 at 9:49
  • 4
    I'm voting to close this question as off-topic because this is about a bug that has been fixed in a release issued before the question was made – egreg Feb 5 '16 at 9:50
  • 2
    @egreg Ok, I voted to close it. That designation "off-topic" still needs to be changed to something like "bug already fixed". The question itself is clearly on topic. What i mean is that it was deemed off-topic after the fact. A truly off-topic question will be off-topic at all points in time. – Jonathan Komar Feb 5 '16 at 9:59
  • 1
    For anybody who is struggling with figuring this out, it is very "on topic". – A Feldman Feb 5 '16 at 14:51

fontspec v2.5a (2016/02/01) "bugs fixed" solves the issue.

  • Version 2.5 did not include fontspec.cfg where Ligatures=TeX was specified as a default feature.

Ligatures=TeX is a default option for fonts loaded by fontspec normally. I therefore did not specify it as a parameter in my documents. In TeX Live 2015, it accidentally became non-default. This meant that LaTeX was not creating ligatures out of the character combinations `` and ''.

Not the answer you're looking for? Browse other questions tagged or ask your own question.