npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

character-map

v1.1.0

Published

A simple command line tool for dumping a UTF-8 string of characters supported by a font file

Downloads

14

Readme

character-map

npm version

A simple command line tool for dumping a UTF-8 string of characters supported by a font file.

Motivation

Unicode fonts are usually too large to be embedded as webfont: subsetting is necessary to get them into a reasonable size, especially for CJK fonts.

But which ones do you subset to ensure your design look consistent? There are 2 major approaches:

  • Dynamic subsetting: using javascript and server-side api to generate a dynamic subset of your font, covering all characters on your webpage.
  • Static subsetting: prepare a list common characters, subset them manually, and use such font only for certain elements on webpage.

I prefer the latter approach, because it's a lot easier to optimize and has less of an impact to performance.

And Apple agrees, their sites for China Mainland, Hong Kong and Japan all use this approach.

But I wonder what characters they pick for their CJK subsets?

character-map to the rescue!

Install

npm install character-map -g

Usage

TrueType, OpenType, WOFF v1 files are supported at the moment.

$ character-map -f my.ttf > map.txt

map.txt will contain a list of characters found in the font. Now you can use this result with a subsetting tool like fontmin.

$ fontmin -t `cat map.txt` other.ttf > subset.ttf

Of course you can verify the result with character-map again.

License

MIT

Acknowledgement

Inspired by CharacterMap and uses opentype.js.