Bug 692629 - glyph index c0000000 out of range
Summary: glyph index c0000000 out of range
Status: RESOLVED FIXED
Alias: None
Product: GhostPCL
Classification: Unclassified
Component: PDF Writer (show other bugs)
Version: 9.04
Hardware: All Linux
: P4 normal
Assignee: Ken Sharp
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-10-25 05:31 UTC by Hans-Josef Mauve
Modified: 2012-03-01 11:09 UTC (History)
1 user (show)

See Also:
Customer:
Word Size: ---


Attachments
Input PCL file for the conversion (214.14 KB, application/pcl)
2011-10-25 05:31 UTC, Hans-Josef Mauve
Details
PDF output created by pcl6 version 8.70 (part of the text missing) (140.35 KB, application/pdf)
2011-10-25 05:33 UTC, Hans-Josef Mauve
Details
pcl source (2.54 KB, application/octet-stream)
2011-11-01 13:17 UTC, kginbg
Details
proposed patch (907 bytes, patch)
2012-02-28 10:05 UTC, Ken Sharp
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Hans-Josef Mauve 2011-10-25 05:31:38 UTC
Created attachment 8043 [details]
Input PCL file for the conversion

The command
pcl6 -dNOPAUSE -sDEVICE=pdfwrite -sOutputFile=delivery.pdf delivery.pcl
results in the error message "glyph index c0000000 out of range"

