Smallcaps suggestions?

Discuss FontCreator here, please do not post support requests, feature requests, or bug reports!
MikeW
Posts: 504
Joined: Mon May 20, 2013 2:51 pm

Re: Smallcaps suggestions?

Post by MikeW » Mon Dec 18, 2017 6:38 am

One could make a small cap font be part of a family, but one normally wouldn't want to do that. If an application doesn't support small caps--which is the only reason to break out the small caps to another font--then it likely only supports the 4 main styles (regular, italic, bold, bold italic).

Before Unicode fonts with their limited character sets, one would name the font to include an SC in the file name, like in the screen shot below.
capture-001577.png
capture-001577.png (63.59 KiB) Viewed 89 times
Mike

Psymon
Posts: 223
Joined: Wed Mar 30, 2011 5:50 pm

Re: Smallcaps suggestions?

Post by Psymon » Mon Dec 18, 2017 8:50 pm

MikeW wrote:
Mon Dec 18, 2017 6:38 am
One could make a small cap font be part of a family, but one normally wouldn't want to do that. If an application doesn't support small caps--which is the only reason to break out the small caps to another font--then it likely only supports the 4 main styles (regular, italic, bold, bold italic).
Well, there's a LOT of software (if not most software) that doesn't support OT features, so isn't that a good reason to do a separate small caps version of one's font? Assuming one feels one's small caps are "important" enough, of course.
Before Unicode fonts with their limited character sets, one would name the font to include an SC in the file name
Um, I'm a bit confused, then. So is it possible to specify "Small Caps" (or "SC") as the sub-family of one's family of fonts? Or no? In the screenshot you provided, it does look like that's what the designer of Sabon did (is that your font?), but I don't know how they did that.

As it is, the only think I can think of to do re naming my small caps font is to call it that in the "Family" field of that naming dialog box -- but that then makes it an entirely separate font when I go to use it in Photoshop (or wherever), of course.

MikeW
Posts: 504
Joined: Mon May 20, 2013 2:51 pm

Re: Smallcaps suggestions?

Post by MikeW » Mon Dec 18, 2017 9:12 pm

The reason for a separate small cap font is just for those applications to be able to select it from the menu if they do not support a full-family listing and/or not support a small cap feature. Many/most recently made fonts do not provide separate fonts except by request. That I agree with.

Yes, one can make it all hang into a family. But if the application in question doesn't support small caps as an OT Feature, it also may not support larger than the typical 4 font family, either.

Psymon
Posts: 223
Joined: Wed Mar 30, 2011 5:50 pm

Re: Smallcaps suggestions?

Post by Psymon » Mon Dec 18, 2017 9:25 pm

MikeW wrote:
Mon Dec 18, 2017 9:12 pm
The reason for a separate small cap font is just for those applications to be able to select it from the menu if they do not support a full-family listing and/or not support a small cap feature. Many/most recently made fonts do not provide separate fonts except by request. That I agree with.
Why do you agree with that? I suppose it would be nice if software was moving more toward supporting OT features and stuff, but it doesn't seem to be that way -- not that I've seen, anyway (although I'm hardly a software reviewer, of course).
Yes, one can make it all hang into a family. But if the application in question doesn't support small caps as an OT Feature, it also may not support larger than the typical 4 font family, either.
Oh, okay. Well, it's too bad, it would have been nice to keep all my fonts together in the same family, but if it's not practical, then oh well.

Thanks for the replies, Mike! :)

MikeW
Posts: 504
Joined: Mon May 20, 2013 2:51 pm

Re: Smallcaps suggestions?

Post by MikeW » Mon Dec 18, 2017 9:39 pm

Bear with me...

What Apple did with the Mac throughout its history is both a blessing and a curse. That is, they really don't give a hoot about supporting old software unless their OS advancements simply allowed them to work.

What Microsoft has done throughout its history until Windows 10 (mainly) is to always attempted backward support capabilities. This too is a blessing and a curse. I feel it is mainly a curse, though. It has historically kept Windows from advancement and provided a main source of bloat.

As for fonts, I don't really care about supporting antiquated or poorly written software as long as the 255 character set works properly in such software. My feeling is that if people want access to such features like small caps (or whatever) they ought to buy software (both the OS and applications) that supports it. Failing that, they can request the separate fonts. They would appear in the menu following the main styles. But I won't accommodate such software right from the start.

My font clients are not John Q. Public. They are mainly publishers and some other designers. I have made changes (additions, really) in certain OT Features so that they can be accessed in an application such as InDesign (ID doesn't support the hist feature, for instance. So I copied the code into a Stylistic Set for them). They tend to use software that supports OT Features no matter how old that software is.

I do have a few families I am thinking about releasing to the public. I will not, however, break out the features such as small caps into a secondary font initially.

Post Reply

Who is online

Users browsing this forum: No registered users and 1 guest