It looks like you're new here. Sign in or register to get started.
Peter Baker said:
My understanding (not sure I remember it exactly) is that the presence of a Reserved Font Name would require that the name be changed if the font was subsetted for a PDF or a web page--subsetting being a kind of alteration. Since GF does a lot of subsetting when serving fonts . . . you see the difficulty. In an operation like GF, it's not desirable to serve fonts with the names obfuscated.
@John Hudson, really? I thought the primary purpose of the reserved font name clause was to prevent caching issues. It's a problem for end users more than for designers. It seems like a bad idea to me to not require name changes.
Daniel Benjamin Miller said:
I thought that the name only needed to be changed if the font were being distributed as a standalone font file, as opposed to embedded in a PDF or the like (and potentially as a subset). This was the same reason why you could embed the font in a PDF without having to include a full copy of the license in your document — or maybe I have a misunderstanding of the OFL on this point.