Font Mangling
| Project: | EPUB Maintenance |
| Component: | Open Publication Structure (OPS) |
| Category: | feature request |
| Priority: | normal |
| Assigned: | GConboy |
| Status: | completed @ 2.0.1 |
Jump to:
I'd think the Font Mangling Informational Document should be incorporated into the embedded-font section of OPS. IN the spirit of "if you want to mangle fonts, you should do it this way."
Description
Issue Id:
27
Resolution:
During 2.0.1 spec maintenance pass, include a non-normative list of approved extensions -- reference the font mangling informational document from OCF.
- Login to post comments
Comments
#1
Brady points out that this is really and OCF thing, not OPS. He's probably correct.
#2
I agree that it should.
#3
I agree that how you mangle the font is related to OCF, not OPS.
It's also an example of how you can use specific files defined in the OPS specs rather than part of the specs themselves. Seems more suited for an individual document from my point of view. Maybe we should start a document for EPUB in general, that would tie all three specs together ?
#4
True. There is another task (that I own) that involves linking all three specs (OCF, OPS & OPF) to EPUB -- each being a third. I'd prefer to see font mangling in OCF, as if you're going to cross-platform mangle fonts this is the way to do it. It touches the package file as well as "encryption.xml" and I think we should cover it appropriately.
#5
I wouldn't want to see more than a reference to the document in OCF, if that. OCF was designed to be extensible, and this is just one possible extension. I don't see it as the only way to embed fonts, just the preferred way if it is sufficient for your needs. Adding it to the spec sets a precedent for adding all extensions we might define to the spec. This really seems like an informational document, of which there may be many more.
I also wouldn't say it "touches the package file". It does use an element that is already defined in the package file, but it doesn't change anything about the package, and the element is used in exactly the way it is defined in the OPF spec (as the unique identifier of the package).
#6
Will become proposed resolution -- include a non-normative list of approved extensions -- reference the font mangling informational document from OCF in the 2.0.1 spec pass.
#7
Moved to "Proposed resolution". Status will become "accepted" to indicate that changes to reference the Font Mangling Informational Document will be made in the 2.0.1 pass.
#8
Moved to "accepted."
#9
Good move. I am supporting this.
*Doing this at my desk at our paper writing service company.
#10