I have encountered a problem in Photoshop concerning .case-forms of parentheses. I can set them via the glyphs panel in InDesign, via the alternative glyphs dropdown and so on. But I can’t make them appear in Photoshop. Even if I set the text to all caps or use the dropdown menu accessing the alternatives. I really don’t know why this happens.
The only thing you need to make sure is that case is represented in aalt, updating features should be enough for that. Then reexport and make sure Photoshop has the right version of the font. Are you using the Adobe Fonts folder?
Oh, and update all your Adobe apps to the latest version. They were struggling with font support in many of their apps last year.
If it still doesn’t work, you have probably found a Photoshop bug.
Thank you, case is represented in aalt. It still won’t work, even with the latest version of Photoshop. Also, Photoshop will only do fake superscript numbers, not the .sups ones I specifically designed. I can’t set them via the aalt dropdown menu at the bottom of the number. I have also tried an alternative way to get it to work by setting up all the .sups glyphs I want to have available as a stylistic set, but even InDesign won’t do it. I feel like I haven’t forgotten anything on the font side, so I am really wondering what’s up with the Adobe programs. Or is there something wrong with my file?
240904_toom Sans.glyphs (163.5 KB)
Don’t know about Photoshop, but InDesign does support superscript and subscript figures. Make sure you have the latest version of the Adobe apps. There were a lot of bugfixes a few months ago.
Hi Max. I just tested your file in Photoshop and confirm that case (for example, a versions of parenleft/right that are shorter vertically) doesn’t work in Photoshop. I also compared your file with one of mine (where case works in Photoshop correctly), and both case and aalt features are presented in the same way. Looks like something with the file, but what exactly…
As far as I can tell from a quick test in InDesign, almost none of your features work at all – sub- and superscripts, numerators and denominators, ordinals, tabular/proportional numbers, or stylistic sets. The only features I can get to work are the default ligatures (fi and fl, though it’s hard to tell since the ligatures look the same as the non-ligatured forms) and the substitution íj → íȷ́ in Dutch – everything else does nothing at all. So there’s definitely something wrong somewhere in the font itself.
Thank you for looking into it. Is there any way I can quickly find out what exactly is wrong? My client wants to get things done and use the new font but I have to make sure it works properly. I don’t know what to look for at this point …
I have updated everything. The features look alright. Everything is named properly. Still nothing. What else could cause this?
Can you check whether fontbakery.com complains about anything feature-related?
1 Like
Wow I have never heard of this site, thank you!
can you set the “Languagesystems” to “Generate feature automatically”.
1 Like
Huh, I did that when testing before and it had no effect – but when I did it just now (on my laptop), it fixed things…
LOL now it works. All the features seem to work. Sorry for bothering you and not checking this little box.
