Description: With the actual LO-version (5.3.0.3) »OpenType layout is now supported on all platforms, and default OpenType features are enabled for all languages« (https://wiki.documentfoundation.org/ReleaseNotes/5.3#Text_Layout). But there is no possibility to controll the use of the features. For example ligatures are set no by default. But I want to decide, if I want to use them or not. The same is with text/old style figures and other features. And how can I work with typographic correct small caps and not with digital generated wrong small caps? Actual Results: OpenType features are enabled by default, so cannot controll them. Expected Results: There has to be implemented a controll-dialog concerning the specific use of OpenType features. Reproducible: Always User Profile Reset: No Additional Info: User-Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:51.0) Gecko/20100101 Firefox/51.0
(In reply to Juergen from comment #0) > With the actual LO-version (5.3.0.3) »OpenType layout is now supported on > all platforms, and default OpenType features are enabled for all languages« > (https://wiki.documentfoundation.org/ReleaseNotes/5.3#Text_Layout). But > there is no possibility to controll the use of the features. There is. The release notes also state that "OpenType layout features can be controlled using the syntax previously only supported for Graphite fonts." Suppose you use Calibri font and want to disable ligatures, you can type this in the font name box: Calibri:-liga And to enable small caps: Calibri:smcp And so on. And you can combine several settings with &.
(In reply to Maxim Monastirsky from comment #1) > (In reply to Juergen from comment #0) > > With the actual LO-version (5.3.0.3) »OpenType layout is now supported on > > all platforms, and default OpenType features are enabled for all languages« > > (https://wiki.documentfoundation.org/ReleaseNotes/5.3#Text_Layout). But > > there is no possibility to controll the use of the features. > There is. The release notes also state that "OpenType layout features can be > controlled using the syntax previously only supported for Graphite fonts." > > Suppose you use Calibri font and want to disable ligatures, you can type > this in the font name box: > > Calibri:-liga > > And to enable small caps: > > Calibri:smcp > > And so on. And you can combine several settings with &. Sorry Maxim, but this is absolutly unconfortable und for the ›normal‹ user unpractical, inacceptable. Nobody, except IT-experts, likes to work with cryptic syntax. That way, I fear, OpenType-features will not be widley used. I hope very much, that LO or Writer will soon get implemented an appropriate, ›user-friendly‹ toolbar, sidebar, controll-window-dialogue or something like this. Bothersome is also that OpenType-features like ligatures are enabled by default, regardless of whether I want them in the text or not. It cannot simple be disabled by the user, right?
We'll mark this as an enhancement then. But not clear there is a priority to provide GUI support for applying and tracking OpenType features [1] beyond the current application/display in the Character style dialog and Sidebar content panel. Some effort could be made to map the OpenType features onto the Character dialog Font Effects tab to provide a GUI, but that would be for a limited subset of features. But IMHO the most efficient is what exists now, applying the feature directly as direct formatting or by defining and applying it in a style. All without cluttering the UI with implementing GUI for infrequently used typographic widgets. =ref-= [1] https://www.microsoft.com/typography/otspec/featurelist.htm
The lack of UI is one of the reasons why big 58941 is still open, no need for a new bug. *** This bug has been marked as a duplicate of bug 58941 ***
See also bug 105454.
This can be done via creating an extension to intergrate such interfaces.
There is an old extension called ›Typography toolbar‹ (https://extensions.libreoffice.org/extensions/typography-toolbar). But the latest release is from 2013 and it does’t work with the actuall LO-version 5.3.1.2. Perhaps someone can concern himself with this.
That is what I proposed in comment 6, I think a new extension compatible with latest LO 5.3.1.2 would be more suitable.