| Summary: | StyledText has problems with layout in the presence of ligatures | ||
|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Boris Bokowski <bokowski> |
| Component: | SWT | Assignee: | Felipe Heidrich <eclipse.felipe> |
| Status: | RESOLVED FIXED | QA Contact: | Silenio Quarti <Silenio_Quarti> |
| Severity: | normal | ||
| Priority: | P3 | CC: | skovatch |
| Version: | 3.6 | ||
| Target Milestone: | 3.7 M3 | ||
| Hardware: | PC | ||
| OS: | Mac OS X - Carbon (unsup.) | ||
| Whiteboard: | |||
|
Description
Boris Bokowski
I'm pretty sure the auto-conversion to ligature behavior can be disabled. TextEdit.app, for example, doesn't do this by default. Btw, one place in Eclipse where this can be observed is in the CVS Commit dialog. I very quickly try adding this line: attrStr.addAttribute(OS.NSKernAttributeName, NSNumber.numberWithInt(0), range); to TextLayout#computeRuns() but it didn't work, more investigation is needed. see http://developer.apple.com/library/mac/#documentation/Cocoa/Reference/ApplicationKit/Classes/NSAttributedString_AppKitAdditions/Reference/Reference.html (In reply to comment #3) > I very quickly try adding this line: > > attrStr.addAttribute(OS.NSKernAttributeName, NSNumber.numberWithInt(0), range); > to TextLayout#computeRuns() but it didn't work, more investigation is needed. Try NSLigatureAttributeName with a value of 0 instead. "NSLigatureAttributeName NSNumber containing integer Default 1, standard ligatures; 0, no ligatures; 2, all ligatures" (In reply to comment #4) > (In reply to comment #3) > > I very quickly try adding this line: > > > > attrStr.addAttribute(OS.NSKernAttributeName, NSNumber.numberWithInt(0), range); > > to TextLayout#computeRuns() but it didn't work, more investigation is needed. > Try NSLigatureAttributeName with a value of 0 instead. > "NSLigatureAttributeName > NSNumber containing integer > Default 1, standard ligatures; 0, no ligatures; 2, all ligatures" thank you sir, that worked. I was afraid that no ligatures was going to break lam-alef ligatures but it all worked fine. I'll clean my workspace tomorrow morning and release the fix. Fixed in HEAD > 20100916 |