Bug 692768 - xapMM:DocumentID malformat making PDF/A invalid
Summary: xapMM:DocumentID malformat making PDF/A invalid
Status: RESOLVED DUPLICATE of bug 692422
Alias: None
Product: Ghostscript
Classification: Unclassified
Component: PDF Writer (show other bugs)
Version: 9.04
Hardware: PC All
: P4 normal
Assignee: Ken Sharp
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-12-31 13:43 UTC by Florian Schmitt
Modified: 2011-12-31 13:54 UTC (History)
1 user (show)

See Also:
Customer:
Word Size: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Florian Schmitt 2011-12-31 13:43:48 UTC 
When creating a PDF/A file from ps, gs inserts a xapMM:DocumentID. In both Linux and Windows 9.04 versions of ghostscript, the generated UUID seems to be malformatted, resulting in an invalid XMP metadata package.

Here are two examples of the XML element containing the DocumentID:

<rdf:Description rdf:about='' xmlns:xapMM='http://ns.adobe.com/xap/1.0/mm/' xapMM:DocumentID='uuid:801a53b2-35fb-11e1-0000-40218ee2ada&#129;(»¥Òc&#31;&#16;'/>

<rdf:Description rdf:about='' xmlns:xapMM='http://ns.adobe.com/xap/1.0/mm/' xapMM:DocumentID='uuid:62012087-6bd0-11ec-0000-40218ee2ada&#156;&#134;ýÿ'/>

The first line is from a PDF/A created with GPL Ghostscript 9.04 (2011-08-05) under Win XP, the second created by the same version under Linux AMD64.

The problem doesn't exist in 8.71 (didn't test other versions), here the uuid seems to be nice, only lacking the "uuid:" prefix. So maybe this problem is caused by the patch to fix #692268 - http://bugs.ghostscript.com/show_bug.cgi?id=692268


PS: Best wishes for the new year :-) !
Comment 1 Ken Sharp 2011-12-31 13:54:09 UTC 

*** This bug has been marked as a duplicate of bug 692422 ***