On Wed, Aug 31, 2011 at 5:58 PM, Neil Hodgson <nyamatongwe at gmail.com> wrote: > [...] some text drawing engines draw decomposed characters ("o" > followed by " ̈" -> "ö") differently compared to their composite > equivalents ("ö") and this may be perceived as better or worse. I'd > like to offer an option to replace some decomposed characters with > their composite equivalent before drawing but since other characters > may look worse, I don't want to do a full normalization. Isn't this an issue properly solved by various normal forms? -- --Guido van Rossum (python.org/~guido)
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4