3 Commits

Author	SHA1	Message	Date
ylemkimon	ea409eaf1d	fix(fonts): update fonts dependencies (#2866) ... * fix(fonts): update fonts dependencies * chore(fonts): fix buildMetrics for Python 3 * fix(fonts): update fonts * test: update screenshots * docs: update reference to katex-fonts * chore: use Python 3 * fix(fonts): update fonts * test: update screenshots * Use explicit path * Command-line arguments aren't actually supported * Small buildMetrics fixes * Add build:{fonts,metrics} script * Lock versions of font-related dependencies * Install minimal texlive * Install fontforge Co-authored-by: Erik Demaine <edemaine@mit.edu>	2021-08-29 07:06:42 +09:00
ylemkimon	3dd1ed45b4	Run screenshotter using Chrome 83 and Firefox 76 (#2304) ... * Run screenshotter using Chrome 83 and Firefox 76 * Update screenshots * Update NegativeSpace-chrome screenshot The new screenshot is correct as per #1194. * Update Units-chrome screenshot The new screenshot is correct as per #732 and compared to Firefox. * Update screenshots	2020-07-14 08:48:55 -07:00
Erik Demaine	4801ab875a	Support for top-level \newline and \\ in inline math (#1298) ... * Support for top-level \newline and \\ in inline math This was a little tricky because `\\` was defined as an endOfExpression. Instead made `\\` a termination specific to an array environment. Outside an array environment, buildHTML handles the `cr` object, resulting in a `.newline` class. Currently this turns into a `display: block` (with appropriate vertical spacing) only in inline math, matching LaTeX. * Simplify code * Fix Jest errors * NewLine screenshot test * Bug fix: \\ only works at top level of inline * Add \newline and \cr to test * Switch test to pmatrix * Add vertical space test * Add \\ vs. \newline tests * Fix flow errors * Add \cr test * Add documentation for \\ at top level * Comment out newRow * Fix commenting out	2018-05-13 09:58:24 -04:00