osdir.com
mailing list archive
Mozy Online Backup: 2GB Free. Automatic. Secure.

Subject: Re: Re: [NTG-context] ConTeXt-XeTeX question - msg#00001

List: tex.xetex

Date: Prev Next Index Thread: Prev Next Index
On 1 Jun 2005, at 2:15 pm, Adam Lindsay wrote:

[I'm copying to the XeTeX list--this may not be ConTeXt-specific. -atl]
Dalyoung said this at Wed, 1 Jun 2005 22:03:37 +0900:

1) Recently, I upgraded ConTeXt new version and got a problem in
compilation. However, after upgrading texexec and creating format
files, it is working fine with some warning messages as following:

WARNING: Type1 font data returned by OFAStreamPSDownload isn't in
the correct format required by the Adobe Type 1 Font Format
specification.
WARNING: Type1 font data returned by OFAStreamPSDownload isn't in
the correct format required by the Adobe Type 1 Font Format
specification.
WARNING: Type1 font data returned by OFAStreamPSDownload isn't in
the correct format required by the Adobe Type 1 Font Format
specification.

I noticed this too on my recent re-install. I presume it's an issue with
legacy type1 .pfb files being wrapped in a Mac format. However, I am not
100% certain this issue is independent of XeTeX on Tiger: I didn't
really test the previous ConTeXt with XeTeX on 10.4.

