On 24/04/2012 19:16, Luis Bernardo wrote:

Hi Luis,
Just by itself the embed-url attribute does not imply that the font will be embedded. I know that the attribute name is confusing, and the documentation may not be up to date, but I believe that is the case. Fonts are subset embedded by default unless the referenced-fonts element is present, in which case they are referenced.

That is correct. The error reported by Adobe Reader suggests that the Simsun font is not registered with Adobe Reader. I believe it is not sufficient for the font to just be installed in the Operating System. I think the fonts also need to be registered with Adobe. Which makes the use case of referencing fonts instead of embedding somewhat worthless.

Thanks,

Chris

On 4/24/12 4:15 PM, Jean-Philippe Courson wrote:
Hi Glenn,

Thanks for your reply.

In your example, you are embedding the font:

<font embed-url="simsun.ttf"> the embed-url attribute will get the font embedded.

I have no problem creating a chinese PDF when the font is embedded.

The issue I am raising is when trying to reference (not embed) the font.

Thanks for your help,

Best regards,
JP

On 23 Apr 2012, at 15:26, Glenn Adams wrote:

I just tried this with the font you referenced and had no problem. Attached is the configuration file and input file I used and resulting output. I'm using the current FOP 1.1dev (trunk) build.

As Chris points out, you may wish to avoid<auto-detect/>. Also, you notice that I disabled the font cache and placed the font in a "fonts" subdirectory where I did the test.


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]





---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to