Databases
StackOverflow2013
Postsdbo
POpdfmark for docinfo metadata in pdf is not accepting accented characters in Keywords or Subject
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POpdfmark for docinfo metadata in pdf is not accepting accented characters in Keywords or Subject
    primarykey
    data
    text
    <p>I am inserting metadata into postscript files with a program, to be distilled to pdf with Adobe Distiller. I am using this code that I grabbed from an online chapter of <a href="http://www.pdflib.com/fileadmin/pdflib/pdf/pdfmark_primer.pdf" rel="nofollow noreferrer">Thomas Merz's "Web Publishing with Acrobat-PDF"</a>: </p> <pre><code>/pdfmark where {pop} {userdict /pdfmark /cleartomark load put} ifelse [ /Title (mot accenté) /Author (mot accenté) /Subject (mot accenté) /Keywords (mot accenté) /DOCINFO pdfmark </code></pre> <p>When you look at the metadata in the resulting pdf, the accented characters turn into "?" in the Subject and Keyword fields, but not the Title and Author fields. The characters are the same ascii 233</p> <p>I tried replacing them with octal encoding (\351), which came out the same (Title and Author okay, Subject and Keywords messed up).</p> <p>file encoding is latin-1,unix eol</p> <p>I found a mention on adobe forums, but the answer didn't make sense to me. </p> <p><a href="http://forums.adobe.com/message/1165593" rel="nofollow noreferrer">http://forums.adobe.com/message/1165593</a> and <a href="http://forums.adobe.com/thread/307687" rel="nofollow noreferrer">http://forums.adobe.com/thread/307687</a> </p> <p>I changed the encoding to utf-8, inserted the characters binarily (in VIM : <code>&lt;Ctrl-v&gt;</code>u00e9), no change. I tried inserting the BOM in a few places, it didn't work.</p> <p>This is with the Distiller from Acrobat Pro 9 (9.3.3177)</p> <p>I didn't notice this problem with Acrobat Pro 7.</p> <p>Does anybody know of a workaround to get the accented characters into ALL the metadata fields when modifying a postscript file, or tell me if I'm doing it wrong?</p> <p>It seems weird that different fields would not accept the same bytes.</p> <p>Possibly related SO question: <a href="https://stackoverflow.com/questions/128162">Unicode in PDF</a> </p> <p>I am embedding all fonts.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USCommunity
    1. USrpilkey
    plurals
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POpdfmark for docinfo metadata in pdf is not accepting accented characters in Keywords or Subject
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POpdfmark for docinfo metadata in pdf is not accepting accented characters in Keywords or Subject
      1. This table or related slice is empty.
      1. VTUpMod
    1. COHi, plinth, I don't understand your edit (version 5) where you added a close bracket. I tried that in my .ps file and Distiller won't accept it: Error: unmatchedmark; OffendingCommand: ]
      singulars
      1. POpdfmark for docinfo metadata in pdf is not accepting accented characters in Keywords or Subject
      1. USrpilkey
    2. COthe edit adding the closing "]" is plain wrong. The `[` operator opens the code block, the `pdfmark` operator closes it. There is no need **and no place** for a `]`.
      singulars
      1. POpdfmark for docinfo metadata in pdf is not accepting accented characters in Keywords or Subject
      1. USKurt Pfeifle
    3. COThanks, I removed the extra ] .
      singulars
      1. POpdfmark for docinfo metadata in pdf is not accepting accented characters in Keywords or Subject
      1. USrpilkey
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload