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

Fonts used in test files #465

Closed
zauguin opened this issue May 21, 2022 · 3 comments
Closed

Fonts used in test files #465

zauguin opened this issue May 21, 2022 · 3 comments

Comments

@zauguin
Copy link
Member

zauguin commented May 21, 2022

fontspec's tests use a bunch of fonts which are either not part of a typical TeX Live installation and sometimes also commercial and therefore not easily available on many systems.

This makes development and especially testing much harder on systems without these fonts and also makes it impossible to automatically run the tests e.g. using GitHub Actions or similar.

In particular this currently affects (on my system at least) the following fonts:

Free fonts:

  • NotoSansCJK-Regular.ttc used in fontload-ttc.lvt
  • Vollkorn-Regular.otf used in luatex-subs.lvt
  • STIX2Text-Regular.otf used in script-lang-trk (STIX2 is part of TeX Live but under the name STIXTwoText-Regular.otf)

Non-free fonts:

  • TimesLTStd with the font files TimesLTStd-Roman.otf / TimesTenLTStd-Roman.otf / TimesTenLTStd-Bold.otf / TimesLTStd-Bold.otf used in fontload-onesize-nosc.lvt
  • CODE2000.TTF used in xetex-mapping-lig.lvt

I would suggest to rename STIX2Text-Regular.otf to STIXTwoText-Regular.otf and add NotoSansCJK-Regular.ttc and Vollkorn-Regular.otf as support files. Which would leave the two non free fonts. Is there some specific reason why these fonts have to be tested or can they be substituted with other fonts?

@wspr
Copy link
Collaborator

wspr commented May 23, 2022

Sorry, I probably forgot to document how I do this. By checking out this repo and running install.sh you should be okay:

https://github.com/wspr/fontspec-test-fonts

I no longer specifically recall the licensing status of the non-free fonts, but I wouldn't have included them if I knew for sure they shouldn't be included (i.e., I'm happy to ditch them if need be, would definitely prefer to use freely available fonts for testing).

The Times font is a little unique because it is missing small caps in some shapes but not others — it showed up an edge case some time back.

The CODE2000 font just has a really good repertoire of glyphs, so it should be easy enough nowadays to replace it with something like Noto which I suspect covers the code points I needed/wanted for that mapping test.

@zauguin
Copy link
Member Author

zauguin commented May 23, 2022

Thanks, fontspec-test-fonts definitely solves my immediate issues except for the STIX2/STIXTwo thing. After looking into it a bit more the STIXTwo name is also used by the official upstream, so I'll create a PR to change that.

The CODE2000 font just has a really good repertoire of glyphs, so it should be easy enough nowadays to replace it with something like Noto which I suspect covers the code points I needed/wanted for that mapping test.

Well, Noto at least has all kinds of glyphs but splits them over different fonts, so if the test requires them to be in the same font it might be problematic. I can take a closer look if it can be changed when I have some time.

@wspr
Copy link
Collaborator

wspr commented Apr 20, 2024

Coming back to this, do you think we should just add the fonts we need to a (sub)folder of the test suite in the main repository? I don't exactly remember why I didn't go that way originally... perhaps to keep the repo file size small(er)

@wspr wspr closed this as completed Apr 27, 2024
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