Nico Weber
Nico Weber
https://adobe-type-tools.github.io/font-tech-notes/pdfs/5177.Type2.pdf says "The behavior of undefined operators is unspecified." but https://learn.microsoft.com/en-us/typography/opentype/spec/cff2 says "When an unrecognized operator is encountered, it is ignored and the stack is cleared." Some type 0 CIDFontType0C...
PDF files are already laid out, kerned, etc. The data in various opentype tables isn't necessary, and some of them even contain invalid data. Add a way to opt in...
Before, we used to reject profiles where the creation datetime was invalid per spec. But invalid dates happen in practice (most commonly, all fields set to 0). They don't affect...
I said I'd look into unifying Filter::decode_ascii_hex() and Parser::parse_hex_string() at some point somewhere iirc. This is a small step towards that.
Non-CID-keyed fonts in PDFs have 8-bit codepoints which are mapped from bytes to character names via encoding. TrueType fonts don't index glyphs by name (Type1 fonts do), so the fix...
...and for fallback fonts too. We use Liberation Sans (a truetype font) for standard and fallback fonts. So we should use the standard PDF algorithm for mapping bytes to truetype...
``` Stacks: 0 crashes (0.0%) 0 distinct crash stacks ``` \o/ The type1 fonts crash triggered in a few places I hit in Real Life (mentioned in that commit's description).
Turns out there's a spec that goes with the table. The big change here is that we can now map `uni1234` to 0x1234 and `u123456` to 0x123456. The parts where...