On Wed, Mar 16, 2016 at 9:39 PM, Martin Mares wrote:

Hello once again,

after fixing the alignment problem, my compilation now fails a couple of pages later: luatex crashes with SIGFPE when trying to write a PK font.

I do not have a simple test case yet, but I think I see the problem in the source: in source/texk/web2c/luatexdir/font/writet3.w, function writepk(), one call to pdf_printf() divides by newdpi, which can be zero when pk_fixed_dpi is not set.

What is the intention behind dpi vs. newdpi?

I remember something ... I will give it a look. -- luigi

On 3/16/2016 9:39 PM, Martin Mares wrote:

Hello once again,

after fixing the alignment problem, my compilation now fails a couple of pages later: luatex crashes with SIGFPE when trying to write a PK font.

I do not have a simple test case yet, but I think I see the problem in the source: in source/texk/web2c/luatexdir/font/writet3.w, function writepk(), one call to pdf_printf() divides by newdpi, which can be zero when pk_fixed_dpi is not set.

What is the intention behind dpi vs. newdpi?

(By the way, is pk_fixed_dpi documented somewhere?)

that's an experiment for cases where you have a (say) 2400 dpi pk file and don't mind it being used for lower resolutions ... this can be the case when you use a few bitmap chars as drop in for missing ones; it then also permits to distribute just one instance Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------