suzanne.soy/KaTeX
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
b94fc6534d
KaTeX/metrics
History
Kevin Barabash 14a58adb90 Migrate to eslint 
Summary
We'd like contributors to use the same linter and lint rules that we use
internally.  This diff swaps out eslint for jshint and fixes all lint failures
except for the max-len failures in the test suites.

Test Plan:
- ka-lint src
- make lint
- make test

Reviewers: emily
2015-12-01 10:02:08 -08:00
..
extract_tfms.py Add a build step to generate extended metrics that additionally contain glyph widths 2015-10-16 14:31:08 -07:00
extract_ttfs.py Add a build step to generate extended metrics that additionally contain glyph widths 2015-10-16 14:31:08 -07:00
format_json.py Migrate to eslint 2015-12-01 10:02:08 -08:00
mapping.pl Adds font metrics to support font commands. 2015-07-10 21:50:04 -06:00
parse_tfm.py Adds font metrics to support font commands. 2015-07-10 21:50:04 -06:00
README.md Switch from fontforge to fonttools 2015-07-10 14:32:02 +02:00

README.md

How to generate new metrics

There are several requirements for generating the metrics used by KaTeX.

  • You need to have an installation of TeX which supports kpathsea. You can check this by running tex --version, and seeing if it has a line that looks like

    kpathsea version 6.2.0

  • You need the JSON module for perl. You can install this either from CPAN (possibly using the cpan command line tool) or with your package manager.

  • You need the python module fonttools. You can install this either from PyPi (using easy_install or pip) or with your package manager.

Once you have these things, run

make metrics

which should generate new metrics and place them into fontMetricsData.json. You're done!