Inkscape 1.1.1 inkscape-1.1.1_2021-09-20_3bf5ae0d25-x64.msi installer reproduceable on 2 win10 systems
coming from Inkscape 1.0.1 where the OTF features were pre-shown beforehand, preview on the selected option as expected, but not executed,
Now on my windows systems I installed v1.1.1.
This time the preview of the different options is not shown, not before nor after selecting a specific option. When one clicks a known option, it is perfectly executed. Alas from different fonts, with sometimes up to 10 alternative features, one can hardly know them all.
Where type is usually an essential part of e.g. logo design, fonts are often chosen with their subsets in mind, this might prove a serious issue.
@TylerDurden Alas, that's where I started, But at inscribing they asked me so many things I could not relate to as a non-professional, that I thought first to try here, Documentation by images could not be added here however. In the meantime I found another remarkable issue, concerning the same (type of) font: the secondary font, "'fontname' shadow" is not listed in the font-list, does appear however in the textbox-controls as if it were a feature. It's not, but I couldn't care less, since it's/those are unusable without the main typeface. That one could be applied in 1.0.1, in 1.1.1 it appears but can't be applied to the text's copy.
It might help: both images show an A4 page with the word 'tekst' on 1.1.1 and on 1.0.1 tekstt with the final t selected as it should be the one glyph that should get the feature. in both versions you see in the feature settings the subsets and the glyphs they cover. You see a clear difference between ss01, ss04 and ss07. In the 1.0.1 version you see a right column with the effect that choice may give on the text. In 1.1.1 that column equals the left column In 1.0.1 at the bottom there is an example of the full word (only 1 glyph selected) showing the effect of the selected subset. Not exactly as one should expect it, but with some imagination you may guess what it would look like. That is a very important feature to find out if glyphs like g/p/q b/d/h/k/l/t in your word might be conflicting with the ornamental feature. Alas in 1.0.1 one might click the execute button into infinity, it didn't do a thing.
in 1.1.1 there was no preview in the right column, nor was there on the bottom of the page. Knowing from the trial in 1.0.1 I needed subset ss06 I clicked execute and I got exactly the result I intended. After executing, the selection button sprung back to the main font column, so it is not pictured.
But, I deinstalled 1.0.1 as indicated on the download-page, so a next time I won't be able to preview and select. Nor can I use CorelDraw to find out, for it doesn't number the subsets. Only in FontForge can I find the specific subset number needed for a specific situation. Let's call that 'impractical'.
In OpenSUSE 15.x LEAP there is only an official rpm of Inkscape 0.92. That version shows only the line there are several features and there it stops. I set my hopes to Inkscape 1.x to finally make the change to linux, but so far that failed on this - for me essential - issue.
I did not report it then in 1.0.1 , my main use was CorelDraw at the time, and Inkscape converted the .cdr files with great precision to .svg (way better than CDR exported). The 0.92 version did fine on my linux system; the task it had to perform did not involve text, So I didn't notice the failure beforehand. Trying to install and run1.1.1 gave an issue beyond the context of this report, so I can't report on Inkscape's behaviour with font-features there.
Kind of weird BTW. that a top level search on fonts , otf, opentype and whatever I tried did not bring me to this dialog. Problem (not yet) solved, but a reoccuring, once solved problem gives me hope..
Inkscape 1.1.1 inkscape-1.1.1_2021-09-20_3bf5ae0d25-x64.msi installer
reproduceable on 2 win10 systems
coming from Inkscape 1.0.1 where the OTF features were pre-shown beforehand, preview on the selected option as expected, but not executed,
Now on my windows systems I installed v1.1.1.
This time the preview of the different options is not shown, not before nor after selecting a specific option.
When one clicks a known option, it is perfectly executed.
Alas from different fonts, with sometimes up to 10 alternative features, one can hardly know them all.
Where type is usually an essential part of e.g. logo design, fonts are often chosen with their subsets in mind, this might prove a serious issue.
I'd search the bug tracker to see if it's known: https://gitlab.com/inkscape/inkscape/-/issues
@TylerDurden Alas, that's where I started, But at inscribing they asked me so many things I could not relate to as a non-professional, that I thought first to try here,
Documentation by images could not be added here however.
In the meantime I found another remarkable issue, concerning the same (type of) font: the secondary font, "'fontname' shadow" is not listed in the font-list, does appear however in the textbox-controls as if it were a feature. It's not, but I couldn't care less, since it's/those are unusable without the main typeface.
That one could be applied in 1.0.1, in 1.1.1 it appears but can't be applied to the text's copy.
Now that you have been approved for two posts, you ma attach images. That could help.
I'm unfamiliar with using the font features, so I could use some guidance to try and replicate the issue. I have Win and Linux here.
It might help:
both images show an A4 page with the word 'tekst' on 1.1.1 and on 1.0.1 tekstt with the final t selected as it should be the one glyph that should get the feature.
in both versions you see in the feature settings the subsets and the glyphs they cover. You see a clear difference between ss01, ss04 and ss07.
In the 1.0.1 version you see a right column with the effect that choice may give on the text. In 1.1.1 that column equals the left column
In 1.0.1 at the bottom there is an example of the full word (only 1 glyph selected) showing the effect of the selected subset. Not exactly as one should expect it, but with some imagination you may guess what it would look like. That is a very important feature to find out if glyphs like g/p/q b/d/h/k/l/t in your word might be conflicting with the ornamental feature. Alas in 1.0.1 one might click the execute button into infinity, it didn't do a thing.
in 1.1.1 there was no preview in the right column, nor was there on the bottom of the page. Knowing from the trial in 1.0.1 I needed subset ss06 I clicked execute and I got exactly the result I intended.
After executing, the selection button sprung back to the main font column, so it is not pictured.
But, I deinstalled 1.0.1 as indicated on the download-page, so a next time I won't be able to preview and select. Nor can I use CorelDraw to find out, for it doesn't number the subsets.
Only in FontForge can I find the specific subset number needed for a specific situation. Let's call that 'impractical'.
In OpenSUSE 15.x LEAP there is only an official rpm of Inkscape 0.92. That version shows only the line there are several features and there it stops.
I set my hopes to Inkscape 1.x to finally make the change to linux, but so far that failed on this - for me essential - issue.
I did not report it then in 1.0.1 , my main use was CorelDraw at the time, and Inkscape converted the .cdr files with great precision to .svg (way better than CDR exported).
The 0.92 version did fine on my linux system; the task it had to perform did not involve text, So I didn't notice the failure beforehand.
Trying to install and run1.1.1 gave an issue beyond the context of this report, so I can't report on Inkscape's behaviour with font-features there.
There seem to be a few issues related to font features: https://gitlab.com/inkscape/inkscape/-/issues?label_name=Dialog%3A%3AText+and+Font
Maybe on is exactly the same as your issue and you can add your findings.
Thanks @TylerDurden ,
That's exactly where I wanted to get. https://gitlab.com/inkscape/inkscape/-/issues/1250 + 908 are the issues I could contribute to: this same problem in 1.0beta2
Kind of weird BTW. that a top level search on fonts , otf, opentype and whatever I tried did not bring me to this dialog.
Problem (not yet) solved, but a reoccuring, once solved problem gives me hope..