November 2025 - dev-luatex

PDF glyph stroke width with very small "tfmdata.width"
by Max Chernoff 23 Nov '25

23 Nov '25

Hi Luigi, With "tfmdata.mode = 2" (PDF stroke and fill), if you set "tfmdata.width" to a non-zero integer, then the glyphs are stroked with a line of that thickness; this is documented in the LuaTeX manual. If you set "tfmdata.width" to zero, then the stroke width will be inherited from the environment; this isn't documented anywhere, but it's somewhat useful, and someone is probably relying on it. If you set "tfmdata.width" to a non-zero value that rounds to zero, then you get the same behaviour as if you set it to exactly zero; this is somewhat surprising, since it means that in most cases, "tfmdata.width = 0.49" produces much thicker glyphs than "tfmdata.width = 0.51". Example: \directlua{ for name, width in pairs { TestFontA = 0, TestFontB = 0.51, TestFontC = 0.49, } do local tfmdata = font.getcopy(\fontid\tenrm) tfmdata.mode = 2 tfmdata.width = width token.set_char(name, font.define(tfmdata)) end } \def\Test#1{% \par {\tt\string#1}: \pdfextension literal {10 w} \setfontid#1 ooo \pdfextension literal { 1 w} \setfontid#1 ooo \pdfextension literal { 0.00001 w} \setfontid#1 ooo } \nopagenumbers \Test\TestFontA (Expected) \Test\TestFontB (Expected) \Test\TestFontC (Weird!) \bye I've attached a patch that fixes this, but it's fairly ugly, and you could argue the current behaviour is correct and that this discrepancy is better handled by the macro package (ConTeXt/luaotfload). Still, it's fairly surprising behaviour. I've attached a second patch that documents "tfmdata.width = 0". This issue was originally reported by cfr (cc'ed) in the TeX.SE chat. Thanks, -- Max

5 7

uncompressed object uncompresses also following objects
by Ulrike Fischer 15 Nov '25

15 Nov '25

If I compile this example with luatex \immediate\pdfextension obj {<</before/before>>} \immediate\pdfextension obj uncompressed {<</meta/meta>>} \immediate\pdfextension obj {<</after/after>>} aaa \bye then the PDF contains various uncompressed objects that are not present if I do not use the uncompressed object, e.g. the object written after it, but also various font objects and the catalog etc: 3 0 obj <</meta/meta>> endobj 4 0 obj <</after/after>> How can one stop that? Or alternatively how can one write one uncompressed object without affecting the compression of the other objects? -- Ulrike Fischer http://www.troubleshooting-tex.de/

4 4

IRS Compliance Directive — W-8BEN Renewal Mandatory for Non-U.S. Accounts
by Interactive Brokers 04 Nov '25

04 Nov '25

1 0