Bug 54936 - Syntax Warning (...): Mismatched EMC operator
Summary: Syntax Warning (...): Mismatched EMC operator
Status: RESOLVED INVALID
Alias: None
Product: poppler
Classification: Unclassified
Component: general (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: poppler-bugs
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-09-14 17:03 UTC by Germán Poo-Caamaño
Modified: 2014-02-18 23:38 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
PDF test case (58.21 KB, application/pdf)
2012-09-14 17:03 UTC, Germán Poo-Caamaño
Details

Description Germán Poo-Caamaño 2012-09-14 17:03:36 UTC
Created attachment 67177 [details]
PDF test case

This was reported in GNOME Bugzilla (evince), however, this bug belong to
poppler. I can reproduce it with poppler-glib-demo, when it renders the pdf. 

I tried with master (b72c02d1a2e), from Sep 13, 2012.

The warnings I get are:
Syntax Warning (579): Mismatched EMC operator
Syntax Warning (2031): Mismatched EMC operator
Syntax Warning (2469): Mismatched EMC operator
Syntax Warning (3593): Mismatched EMC operator
Syntax Warning (579): Mismatched EMC operator

It might be a problem with the PDF.  I can trigger this one, when I try
to render from the second page.

FWIW, the document has POPPLER_ACTION_JAVASCRIPT.

The report in GNOME is:
https://bugzilla.gnome.org/show_bug.cgi?id=598789
Comment 1 Albert Astals Cid 2012-09-15 18:54:20 UTC
This is kind of a "no bug". The pages have an "End Marked Content" as first command of the page, hence the bug, yes, the warning might go away if/when we support Javascript if the javascript is adding some crap at the beginning of tha page (that it seems like it but to be honest i don't feel like reading all that javascript code).

So to be honest this bug should be closed, but i'll let you reporter decide if you want to keep it around until someone implements javascript support or not


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.