It's a XeTeX+Tiger issue, not related to the specific format being used but to the way we're supporting .pfb fonts (which the OS doesn't really support). Something changed between Panther and Tiger that made this start happening, although the output still seems to be OK (in particular, the .pfb fonts that the warnings relate to still seem to render fine).

I have reported this to Apple and am trying to determine whether it is in fact a problem with what XeTeX is doing (in which case I need some more information on just what is wrong), or an Apple problem. Maybe I can get some answers at WWDC next week, if I can corner the right people.


I don't know the causes of these warnings. I am using personal
script file for Korean, but there was no warning before in the same
condition.

The first thing to figure out is if XeLaTeX users encounter this as well
on Tiger when using legacy fonts.

Yes, they will, but if they're running from an environment like TeXShop rather than Terminal, they may not have noticed the messages, as they'll appear only in the system log, which most people don't usually look at.

JK


Was this page helpful?
Yes No
Thread at a glance:

Previous Message by Date: click to view message preview

Re: ConTeXt-XeTeX question

[I'm copying to the XeTeX list--this may not be ConTeXt-specific. -atl] Dalyoung said this at Wed, 1 Jun 2005 22:03:37 +0900: >> 1) Recently, I upgraded ConTeXt new version and got a problem in >> compilation. However, after upgrading texexec and creating format >> files, it is working fine with some warning messages as following: >> >> WARNING: Type1 font data returned by OFAStreamPSDownload isn't in >> the correct format required by the Adobe Type 1 Font Format >> specification. >> WARNING: Type1 font data returned by OFAStreamPSDownload isn't in >> the correct format required by the Adobe Type 1 Font Format >> specification. >> WARNING: Type1 font data returned by OFAStreamPSDownload isn't in >> the correct format required by the Adobe Type 1 Font Format >> specification. I noticed this too on my recent re-install. I presume it's an issue with legacy type1 .pfb files being wrapped in a Mac format. However, I am not 100% certain this issue is independent of XeTeX on Tiger: I didn't really test the previous ConTeXt with XeTeX on 10.4. >> I don't know the causes of these warnings. I am using personal >> script file for Korean, but there was no warning before in the same >> condition. The first thing to figure out is if XeLaTeX users encounter this as well on Tiger when using legacy fonts. -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Adam T. Lindsay, Computing Dept. atl@xxxxxxxxxxxxxxxx Lancaster University, InfoLab21 +44(0)1524/510.514 Lancaster, LA1 4WA, UK Fax:+44(0)1524/510.492 -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

Next Message by Date: click to view message preview

Re: Re: [NTG-context] ConTeXt-XeTeX question

Le 1 juin 05 à 15:28, Jonathan Kew a écrit : On 1 Jun 2005, at 2:15 pm, Adam Lindsay wrote: WARNING: Type1 font data returned by OFAStreamPSDownload isn't in the correct format required by the Adobe Type 1 Font Format specification. It's a XeTeX+Tiger issue, not related to the specific format being used but to the way we're supporting .pfb fonts (which the OS doesn't really support). Something changed between Panther and Tiger that made this start happening, although the output still seems to be OK (in particular, the .pfb fonts that the warnings relate to still seem to render fine). [...] The first thing to figure out is if XeLaTeX users encounter this as well on Tiger when using legacy fonts. Yes, they will, but if they're running from an environment like TeXShop rather than Terminal, they may not have noticed the messages, as they'll appear only in the system log, which most people don't usually look at. I think I got that once, and it halted compilation in TeXShop. Compiling again (without changing anything in between) made the message disappear and not reappear ever after. I'm not sure, though, as I didn't take the time to note the exact warning and context. Bruno Voisin

Previous Message by Thread: click to view message preview

Re: ConTeXt-XeTeX question

[I'm copying to the XeTeX list--this may not be ConTeXt-specific. -atl] Dalyoung said this at Wed, 1 Jun 2005 22:03:37 +0900: >> 1) Recently, I upgraded ConTeXt new version and got a problem in >> compilation. However, after upgrading texexec and creating format >> files, it is working fine with some warning messages as following: >> >> WARNING: Type1 font data returned by OFAStreamPSDownload isn't in >> the correct format required by the Adobe Type 1 Font Format >> specification. >> WARNING: Type1 font data returned by OFAStreamPSDownload isn't in >> the correct format required by the Adobe Type 1 Font Format >> specification. >> WARNING: Type1 font data returned by OFAStreamPSDownload isn't in >> the correct format required by the Adobe Type 1 Font Format >> specification. I noticed this too on my recent re-install. I presume it's an issue with legacy type1 .pfb files being wrapped in a Mac format. However, I am not 100% certain this issue is independent of XeTeX on Tiger: I didn't really test the previous ConTeXt with XeTeX on 10.4. >> I don't know the causes of these warnings. I am using personal >> script file for Korean, but there was no warning before in the same >> condition. The first thing to figure out is if XeLaTeX users encounter this as well on Tiger when using legacy fonts. -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Adam T. Lindsay, Computing Dept. atl@xxxxxxxxxxxxxxxx Lancaster University, InfoLab21 +44(0)1524/510.514 Lancaster, LA1 4WA, UK Fax:+44(0)1524/510.492 -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

Next Message by Thread: click to view message preview

Re: Re: [NTG-context] ConTeXt-XeTeX question

Le 1 juin 05 à 15:28, Jonathan Kew a écrit : On 1 Jun 2005, at 2:15 pm, Adam Lindsay wrote: WARNING: Type1 font data returned by OFAStreamPSDownload isn't in the correct format required by the Adobe Type 1 Font Format specification. It's a XeTeX+Tiger issue, not related to the specific format being used but to the way we're supporting .pfb fonts (which the OS doesn't really support). Something changed between Panther and Tiger that made this start happening, although the output still seems to be OK (in particular, the .pfb fonts that the warnings relate to still seem to render fine). [...] The first thing to figure out is if XeLaTeX users encounter this as well on Tiger when using legacy fonts. Yes, they will, but if they're running from an environment like TeXShop rather than Terminal, they may not have noticed the messages, as they'll appear only in the system log, which most people don't usually look at. I think I got that once, and it halted compilation in TeXShop. Compiling again (without changing anything in between) made the message disappear and not reappear ever after. I'm not sure, though, as I didn't take the time to note the exact warning and context. Bruno Voisin
Sign up for updates to this mailing list. email:
Loading Comments...
Home | News | Patents | Sitemap | FAQ | advertise

Advertising by