Save As a Package and exclude individual fonts.

[Old Bruce]

In order to comply with various font EULAs please let us choose whether or not to include restricted fonts when we make a package. As things stand we can include all the fonts or none of the fonts. The dialog will show us which fonts are restricted but then we have to either exclude all fonts or enter into the package folder and selectively find and remove the restricted fonts.

[walt.farrell]

It might also be useful to be able to exclude restricted fonts individually (including some, omitting some) if you know that you have the rights for some of the fonts.

And along that line, it would be useful if the dialog would display the font license information, which many fonts contain, to help you make the right decision based on the use that will be made of the document package.

[Old Bruce]

2 minutes ago, walt.farrell said:

display the font license information, which many fonts contain,

And many don't. This will lead to "But it didn't say I cannot do this..."

[Alfred]

2 hours ago, walt.farrell said:

display the font license information, which many fonts contain,

 

2 hours ago, Old Bruce said:

And many don't. This will lead to "But it didn't say I cannot do this..."

Please show us a font that doesn’t include embeddability flags.

[William Overington]

13 hours ago, Alfred said:

Please show us a font that doesn’t include embeddability flags.

But that was not claimed.

I looked in FontCreator and there is a field that is called, at least in FontCreator, I don't know about elsewhere, License Agreement.

The Arial font installed on my computer has a panelful of text in the License Agreement field, my Chronicle Text font has nothing in that field.

http://www.users.globalnet.co.uk/~ngo/CHRONTXT.TTF

The details of the embedding flags are in the following document.

https://docs.microsoft.com/en-us/typography/opentype/spec/os2

Please search for

embed

I got 35 results, but they are all in the same section, so no great problem that there are 35 of them.

William

 

[walt.farrell]

14 hours ago, Alfred said:

Please show us a font that doesn’t include embeddability flags.

It sounds like some kind of embeddability flag is required by the architecture of the file. And yes, it would be helpful to have that displayed, too.

[kenmcd]

REQUIRED field - fsType - Indicates font embedding licensing rights for the font.

NOT-REQUIRED fields - License Description, License Info URL

[walt.farrell]

2 hours ago, LibreTraining said:

REQUIRED field - fsType - Indicates font embedding licensing rights for the font.

NOT-REQUIRED fields - License Description, License Info URL

Sorry, but based on the other topic that spawned this one, all are needed. See from this post for a demo of why fsType is not sufficient:

 

[MikeW]

35 minutes ago, walt.farrell said:

Sorry, but based on the other topic that spawned this one, all are needed. See from this post for a demo of why fsType is not sufficient:

Not really. I doubt any application would parse a license description or go to a website. Those fields are optional.

[walt.farrell]

1 hour ago, MikeW said:

Not really. I doubt any application would parse a license description or go to a website. Those fields are optional.

I'm not asking the application to parse anything. I'm asking the application to display them if they're available, so the user has a chance of understanding their obligations.

[MikeW]

8 minutes ago, walt.farrell said:

I'm not asking the application to parse anything. I'm asking the application to display them if they're available, so the user has a chance of understanding their obligations.

I think it would be a fool's errand to take the time to program the feature. And all for little gain.

Too many fonts have only a brief license description if anything at all. Some include a website, many do not. Rarely will a font contain a full copy of a license. 

[William Overington]

17 minutes ago, walt.farrell said:

I'm not asking the application to parse anything. I'm asking the application to display them if they're available, so the user has a chance of understanding their obligations.

You could try opening the font in WordPad on a computer that is running Windows, and then scroll down to near the end of the file.

Some of what is displayed is in plain text.

Or you could use High-Logic FontCreator to display the text.

FontCreator is not only useful for generating new original fonts but is also useful for inspecting such text and which glyphs are in a font and so on while not altering the font at all.

William

 

[kenmcd]

2 hours ago, walt.farrell said:

Sorry, but based on the other topic that spawned this one, all are needed. See from this post for a demo of why fsType is not sufficient:

Sorry @walt.farrell my mini post was not clear.
That is what is or is not required inside a font file.
My point being that the embedding info is always going to be available to display to users,
but the license fields are not required so they may or may not be there to display.

[William Overington]

I asked in a specialist font format mailing list and a reply from an expert has been received.

https://lists.aau.at/pipermail/mpeg-otspec/2022-March/date.html

William

 

[Alfred]

19 minutes ago, William Overington said:

I asked in a specialist font format mailing list and a reply from an expert has been received.

https://lists.aau.at/pipermail/mpeg-otspec/2022-March/date.html

TL;DR

Quote

In reality, [it] is rarely the case [that a font file includes its license info], because the same font can be licensed to different entities for different types of use under very different licenses. In the majority of cases, the license rights are specified in the agreement that is signed when a font is acquired, and its conditions are binding.

For maximum flexibility, it’s common for the licensing info to be included in a separate file in the distribution package.