Skip to content
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

Some problems with fontspec and xelatex under windows #106

Closed
maser111 opened this issue Dec 14, 2018 · 2 comments
Closed

Some problems with fontspec and xelatex under windows #106

maser111 opened this issue Dec 14, 2018 · 2 comments

Comments

@maser111
Copy link

I'm using EB Garamond on Windows with MikTeX 2.9 and fontspec with xelatex. I've updated the package downloaded with MikTex (package of 5 Dec 2018). Before the update, the output have a well rendered font with oldstyle numbers and Q.long by default. After the update, the font seems the default Garamond by windows.

This is my short test.

\documentclass{book}

%\usepackage[english,italian]{babel}
\usepackage[utf8]{inputenc}

\usepackage{fontspec}
\setmainfont{EB Garamond}

\usepackage{lipsum}

%%%% STARTING DOCUMENT

\begin{document}

\chapter{Lorem Ipsum}

0123456789 Qui Pro Quo.\par

\lipsum[1]\par
\lipsum[2]\par
\lipsum[3]\par
\lipsum[4]\par

\end{document}

What I'm doing wrong?

@maser111
Copy link
Author

I have recreated the test file under a linux box (test - ok.pdf) and the file produced after the update on windows (test - not ok.pdf)

test - not ok.pdf
test - ok.pdf

@vronizor
Copy link

vronizor commented Apr 21, 2020

The long Q is located within a different stylistic set (ss) of the OpenType features, specifically in ss6. You can go through the fonts feature using FontDrop. Just drag/drop the EBGaramond-Regular.otf file there and go to the OT tab to see all the features of the fonts.

Going back to your example, changing the setmainfont options did it for me:

\setmainfont{EB Garamond}[Numbers=OldStyle, StylisticSet=6]

See section 3.1.10 and 3.1.13 on page 42 and 45 of the fontspec manual.

@georgd georgd closed this as completed Mar 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants