> however I have noticed two things which makes the conversion tex4ht > does problematic. First, when you open the html file using a browser, > the ff,fi,... combination look different than the rest of the text > (blurred).
This looks like a browser bug to me, if a unicode char is generated for the ligature, and the browser is showing it differently than the surrounding chars. In general a run of text within the same font should look the same wrt the font weight etc. Could also be a font problem, maybe your default browser font doesn't have the ligature chars hinted correctly while the other chars are, and you're using a scaled font. > Second, the funny conversion makes it hard to apply > post-processors, such as spell checkers and syntax checkers to the > html file. Why don't you use a Latex-aware spell checker, like ispell, on the TeX source? As for the HTML syntax checking (i.e., validation of the SGML markup), I doubt it should matter whether the character entities for the ligatures are in or not. > you are probably right that by creating an htf file this can be > done. However, I would expect that this would be the default behavior, > hence I do not think that the user should be bothered with doing that. > Nevertheless, I might be wrong ... Just a note from another user of tex4ht who thinks this is definitely not a bug, but rather a wishlist. Personally, I can't identify with the need to implement this feature, but could be other users might want it as well. V. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
