Comment #12 on issue 22240 by verdyp: Do ligature substitution on web content http://code.google.com/p/chromium/issues/detail?id=22240
I agree, but what is suggested is to implement several levels of ligatures, as those already implemented (with custom CSS properties) in Adobe Flex 4, which provides an excellent implementation of what typographs want. See http://help.adobe.com/en_US/Flex/4.0/langref/spark/components/supportClasses/Slider.h tml But fonts and renderers can still correctly honor the prohibition of automatic ligatures for specific languages like: - 'fl' in German between two morphemes : note that Unicode suggests using <f,ZWNJ,l> for this case, if the language cannot be identified by the browser or is not explicitly tagged. - 'oe' in French (there are oppositions like "œuf" where the ligature is required and "coexister" where the ligature is prohibited) Even without such advanced ligatures support (such as the one already proposed by Adobe), the browser should still honor the ZWJ and ZWNJ correctly (without exhibiting the bug #26487) and in a way conforming to Unicode (not showing by default glyphs for format controls). -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~---------~--~----~------------~-------~--~----~ Automated mail from issue updates at http://crbug.com/ Subscription options: http://groups.google.com/group/chromium-bugs -~----------~----~----~----~------~----~------~--~---
