Bug#297486: tex4ht: "fi" and "fl" ligatures not decomposed along with "ff", "ffi", "ffl"

[Kapil Hari Paranjape]

Hello,

On Mon, Feb 28, 2005 at 06:49:24PM -0500, Chung-chieh Shan wrote:
> The following files map character entities like &#xFB03 to ffi,
> but do not map &#xFB01 and &#xFB02 to fi and fl, respectively:
> 
> /usr/share/texmf/tex4ht/ht-fonts/iso8859/1/charset/unicode.4hf
> /usr/share/texmf/tex4ht/ht-fonts/iso8859/2/charset/unicode.4hf
> /usr/share/texmf/tex4ht/ht-fonts/mozilla/charset/unicode.4hf
> /usr/share/texmf/tex4ht/ht-fonts/mozilla/charset/mnemonic/unicode.4hf
> /usr/share/texmf/tex4ht/ht-fonts/ooffice/charset/unicode.4hf
> 
> I don't see any reason to treat these ligatures differently.

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.

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 and regards,

Kapil.

-- 
 http://www.imsc.res.in/~kapil/gpg.html for my Public Key.
------------------------------------------------------------------
1024D/5416E5B8 2004-10-13 Kapil Hari Paranjape <[EMAIL PROTECTED]>
1024g/3BDF565B 2004-10-13
Key fingerprint = F160 CBB9 03C8 425D 4BBA  79F4 491F 8FDA 5416 E5B8
--


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]