On 2005-03-07T09:20:53+0530, Kapil Hari Paranjape wrote:
> Here is the response that I received from the upstream author.
> 
> =========================================
> Kapil,
> 
> Ideally, I wouldn't split any of these ligatures.  The mapping applies
> to the ligatures that currently don't get supported on MSIE. In fact,
> the only reason for the mozilla and ooffice branches is to take care
> of deficiencies in current state of browsers.
> 
> =========================================
> 
> Please let me know if you think this does not answer your query.

Hello,

I don't feel very strongly about this issue, so please feel free to not
change anything.  But I am a bit confused about the upstream author's
reply.  I just tried the ligatures in Firefox (1.0.1), and it seems that
none of the ligatures from &#FB00; to &#FB04; is supported.  Doesn't
this mean that all of these ligatures, including fi and fl,
should be included in

> > /usr/share/texmf/tex4ht/ht-fonts/mozilla/charset/unicode.4hf
> > /usr/share/texmf/tex4ht/ht-fonts/mozilla/charset/mnemonic/unicode.4hf

?

> In principle, it *is* possible for you to keep your own versions
> of .4hf files by defining the environment variable
>       TEX4HTFONTSETS
> but I realise that this may be painful.

Thanks for the tip.

        Ken

-- 
Edit this signature at http://www.digitas.harvard.edu/cgi-bin/ken/sig
Dude or his dudeness or el duderino

Attachment: signature.asc
Description: Digital signature

Reply via email to