Script defaults to DFLT

[tiroj]

When testing Latin text strings in a font that includes a DFLT script tag as well as a latn one, the Automatic setting in the Script field presumes DFLT instead of latn, meaning that the language systems associated with the latn script tag do not show up in the Language field. I have to manually select the latn entry in the Script field.

[justvanrossum]

I'm not sure I follow 100%. It may be that the UI behavior is confusing. Or indeed buggy.

The popups do not respond dynamically to the contents fo the text string displayed.

The Language popup only shows the languages for an explicitly selected Script, so when Script is set to Automatic, I don't expect to find anything interesting in the Languages popup.

In other words, to have to manually select the latn entry in the Script field before you can see the available languages is to be expected.

When Script is set to Automatic, FG will do segmenting based on detected scripts and bidi properties, so there isn't a single "automatic" Script per se: it could be several.

[tiroj]

Thanks, that makes more sense now.

I'm trying to imagine a UI that would enable one to select individual language system settings per script and have those apply to different parts of a multi-script string using the Script=Automatic setting. Then again, maybe I'm the only person to whom tha would appeal.

[arrowtype]

This also confused me – I didn’t think the locl feature I was working on was registering.

Maybe this is a dumb idea, but maybe the “Script” and “Language” selections could be combined into a single menu, to make this more obvious? After all, this is how they are registered in feature syntax, right?

languagesystem DFLT dflt;
languagesystem latn dflt;
languagesystem latn ROM;
languagesystem latn CAT;
# etc

[justvanrossum]

That's not a bad idea, and might also have prevented John confusion!