https://bugs.documentfoundation.org/show_bug.cgi?id=167686
Eyal Rozenberg <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |needsDevEval --- Comment #5 from Eyal Rozenberg <[email protected]> --- (In reply to V Stuart Foote from comment #3) > Real issue is how to extract each font's full set of Smart Font (SF) > features, and then how to represent those features in a UI to make feature > selections. If you're saying, that we are currently not extracting the full set of features, then - please file that as a separate bug. That is not the "real issue" here. This bug is about what we do with non-toggle, non-numeric features we already extract. Currently we use drop-down listboxes for them, but we should prefer radio buttons, in many more, and perhaps nearly all, cases (which are not in fact boolean yes/no or on/off toggles). > Problem already is that most Graphite based SF, and a growing set of OTF > fonts, have extensive SF stylistic and alternative forms embedded internal > to the font. Some are so numerous they already overwhelm the font > 'Features...' dialog. > That would be another bug, related but separate from this one. > More extensive refactoring of the UI is going to be needed, should work on > bug 166079 ever happen. Absent that the 'Features...' dialog UI is suitable > to task of handling SF features. This is marked as an _enhancement_, not a bug. Naturally, a drop-down list box works as does a radio button group. Also, if the UI is completely revamped - this bug may become irrelevant. But for now, we may effect a concrete improvement which should not be difficult. In fact, I wonder if it might not be an easy hack. -- You are receiving this mail because: You are the assignee for the bug.