When I try the same with an older version of pcl6 (8.70) there is no error message, but the resulting pdf is incomplete (a part of the text is missing).
Comment 1 Hans-Josef Mauve 2011-10-25 05:33:10 UTC
Created attachment 8044 [details]
PDF output created by pcl6 version 8.70 (part of the text missing)
Comment 2 Ken Sharp 2011-10-25 07:06:46 UTC
(In reply to comment #0)
 
> The command
> pcl6 -dNOPAUSE -sDEVICE=pdfwrite -sOutputFile=delivery.pdf delivery.pcl
> results in the error message "glyph index c0000000 out of range"

This is a warning, not an error.

 
> When I try the same with an older version of pcl6 (8.70) there is no error
> message, but the resulting pdf is incomplete (a part of the text is missing).

So you are complaining that the current code is better ?
Comment 3 Hans-Josef Mauve 2011-10-25 23:39:59 UTC
Maybe my description of the problem wasn't complete:

The result of the command is not ONLY the error message / warning, but ALSO an incomplete PDF with some of the text missing.

Sorry for not making this point clear in the first run.



P.S. The answer I received could be interpreted as if you are not seriously interested in dealing with this problem:
- Even if the message is only a warning, wouldn't it be worth to find out if there is something wrong?
- A comment like "So you are complaining that the current code is better ?" might be a reasonable question, if it is asked as question. It would then point out that there is a misunderstanding. But as the bug was closed together with adding this reply, the question wasn't asked, and all that's left is a comment that might indicate that the other person is silly (please note that I intentionally used a very gentle wording for this to avoid any escalation of this matter).

If you are not interested in dealing with this bug, please let me know. In this case I would be happy to stop wasting your (and my) time.
Comment 4 Ken Sharp 2011-10-26 07:12:54 UTC
(In reply to comment #3)
> Maybe my description of the problem wasn't complete:
> 
> The result of the command is not ONLY the error message / warning, but ALSO an
> incomplete PDF with some of the text missing.

That certainly wasn't clear to me, your original post seemed to state that you got a warning which wasn't present in an earlier version, but the *earlier* version produced missing output. The attachment says it was produced by 8.70, not 9.04, and states that some of the text is missing.

The implication being that the current version does not produce incomplete output, but does issue a warning.


> P.S. The answer I received could be interpreted as if you are not seriously
> interested in dealing with this problem:
> - Even if the message is only a warning, wouldn't it be worth to find out if
> there is something wrong?

This is a common warning from the PCL interpreter, in fact so common that its being removed.

Can you please indicate whether the problem is missing content in the PDF file produced by the current or earlier version, and what content is in fact missing ?
Comment 5 Hans-Josef Mauve 2011-10-26 21:42:07 UTC
(In reply to comment #4)
> (In reply to comment #3)
> > Maybe my description of the problem wasn't complete:
> > 
> > The result of the command is not ONLY the error message / warning, but ALSO an
> > incomplete PDF with some of the text missing.
> 
> That certainly wasn't clear to me, your original post seemed to state that you
> got a warning which wasn't present in an earlier version, but the *earlier*
> version produced missing output. The attachment says it was produced by 8.70,
> not 9.04, and states that some of the text is missing.
> 
> The implication being that the current version does not produce incomplete
> output, but does issue a warning.
> 
> 
> > P.S. The answer I received could be interpreted as if you are not seriously
> > interested in dealing with this problem:
> > - Even if the message is only a warning, wouldn't it be worth to find out if
> > there is something wrong?
> 
> This is a common warning from the PCL interpreter, in fact so common that its
> being removed.
> 
> Can you please indicate whether the problem is missing content in the PDF file
> produced by the current or earlier version, and what content is in fact missing
> ?

The problem is the missing content in the PDF file - this occurs in both versions.

Missing content:
The text in the middle of the document should be:
 BUTCH12BL           Butchers 12pack Bloss                     100   80
                                                              
                      Please despatch this order when         
                      Customer request                   
                                                              
                      FPEC PALLET x 5                         

In the PDF file the text is:
 BUTCH12BL           Butchers 12pack Bloss                     100
Comment 6 kginbg 2011-11-01 13:17:33 UTC
Created attachment 8056 [details]
pcl source
Comment 7 kginbg 2011-11-01 13:25:41 UTC
I've got the same problem. After compiling 9.04 on Debian squeeze

    pcl6 -sDEVICE=pdfwrite -sOutputFile=klemens.pdf klemens.pcl

yields

    glyph index c0000000 out of range.

The resulting klemens.pdf contains only a few preliminaries, but none
of the contents of the pcl-source. Trying to open it with the filebrowser
results in an error message, that the pdf is damaged. Source klemens.pcl
I've just posted before. Could you please address to the problem.
Thanks in advance.

Klemens.
Comment 8 kginbg 2011-11-03 17:02:46 UTC
anybody care for this problem?
Comment 9 Ken Sharp 2011-11-03 17:07:47 UTC
(In reply to comment #8)
> anybody care for this problem?

Its assigned to me, I will get to it in time. Commercial customer problems come first, then what I deem to be 'urgent' problems from free users and so on.

PCL to PDF conversion bugs from free users are pretty low down the pole and there are a large number of more urgent bugs and enhancements to be done.
Comment 10 Ken Sharp 2012-02-25 21:09:18 UTC
Current code creates valid PDF files without warnigns for both these files. However there is content missing in both cases.
Comment 11 Ken Sharp 2012-02-28 09:42:26 UTC
(In reply to comment #7)
> I've got the same problem. After compiling 9.04 on Debian squeeze
> 
>     pcl6 -sDEVICE=pdfwrite -sOutputFile=klemens.pdf klemens.pcl
> 
> yields
> 
>     glyph index c0000000 out of range.
> 
> The resulting klemens.pdf contains only a few preliminaries, but none
> of the contents of the pcl-source. Trying to open it with the filebrowser
> results in an error message, that the pdf is damaged. Source klemens.pcl
> I've just posted before. Could you please address to the problem.

This seems to work perfectly well with the 9.05 release. It is, in any event, a different problem since this file does not contain a downloaded TrueType font.
Comment 12 Ken Sharp 2012-02-28 10:05:49 UTC
Created attachment 8387 [details]
proposed patch

This patch addresses the original problem for me. However, regression testing shows a large number of differences. I'm in the process of checking those and its entirely possible they are all improvements.
Comment 13 Ken Sharp 2012-03-01 11:09:11 UTC
The proposed patch unfortunately caused other problems. Git commit:
2a57a68efe18dd4f7898b180400a95d7baccfbc2

does fix the problem, and fix several of the regression test files as well, without introducing any new problems.