RE: Mac Font problem
Andreas, That solved it for now... tx. When I have time I will try to find out the cause... Ch., -Original Message- From: Andreas L Delmelle [mailto:[EMAIL PROTECTED] Sent: 20 November 2007 08:13 To: fop-users@xmlgraphics.apache.org Subject: Re: Mac Font problem On Nov 20, 2007, at 07:56, Raphael Parree wrote: Hi I have a problem with a font on a Mac.on my PC everything seems to work but on the Macs uses by our publishing department the Courier New font does not work. It is installed on the Mac (True Type font). I am working with rev 592554 (6 nov) and use the auto detect feature. I have tried deleting the cache file as that often helps on ,my PC after using new fonts or updating FOP. I saw some posts about true type fonts on a Mac posted in feb 2006 (http:// www.nabble.com/TTFReader-and-MacOsX-.ttf-fonts- tf1139715.html#a2986169) I'm also on Mac, and noticed the same effect. Haven't looked into the exact cause, though... One possible workaround, until someone decides to get to the bottom of this: Mac OS X also supports Windows TTFs, so in the worst case, you could maybe try to replace the native Mac TTF with the Windows TTF. Untested though, can't say for sure it will work. HTH! Andreas - 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]
Re: Mac Font problem
On Nov 20, 2007, at 09:05, Raphael Parree wrote:
Andreas,
That solved it for now... tx.
When I have time I will try to find out the cause...
FWIW, and to whom it may concern: the limitation, I think, is caused
by the following in org.apache.fop.fonts.TTFFile line 225 and following
===
if (cmapPID == 3 cmapEID == 1) {
cmapUniOffset = cmapOffset;
}
}
if (cmapUniOffset = 0) {
log.fatal(Unicode cmap table not present);
log.fatal(Unsupported format: Aborting);
return false;
}
===
I looked at the docs available on developer.apple.com (amongst
others: http://developer.apple.com/textfonts/TTRefMan/RM06/
Chap6name.html#ID), and it seems that the above means that we
currently only support CMAPs with a PlatformID of 3 (= Microsoft).
I'll see shortly if changing this helps to support Mac TrueType fonts.
Cheers
Andreas
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Mac Font problem
On Nov 20, 2007, at 07:56, Raphael Parree wrote: Hi I have a problem with a font on a Mac…on my PC everything seems to work but on the Macs uses by our publishing department the Courier New font does not work. It is installed on the Mac (True Type font). I am working with rev 592554 (6 nov) and use the auto detect feature. I have tried deleting the cache file as that often helps on ,my PC after using new fonts or updating FOP. I saw some posts about true type fonts on a Mac posted in feb 2006 (http:// www.nabble.com/TTFReader-and-MacOsX-.ttf-fonts- tf1139715.html#a2986169) I'm also on Mac, and noticed the same effect. Haven't looked into the exact cause, though... One possible workaround, until someone decides to get to the bottom of this: Mac OS X also supports Windows TTFs, so in the worst case, you could maybe try to replace the native Mac TTF with the Windows TTF. Untested though, can't say for sure it will work. HTH! Andreas - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
