From: Jonathan Kew <jonathan_kew-HUkWsRAlkkg@public.gmane.org>
Cc: mailing list for ConTeXt users
<ntg-context-wvrSQK3plZs@public.gmane.org>
Subject: Re: Re: [NTG-context] ConTeXt-XeTeX question
Date: Wed, 1 Jun 2005 14:28:56 +0100 [thread overview]
Message-ID: <57bc824363d25869545949b44f33667b@sil.org> (raw)
In-Reply-To: <20050601131540.31203-O5WfVfzUwx9baopHwiXPDzYRy0cijUJx@public.gmane.org>
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
prev parent reply other threads:[~2005-06-01 13:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4EDE04C0-8781-4951-BBCE-023EF5F69573@mac.com>
2005-06-01 13:03 ` Dalyoung
2005-06-01 13:15 ` Adam Lindsay
[not found] ` <20050601131540.31203-O5WfVfzUwx9baopHwiXPDzYRy0cijUJx@public.gmane.org>
2005-06-01 13:28 ` Jonathan Kew [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=57bc824363d25869545949b44f33667b@sil.org \
--to=jonathan_kew-hukwsralkkg@public.gmane.org \
--cc=ntg-context-wvrSQK3plZs@public.gmane.org \
--cc=xetex-WUdSmCIlby8@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).