ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
* ConTeXt-XeTeX question
       [not found] <4EDE04C0-8781-4951-BBCE-023EF5F69573@mac.com>
@ 2005-06-01 13:03 ` Dalyoung
  2005-06-01 13:15   ` Adam Lindsay
  0 siblings, 1 reply; 3+ messages in thread
From: Dalyoung @ 2005-06-01 13:03 UTC (permalink / raw)



[-- Attachment #1.1: Type: text/plain, Size: 1534 bytes --]



>
> Hi all,
>
> I need some help.
>
> 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 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.
>
> 2) I noticed some strange spaces.
>
>     (a) between units and words
>         1\Centi\Meter 인    --> output: 1cm   인
>
>     (b) between units and comma, units and units, but there is no  
> space between units and next words.
>
>     길이의 기본단위는 \Meter, 넓이의 기본 단위는 \Square\Meter, 그리 
> 고 부피의 기본 단위는 \Cubic\Meter 이다.
>         output: 길이의 기본단위는 m    , 넓이의 기본 단위는 m    2,  
> 그리고 부피의 기본 단위는 m    3 이다.
>
> Here 2 and 3 are written as superscript.
>
> Are these problems yielded from my personal font script file?
>
> Thank you for reading.
>
> Regards,
>
> Dalyoung


[-- Attachment #1.2: Type: text/html, Size: 3188 bytes --]

[-- Attachment #2: Type: text/plain, Size: 139 bytes --]

_______________________________________________
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: ConTeXt-XeTeX question
  2005-06-01 13:03 ` ConTeXt-XeTeX question Dalyoung
@ 2005-06-01 13:15   ` Adam Lindsay
       [not found]     ` <20050601131540.31203-O5WfVfzUwx9baopHwiXPDzYRy0cijUJx@public.gmane.org>
  0 siblings, 1 reply; 3+ messages in thread
From: Adam Lindsay @ 2005-06-01 13:15 UTC (permalink / raw)


[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@comp.lancs.ac.uk
 Lancaster University, InfoLab21        +44(0)1524/510.514
 Lancaster, LA1 4WA, UK             Fax:+44(0)1524/510.492
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: Re: [NTG-context] ConTeXt-XeTeX question
       [not found]     ` <20050601131540.31203-O5WfVfzUwx9baopHwiXPDzYRy0cijUJx@public.gmane.org>
@ 2005-06-01 13:28       ` Jonathan Kew
  0 siblings, 0 replies; 3+ messages in thread
From: Jonathan Kew @ 2005-06-01 13:28 UTC (permalink / raw)
  Cc: mailing list for ConTeXt users

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

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2005-06-01 13:28 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [not found] <4EDE04C0-8781-4951-BBCE-023EF5F69573@mac.com>
2005-06-01 13:03 ` ConTeXt-XeTeX question Dalyoung
2005-06-01 13:15   ` Adam Lindsay
     [not found]     ` <20050601131540.31203-O5WfVfzUwx9baopHwiXPDzYRy0cijUJx@public.gmane.org>
2005-06-01 13:28       ` Re: [NTG-context] " Jonathan Kew

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).