fonttools VS npm

The tool parent and sibling comment listed allows you to do basic subsetting [1], and generates the formats you need. If you do this more often, it is of course useful to learn how to do this yourself. A commonly used tool is pyftsubset, part of fonttools [2]

[1]: https://fonts.google.com/knowledge/glossary/subsetting

[2]: https://github.com/fonttools/fonttools

I know fontforge doesn't support OTF-SVG, but I'm actually using it for creating OTF-SVG from scratch. Is anyone willing to help me with this issue? https://github.com/fonttools/fonttools/discussions/3229

I'm having this issue and maybe here someone can help me.. https://github.com/fonttools/fonttools/discussions/3229

In short, I draw glyphs in png and use python to build fonts (by https://github.com/fonttools/fonttools ). I agreed on some rules and then everything became simple. No required professional font editer.

If you have FontTools successfully installed, there is also a bundled script that's similar to what justinpenner's code does, without the built-in directories; you can find it at https://github.com/fonttools/fonttools/blob/main/Snippets/layout-features.py

What I like the most is that you can also download google-fonts and convert them automatically. Webfont-Kit-Generator uses fonttools (written in Python), that's pretty cool too.

A drawback to icon fonts is that by default, you are carrying all of the glyphs in an icon font along for the ride. You can mitigate that by using a tool like fonttools to strip out the unused font glyphs.

If you're interested in learning more about how variable fonts work, I can point you to all sorts of tools and other resources. For example, fontTools includes a command line tool called ttx that converts any standard font format (ttf/otf/ttc/otc/woff/woff2) to a human-readable XML text file. You can also inspect variable and static fonts easily with online tools like Wakamai Fondue and Samsa.

If you want to look inside a font file, you can use the ttx command line tool (included with fontTools) to convert binary fonts to human-readable XML format. You can also open them in a font editor like FontForge or Glyphs if you want a GUI, but font editors may not show you everything that's inside the file.

The fact that JSON doesn't support comments is so annoying, and I always thought that Douglas Crockford's rationale for this basically made no sense ("They can be misused!" - like, so what, nearly anything can be misused. So without support for comments e.g. in package.json files I have to do even worse hacky workaround bullshit like "__some_field_comment": "this is my comment"). There is of course jsonc and JSON5 but the fact that it's not supported everywhere means 10 years later we still can't write comments in package.json (there is https://github.com/npm/npm/issues/4482 and about a million related issues).

Things like the sparkline charts on npmjs (e.g. https://www.npmjs.com/package/npm ) are interactive SVGs. I think they're pretty common for data visualizations of all kinds

I actually did a POC 7 years ago about this - https://github.com/tanepiper/steal-ur-stuff

It was reported to npm at the time, but they chose to ignore it - https://github.com/npm/npm/issues/17724

Every time this pops up, I'm reminded of the day that the NPM registry started returning 418 responses.

I remember being at a training course that day and my manager asking me what we could do to fix it because our CI was failing to pull dependencies from NPM.

Trying to explain that NPM was returning a status code intended as an April Fools joke and which was never meant to see the light of production was quite difficult

https://github.com/npm/npm/issues/20791

I should really get around to how I discovered this 6 years ago and still nothing done about it

Whenever something like this comes up I usually have to tap the sign (and the original report)

NPM is not "Node Package Manager". https://www.npmjs.com/package/npm

> which can be overriden with env setting

Support for this is not great. Lots of packages still don't support this properly. My experience matches the 2015 comment https://github.com/npm/npm/issues/775#issuecomment-71294085

> Not sure why "symlinks" would be involved.

If you make your node_modules a symlink, multiple packages will fail. Even if you're not interested in doing that, others are.

> What NPM does is leaps and bounds ahead

Unless you change your node / gyp version. It doesn't really have a concept of runtime version. You can restrict it, but not have two concurrent versions if they conflict.

[email protected] was released in May 2017 and it seems to address many of the issues that Yarn aims to solve. Do keep an eye on it!

I think it's had been supposed to do that since forever. Apart from some bug in npm 5.3. Are you sure your package-lock versions actually conform to the semver ranges in your package.json?