You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@pdfbox.apache.org by "Guillaume Bailleul (Created) (JIRA)" <ji...@apache.org> on 2011/12/01 21:30:41 UTC
[jira] [Created] (PDFBOX-1178) Type3Validation error when firstChar
and lastChar badly defined in font description dictionary
Type3Validation error when firstChar and lastChar badly defined in font description dictionary
----------------------------------------------------------------------------------------------
Key: PDFBOX-1178
URL: https://issues.apache.org/jira/browse/PDFBOX-1178
Project: PDFBox
Issue Type: Bug
Components: Preflight
Reporter: Guillaume Bailleul
Assignee: Eric Leleu
Fix For: 1.7.0
I have got a problem with a font in a PDF/A where LastChar entry seems badly defined (255). I will add the file if possible. The file is valid with commercial validators.
File cannot be validated due to NullPointerException because the case "character stream not existing and character width not defined" is not handle. I join a patch that accept that character are not defined.
With this patch, validation works. I put "TODO" where new case have to be handled.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (PDFBOX-1178) Type3Validation error when
firstChar and lastChar badly defined in font description dictionary
Posted by "Eric Leleu (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PDFBOX-1178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Eric Leleu resolved PDFBOX-1178.
--------------------------------
Resolution: Fixed
Fixed, If the CharProc is null we set a GlyphDetail with an exception. (whatever is the Width value) If the character is used in a TextOperator, the GlyphDetail will throw the exception.
> Type3Validation error when firstChar and lastChar badly defined in font description dictionary
> ----------------------------------------------------------------------------------------------
>
> Key: PDFBOX-1178
> URL: https://issues.apache.org/jira/browse/PDFBOX-1178
> Project: PDFBox
> Issue Type: Bug
> Components: Preflight
> Reporter: Guillaume Bailleul
> Assignee: Eric Leleu
> Fix For: 1.7.0
>
> Attachments: pdfbox_1178.patch, test1_4.pdf
>
>
> I have got a problem with a font in a PDF/A where LastChar entry seems badly defined (255). I will add the file if possible. The file is valid with commercial validators.
> File cannot be validated due to NullPointerException because the case "character stream not existing and character width not defined" is not handle. I join a patch that accept that character are not defined.
> With this patch, validation works. I put "TODO" where new case have to be handled.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (PDFBOX-1178) Type3Validation error when firstChar
and lastChar badly defined in font description dictionary
Posted by "Guillaume Bailleul (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PDFBOX-1178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Guillaume Bailleul updated PDFBOX-1178:
---------------------------------------
Attachment: test1_4.pdf
example of PDF/A with problem
> Type3Validation error when firstChar and lastChar badly defined in font description dictionary
> ----------------------------------------------------------------------------------------------
>
> Key: PDFBOX-1178
> URL: https://issues.apache.org/jira/browse/PDFBOX-1178
> Project: PDFBox
> Issue Type: Bug
> Components: Preflight
> Reporter: Guillaume Bailleul
> Assignee: Eric Leleu
> Fix For: 1.7.0
>
> Attachments: pdfbox_1178.patch, test1_4.pdf
>
>
> I have got a problem with a font in a PDF/A where LastChar entry seems badly defined (255). I will add the file if possible. The file is valid with commercial validators.
> File cannot be validated due to NullPointerException because the case "character stream not existing and character width not defined" is not handle. I join a patch that accept that character are not defined.
> With this patch, validation works. I put "TODO" where new case have to be handled.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (PDFBOX-1178) Type3Validation error when firstChar
and lastChar badly defined in font description dictionary
Posted by "Guillaume Bailleul (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PDFBOX-1178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Guillaume Bailleul updated PDFBOX-1178:
---------------------------------------
Attachment: pdfbox_1178.patch
a patch that accept some missing character description streams
> Type3Validation error when firstChar and lastChar badly defined in font description dictionary
> ----------------------------------------------------------------------------------------------
>
> Key: PDFBOX-1178
> URL: https://issues.apache.org/jira/browse/PDFBOX-1178
> Project: PDFBox
> Issue Type: Bug
> Components: Preflight
> Reporter: Guillaume Bailleul
> Assignee: Eric Leleu
> Fix For: 1.7.0
>
> Attachments: pdfbox_1178.patch
>
>
> I have got a problem with a font in a PDF/A where LastChar entry seems badly defined (255). I will add the file if possible. The file is valid with commercial validators.
> File cannot be validated due to NullPointerException because the case "character stream not existing and character width not defined" is not handle. I join a patch that accept that character are not defined.
> With this patch, validation works. I put "TODO" where new case have to be handled.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira