I cannot reproduce the problem. It works fine with Acrobat 8. On the net
I found references that this could be a bug in Acrobat 5 and/or 6. Some
also mention it has to do with images embedded in the PDF. What Acrobat
version are you working with? "135" is an error code which is described
nowhere so it's difficult in the first place to know exactly what's
wrong. My best guess is that it's really a bug in some Acrobat version.
It wouldn't be the first. By far.

On 23.01.2008 21:25:07 [EMAIL PROTECTED] wrote:
> 
> Hi everyone, 
> 
> we are facing a problem rendering a .pdf when using certain .ttf files, of
> e.g. Times New Roman font, or TrebuchetMS. Specifically, we get the
> following message: 
> 
> "There was an error processing a page. There was a problem reading this
> document (135)". 
> 
> When we change the font-face into something else, like e.g. Arial, Georgia
> etc., everything works fine and we get our .pdf rendered without any
> problem. 
> 
> We have the problem with both fop-0.93 and fop-0.94, on different
> installations (on different machines). The fonts we have the problem with,
> do not have embedding restrictions and no errors have been reported for any
> of them during the metrics creations process (pasted below). Any help/ideas
> would be greatly appreciated!
> 
> 
> --
> Parsing font...
> Reading C:\server\fop-fonts\poster\win\times.ttf...
> Font Family: Times New Roman
> Creating xml font file...
> Creating CID encoded metrics...
> Writing xml font file C:\server\fop-fonts\poster\win\times.xml...
> This font contains no embedding license restrictions.
> 
> XML font metrics file successfully created.
> --
> 
> -- 
> View this message in context: 
> http://www.nabble.com/problem-rendering-.pdf-with-certain-fonts-%22%28135%29%22-tp15051331p15051331.html
> Sent from the FOP - Users mailing list archive at Nabble.com.


Jeremias Maerki


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to