PDFdev is a service provided by PDFzone.com | http://www.pdfzone.com _____________________________________________________________
I tried to create a pdf file with truetype CID font, but it does not work. I do not see why. Perhaps should I have to embed the font? I put the the file on ftp://ftp02.irislink.com/ocr/xwalhin/pdf/file2.pdf A strange think is that Acrobat 5 opens this file, but Acrobat 6 does not! How is it possible? Xavier -----Original Message----- From: Thomas Merz [mailto:[EMAIL PROTECTED] Sent: jeudi 27 novembre 2003 15:51 To: Xavier Walhin Cc: [EMAIL PROTECTED] Subject: Re: [PDFdev] page content problem Xavier Walhin wrote: > ok, I should (and I will) use CID font. > Anyway, can you explain why the proposed syntax is wrong? Is it a pdf rule > breaking in my example, is it an interpretation error from Acrobat,...? I didn't say it's wrong (except for the short /Widths array), but rather gave a recommendation for more robust output. It is based on the following: - Encoding handling for TrueType fonts was underspecified in the PDF reference for a long time, with unpredictable behavior in early viewer generations (perhaps up to Acrobat 4). - Certain combinations of Encodings and TrueType cmaps were documented to result in platform-specific behavior in Acrobat. - Starting with PDF 1.4 the PDF reference contains a clearer recommendation (p. 333): "Because some aspects of TrueType glyph selection are dependent on the viewer implementation or the operating system, PDF files that use TrueType fonts should follow certain guidelines to ensure predictable behavior across all viewer applications. The font program should be embedded. A nonsymbolic font should specify MacRomanEncoding or WinAnsiEncoding as the value of its Encoding entry, with no Differences array." Using WinAnsi was my first recommendation; since you require characters outside of WinAnsi, CID fonts seem the most reliable approach. Note the word "should" -- you can still ignore the above phrase, but I guess you'll do so at your own risk... - Finally, there are bugs in various Acrobat versions when it comes to glyph selection. For example, a few names of the Adobe glyph list (AGL) don't seem to work as documented when trying to address TrueType fonts with name-based Encodings containing standard glyph names. This is another reason to avoid the name-based Encoding approach and stick with direct glyph ID addressing and CID fonts. Thomas _______________________________________________________________ Thomas Merz [EMAIL PROTECTED] http://www.pdflib.com Personalize PDF: PDFlib Personalization Server and Block plugin _______PDFlib - a library for generating PDF on the fly________ To change your subscription: http://www.pdfzone.com/discussions/lists-pdfdev.html
