-
Notifications
You must be signed in to change notification settings - Fork 64
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Tried to keep the css together but it doesn't feel super logically grouped so I wound up rearranging everything. Sorry future git-blamer. Units of measurements are all over the place, here's what defines them: - mm for page-related units - pt for text-related units - em for horizontal units - ex for vertical units Highly specific rules come from a loyalty to the Ecma specification template first, previous years' standards second. There should be no changes that impact screen rendering; changes to the primary stylesheet come from inline styles that existed in both ECMA-262 and ECMA-402. - Remove print css from Spec file - Remove styles from inline assets test - Add publishing instructions - Small tweaks to allow ecmarkup to generate print-friendly PDFs beyond just 262 & 402 - Use font-face to make sure all the characters are rendered as we wish, including 0 with slash, double-stroke F, and infinity - Dynamically generate PDF covers based on frontmatter (TODO: Ecma-endorsed proposal cover?) - Make sure year is being properly inserted into footers
- Loading branch information
Showing
9 changed files
with
1,656 additions
and
311 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,28 @@ | ||
# Generating a PDF from ecmarkup | ||
|
||
In order to produce a PDF, the front matter `title`, `shortname`, `version`, and `date` are **mandatory**. If generating a final annual edition, date should reflect the date of the Ecma GA which will ratify the Standard. For example: | ||
|
||
``` | ||
title: ECMAScript® 2024 Language Specification | ||
shortname: ECMA-262 | ||
version: 15th Edition | ||
date: 2024-06-25 | ||
``` | ||
|
||
To generate markup for use in PDF conversion, make sure to include the options `--assets`, `--assets-dir`, and `--old-toc`. If you have images and styles to include, make sure to move them into your assets directory before running `ecmarkup`. For example: | ||
|
||
```shell | ||
mkdir -p out && | ||
mv images out && | ||
mv print.css out && | ||
ecmarkup --assets external --assets-dir out --old-toc spec.html out/index.html | ||
``` | ||
|
||
Then, from your spec's working directory, run [`prince`](https://www.princexml.com/) to generate your PDF. | ||
|
||
```shell | ||
cd path/to/spec | ||
prince --script ./node_modules/ecmarkup/js/print.js out/index.html -o path/to/output.pdf | ||
``` | ||
|
||
This has been extensively tested with Prince 15. Earlier and later editions not guaranteed. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.