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.

Sign up for GitHub

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

Jump to bottom

postscriptname null in some version of fontkit #336

Open
alecjacobson opened this issue Jun 7, 2024 · 2 comments · May be fixed by #337
Open

postscriptname null in some version of fontkit #336

alecjacobson opened this issue Jun 7, 2024 · 2 comments · May be fixed by #337

Comments

@alecjacobson
Copy link

I admit I'm lost in my node dependencies, but I have some configuration where this program works correctly:

var fontkit = require('fontkit');

// open a font synchronously from arg
var font = fontkit.openSync('STRRETCH-SANS-FREE-dqme76.otf');
console.log(font.postscriptName);

and outputs:

STRRETCHSANSFREERegular

But then in a different node installation directory this same program will just output:

null

I liked the behavior that I could reliably get the postscriptname from the font I loaded from file. Did this feature change?
@alecjacobson
Copy link
Author

Could be related to #333

@alecjacobson
Copy link
Author

also, fwiw, both of my installs are supposedly using 2.0.2 so it's really weird that they're producing different behavior. Maybe there's an issue with dependencies?

If I downgrade to 1.9.0 I don't seem to have a problem. But already 2.0.0 produced null in one of the installations

@alecjacobson alecjacobson linked a pull request Jun 7, 2024 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Downgrades and locks to restructure 3.0.0 alecjacobson/fontkit
1 participant
@alecjacobson