@typeglyph said in Typography Panel Bug?:
About the “defaults”. Two items here really. It used to be that when you started a program, Pagemaker, Freehand, Quark, Illustrator, Photoshop etc. before you opened any document to work on, you could set your programs’, preferences. Close the program and re-open it to see your changes as the new default for any new document you start.
This is how it works in VS also. Including most options set in document setup, etc for new documents.
More on defaults, for example why are the colour spaces defaulting to the “shitty” RGB colour space (sRGB) instead of some thing more robust and with a wider gamut of colours?
I think that sRGB is a common color space, especially for design intended for the web. Of course it has a reduced gamut (web).
When we teach about colour spaces we often direct students to use the Adobe(1998) colour space, and no longer use any of the CMYK or other RGB spaces.
Not being an Adobe program, the Adobe color spaces can be selected if available in the OS or installed separately.
But as an aside look at the construction of the word: de·fault. The word “de” is often defined as OF or demoting and the word “fault” often connotes a MISTAKE. So a program coder [programmer] who sets defaults rigidly is actually setting up the program to use mistakes.
I tried to avoid as many defaults to be rigid. Most are configurable, even as some are not exposed to the user (i.e. can be easily added to preferences if needed).
For fonts, the default (for now) is to keep the current enabled feature set from the previous font. So when a font (typeface) is changed, the feature set will remain the same (even if not supported), and must be selected separately.
