MRQ PDF Now Available!

Thanks Archer.

Font is now installed (it still doesn't say embedded?) and the chapter titles do indeed look just like the ones in the book now.

Any idea why Helvetica and Symbol aren't labelled as embedded subsets in the document properties?

Are they missing fonts too?
 
Sigtrygg said:
Thanks Archer.

Font is now installed (it still doesn't say embedded?) and the chapter titles do indeed look just like the ones in the book now.

It wont say that. Embedded means they are part of the .pdf document, and you do not have to install them to get the document to look as it is supposed to.

Sigtrygg said:
Any idea why Helvetica and Symbol aren't labelled as embedded subsets in the document properties?

Are they missing fonts too?

They are missing from being part of the document yes. But they might be default system fonts, and as such it is not a big problem. Helvetica should not be a problem, but Symbol could be, depending on what symbol font that is (there are not few such fonts, namned just Symbol).

I really think Mongoose should make the effort to embedd the required fonts in the .pdf.
 
Archer said:
I really think Mongoose should make the effort to embedd the required fonts in the .pdf.

I agree. I hope that do in the next release of the core rules and of future releases.

As a tip there is an option on Drivethrurpg to get an email notification if there are changes to the product. It is on the sidebar on the right of the product page for RQ.
 
Please note that not all fonts are embeddable - some contain copy protection to prevent their being distributed even in "embedded only" form.

If that was the problem, I would guess in the argument of additional size to print them as graphics or leaving them as a normal font the argument to keep the PDF size down won.
 
You can get permission to embedd fonts, by contacting the (C) holder.

To change the fonts permissions are easily done enough (with Fontlab from http://www.fontlab.com/index.php). So it becomes more a question about getting the permission from the creator of the font.

Note, if Mongoose do not have the rights to embedd the font in .pdfs, I suspect tha they do not have right to use it when publishing something in print either. These two things usually go hand in hand.
 
Archer said:
These two things usually go hand in hand.

I've got a few fonts where the creator is quite happy to have the things used in the creation of any work, but does not want the font distributed in digital format within PDFs for fear of someone decrypting and extracting it. Seems a bit far to go when anyone can just copy the original font file though :)
 
mthomason said:
Archer said:
These two things usually go hand in hand.

I've got a few fonts where the creator is quite happy to have the things used in the creation of any work, but does not want the font distributed in digital format within PDFs for fear of someone decrypting and extracting it. Seems a bit far to go when anyone can just copy the original font file though :)

With newer software for creating .pdfs, only the parts that is needed from the font are included, just for that reason.

Some fonts are as you say, allowed to use in print, but not digital publishing. That is why you have to get hold of the (C) holder and try to get the permission for it.

Some sites that sell fonts allow you to directly buy the font with different licenses, depending on what you want to do with it (embedding etc.).
 
Back
Top