Are font subsets embedded by default?

42 views
Skip to first unread message

P Toost

unread,
Dec 12, 2013, 9:40:26 PM12/12/13
to prawn...@googlegroups.com
We have an issue which might be related to Prawn embedding font subsets.

Is this the default behavious and, if so, is there any way to force Prawn to embed the full font?

Thanks
Nick

Gregory Brown

unread,
Dec 13, 2013, 11:46:26 AM12/13/13
to prawn...@googlegroups.com
The default behavior is to subset, yes. I don't believe we have the
option to embed the full font.

I'm trying to think of a use case where that would be desirable, but
can't think of one. Can you tell me why you'd want the full font
rather than subsets?

-greg
> --
> You received this message because you are subscribed to the Google
> Groups "Prawn" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to prawn-ruby+...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.

P Toost

unread,
Dec 13, 2013, 6:45:17 PM12/13/13
to prawn...@googlegroups.com
Thanks for the quick response Greg.

It's far from desirable, that's for sure.

We are producing large'ish batches of letters that go to a commercial mail house for printing. They collate the batches into merged document streams to send through their printers.

Apparently, the large numbers of font subsets contained in their merged streams are causing their printer to run out of memory. They said if we could embed the full fonts than, I think, they would keep just one full font set and discard the others.

I think it's a problem they should solve when doing the merge by combining the subsets into one set, but, as timeframes are currently tight, I was looking to see if we could do anything (at least in the short term) to speed up the resolution.

Gregory Brown

unread,
Dec 13, 2013, 6:57:36 PM12/13/13
to prawn...@googlegroups.com
I wish I could offer more in the way of support here, but when I wrote
TTFunk, it didn't have subsetting at all. Jamis Buck added all of the
subsetting stuff later, but even that was five years ago.

There is no conceptual reason why I'd not want to make it possible to
disable subsetting, even though it does appear to be a bit of an edge
case. But I remember far too little about the internals to give you a
reasonable suggestion on how to go about doing that.

If anyone on the list has a better memory than me or wants to throw some
ideas out there, please do.

-greg
> > an email to prawn-ruby+...@googlegroups.com <javascript:>.
> > For more options, visit https://groups.google.com/groups/opt_out
> <https://groups.google.com/groups/opt_out>.
Reply all
Reply to author
Forward
0 new messages