[XeTeX] Strange Euler Script font behaviour

[Will Robertson]

On 20 Nov 2004, at 1:08 AM, Jonathan Kew wrote:
>
> OK, confession time.... access to characters in TeX legacy fonts using 
> TFMs and non-standard encodings is currently rather fragile. (I'm 
> amazed to have gotten away with it as far as this!)

I'm a little surprised not to have noticed it yet :)

> ...
> So, for right now you could probably solve this if you're prepared to 
> create a suitable .enc file and edit psfonts.map to explicitly use 
> this. For the longer term, I'm looking at possible ways to make the 
> whole process more robust, and perhaps to avoid the need for a full 
> 'post' table in the .otf fonts (to simplify the conversion from .pfb), 
> or even use the .pfb files directly. This is in a 
> research/experimental stage at the moment; no guarantees of exactly 
> what I'll be able to achieve.

Okay, I'm having a bit of a play around to see what I can come up with.
One question: what is the difference between
    texmf/fonts/otf/eusm10.otf
and
    texmf/fonts/otf/xetex/bluesky/euler/eusm10.otf
?
I notice they're not identical.

Anyway, I'm also interested in converting the Base35 postscript fonts 
for use in XeTeX, so I might try my hand at that also if I have time. 
If the only requirement is to include the post table, I think fontforge 
is up to the task.

> Sorry for the brokenness of the current situation!

Not at all :)
Keeps us on our toes.

Will