View Issue Details

IDProjectCategoryView StatusLast Update
0000991luatexluatex bugpublic2016-11-25 11:17
Reporterkarlberry Assigned ToHans Hagen  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionno change required 
Platformany (i sippose)OSanyOS Versionany
Product Version1.0.0 
Summary0000991: context+cowfont generates pdf that cannot be read by ghostscript
Descriptionrunning "context cow.tex" on the attached file (it just typesets a Q in the cow font) results in a pdf that gs cannot read. gs cow.pdf reports:
**** Error reading a content stream. The page may be incomplete.
               Output may be incorrect.
and the gs output window is empty. (i don't really care about gs per se, but gs --bbox fails in the same way, thus pdfcrop cannot work, which was a pain.)

whether this is a bug in the cow font, luatex, or ghostscript, i don't know. i tried a variety of gs versions and they all failed. since the cow font is so unusual, i thought i'd report it here first.
Steps To Reproducecontext cow.tex
gs cow.pdf
Additional Information1) this is actually with current context-minimals, luatex version 1.0.0, but your "product version" field does not offer that as an option :).

2) not every use of the cow font results in this error. i have a 12-page document; 3 pages are bad (2, 4, and 12), the rest are fine. (running pdfcrop on the 12-page pdf will report the problematic pages.) i can send that also if you want the additional examples, or maybe the ui here will let me add it to this report after i submit it ...
TagsNo tags attached.

Activities

karlberry

2016-10-20 20:29

reporter  

cow.tex (221 bytes)

karlberry

2016-10-20 20:30

reporter  

cow-12.tex (5,648 bytes)

karlberry

2016-10-20 23:28

reporter   ~0001648

p.s. barbara reports the current version of acrobat professional (not just reader) reports "An error exists on this page. Acrobat may not display
the page correctly.". It provides no other details, but it does lend support to the bug in luatex/cowfont hypothesis, vs. being in ghostscript. nothing's for sure, of course. hope you can investigate ... tx.

Taco

2016-10-21 10:39

administrator   ~0001649

The page stream looks odd on my side as well:

9 0 obj
<<
  /Length 199
>>
stream
0 g 0 G
0 g 0 G
q
/Span << /ActualText <feff0051> >> BDC [<feff>] TJ
1.000000 g
BT
/F5 11.955168 Tf 1 0 0 1 70.867 701.98286 Tm [<0145>]TJ
0.000000 g
1 0 0 1 70.867 701.98286 Tm [<0030>]TJ
ET
EMC
Q
endstream

It seems GS complains about the [<feff>] TJ: if I replace that bit by space characters, GS is happy

Hans Hagen

2016-10-21 15:32

manager   ~0001650

I came to the same conclusion and removed that hack. We introduced that when we were testing cut/paste in viewers other than acrobat. So, instead of that hack, we now just wait till the open source viewers get better.

Btw, I will look onto the "/F5 flushing earlier and not interfering with literals" case later (as I didn't want to mess with the vf backend around 1.0 release).

Hans Hagen

2016-11-25 11:17

manager   ~0001657

i'll add a bit more control over virtual command flushing

Hans Hagen

2016-11-25 11:17

manager   ~0001658

currently handles in context

Issue History

Date Modified Username Field Change
2016-10-20 20:29 karlberry New Issue
2016-10-20 20:29 karlberry File Added: cow.tex
2016-10-20 20:30 karlberry File Added: cow-12.tex
2016-10-20 23:28 karlberry Note Added: 0001648
2016-10-21 10:39 Taco Note Added: 0001649
2016-10-21 10:41 Taco Product Version 0.87.0 => 1.0.0
2016-10-21 15:32 Hans Hagen Note Added: 0001650
2016-11-25 11:17 Hans Hagen Note Added: 0001657
2016-11-25 11:17 Hans Hagen Note Added: 0001658
2016-11-25 11:17 Hans Hagen Status new => closed
2016-11-25 11:17 Hans Hagen Assigned To => Hans Hagen
2016-11-25 11:17 Hans Hagen Resolution open => no change required