You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The subsetting functionality was originally driven by the needs of embedding fonts in PDFs in Prince. In this context a number of tables are not required due to being handled by the PDF document or by processing that done as part of generating the PDF.
Ideally we'd like the subsetting functionality to be useful outside the PDF context as well. This will necessitate including all tables required by OpenType. At the same time we don't want to unnecessary increase the size of our customers PDFs by including unnecessary tables. So, there needs be a way to control the tables that are included when subsetting fonts in order to support both use cases. I'm imagining this would be implemented along these lines:
The subsetting function accepts a list of tables to include in the output font.
There is a pre-defined list of tables that can be supplied to produce a valid OpenType font. We could define our own predefined list of tables for use with Prince.
The subsetting functionality was originally driven by the needs of embedding fonts in PDFs in Prince. In this context a number of tables are not required due to being handled by the PDF document or by processing that done as part of generating the PDF.
Ideally we'd like the subsetting functionality to be useful outside the PDF context as well. This will necessitate including all tables required by OpenType. At the same time we don't want to unnecessary increase the size of our customers PDFs by including unnecessary tables. So, there needs be a way to control the tables that are included when subsetting fonts in order to support both use cases. I'm imagining this would be implemented along these lines:
E.g.
The text was updated successfully, but these errors were encountered: