[XeTeX] Lucida Bright problem with 0.997

Stephen Moye stephenmoye at mac.com
Sun Jul 29 00:03:17 CEST 2007


On Jul 28, 2007, at 4:50 PM, Jonathan Kew wrote:

> On 28 Jul 2007, at 9:28 pm, Stephen Moye wrote:
>
>>> What format are your Lucida Bright fonts? Are you perhaps using an
>>> old set of "classic-style" LWFN PostScript fonts and an accompanying
>>> suitcase of bitmaps?
>>
>> Yes. The following output from "xdvipdfmx -vv testart.xdv" would
>> seem to
>> support that:
>>
>> 16:13 ~/Desktop% xdvipdfmx -vv testart.xdv
>> DVI Comment:  XeTeX output 2007.07.28:1612
>> testart.xdv -> testart.pdf
>> <AGL:texglyphlist.txt>[1<LucidaBright(LucidaBright:Lucida Bright)
>> @9.93pt<NATIVE-FONTMAP:LucidaBright/H>
>> fontmap: LucidaBright/H -> LucidaBright/H(Identity-H)
>>
>> pdf_font>> Input encoding "Identity-H" requires at least 2 bytes.
>> pdf_font>> The -m <00> option will be assumed for "LucidaBright/H".
>>>
>> ** ERROR ** Invalid font: -1 (0)
>>
>> Output file removed.
>> 16:13 ~/Desktop%
>>
>> ===
>>
>> What font formats would not incur the error? OT, obviously -- any
>> others?
>
> Any form of TrueType (.ttf or Mac suitcase/dfont) should be OK, I
> believe; but if a font is currently in Type 1 format, it would be a
> pity to convert it to TrueType curves. To maintain the Type 1
> outlines, it would need to be repackaged in OpenType (CFF) format.
> PFB would also be OK for xdvipdfmx, but that isn't supported in
> standard Mac applications, so they'd be TeX-only fonts.

I'll have to sort that out, but at least there is a workaround.
>
> I'll look into the LWFN issue, as that's obviously going to be a
> problem for Mac users with older PostScript fonts around.

That would be wonderful -- thanks.



Stephen


More information about the XeTeX mailing list