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

Renderer=HarfBuzz is XeTeX. #430

Open
kberry opened this issue Aug 30, 2020 · 3 comments
Open

Renderer=HarfBuzz is XeTeX. #430

kberry opened this issue Aug 30, 2020 · 3 comments

Comments

@kberry
Copy link

kberry commented Aug 30, 2020

I'd like to run a document (tugboat article) with both xelatex and lualatex. With LuaLaTeX, Renderer=HarfBuzz is required to use hb, as in:

\newfontfamily\devanagarifont[Script=Devanagari,Renderer=HarfBuzz]
  {NotoSerifDevanagari-Regular.ttf}

when run with xelatex, this generates a warning:

Package fontspec Warning: Ignored LuaTeX-only feature:
(fontspec)                'Renderer=Full/Basic/Node/Base/HarfBuzz'.

Ok, it's just a warning, but still, it's rather irritating. XeTeX is already rendering with HarfBuzz. So it would be nice if this particular setting would be silently accepted, instead of complained about. I know it's probably not simple though :(. Fine if you want to call it "wontfix" : ), just thought i'd suggest it. thanks.

@Davislor
Copy link

Davislor commented Dec 23, 2020

You can write

\usepackage{iftex}

\ifluahbtex
  \defaultfontfeatures{ Renderer=HarfBuzz, Scale=MatchLowercase, Ligatures=TeX }
\else
  \defaultfontfeatures{ Scale=MatchLowercase, Ligatures=TeX }
\fi

Or


\usepackage{iftex}

\ifluahbtex
   \defaultfontfeatures[NotoSerifDevanagari]{Renderer=HarfBuzz}
\fi

\newfontfamily\devanagarifont{NotoSerifDevanagari}[
  Scale = MatchUppercase,
  Script = Devanagari,
  UprightFont = *-Regular,
  BoldFont = *-Bold,
  Extension = .ttf ]

@kberry
Copy link
Author

kberry commented Dec 23, 2020

Yes, thanks. I know. The point of my message is that with xetex, since the renderer is always harfbuzz, it would be nice to silently accept that setting instead of warning about Renderer=harfbuzz. Then no conditional in the source is needed to avoid warnings when harfbuzz is desired for both engines.

However, I have my doubts that Will is ever going to have time to think about this, at least for the next N years while the kids gets older. And that's ok :).

@Davislor
Copy link

It’s a good suggestion. I usually just live with the warning, but it’s better not to have spurious warnings.

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

2 participants