Open saward opened 4 years ago
I am not sure what's going on, but I have two guesses:
1) does it have something to do with the "[wght]" on the filename? In other words, does it work if you rename the file to not use that bracket notation that we use to indicate the variable font axis?
2) was quicksand recently updated from a set of static fonts into a variable font? If so, maybe LaTeX may be having trouble parsing a variable font? I am not sure what's the level of support for variable fonts in LaTeX nowadays.
Renaming and running fc-cache -f
results in the same error:
xdvipdfmx:fatal: Invalid TTC index (not TTC font): /usr/local/share/fonts/Quicksand.ttf
I did look through the commit history for this repo, and saw that this font was added since my last build. I strongly suspect that the last time I fetched this repo was before these commits:
Apart from that, I don't understand enough about your second guess to remark intelligently.
yeah... At #2050 I see: "In 2019, Mirko Velimirovic converted the family into a variable font."
I think LaTeX does not deal well with variable fonts yet.
I'm now also seeing this for another font I have been using:
xdvipdfmx:fatal: Invalid TTC index (not TTC font): /usr/local/share/fonts/Inconsolata[wdth,wght].ttf
It happened to me the same with EBGaramond[wght].ttf... :( Now I can't use it in my XeLaTeX documents :(
Hi,
I've been using these fonts as part of a base docker image creating latex PDF's. It's been working fine with the last update about 9 months ago, but I recently updated the base docker image, which pulled the very latest Google fonts. I'm now having an issue building the latex file. The relevant error is
xdvipdfmx:fatal: Invalid TTC index (not TTC font): /usr/local/share/fonts/Quicksand[wght].ttf
. That error in some context:Removing this file from my system enables me to build the PDF without issue.
I don't understand the details of fonts well enough to understand who or what is at fault. I thought I'd post this here in case someone can point me in the right direction -- is this an issue with this ttf file, or something else?
Thanks!