This is also done with another meta element. To do that, the metadata.opf file will also have to define a collection, and mark the book as a member of it. However, it should be noted that even this doesn't actually specify which book in the trilogy it would be, or group it together with other books that it might belong with. I don't believe any apps make use of this though, so it's mostly theoretical. This would make the app think that the full title might be something like Stargate SG-1: The Defective Gates Trilogy, A Dribble of Event Horizon: When Good Wormmholes Go Bad. Again, each will reference the title's id directly. This tells the app which order to display those titles in. It is also possible to use the schema attribute to specify a new list of title-types, though I still haven't managed to make sense of that yet.Īdditionally, there should probably be a "display-seq" meta element for each title. Those are "main, subtitle, short, collection, edition and expanded".īut, one might also use "series" and "franchise" and have it be close to the formal spec. The trouble is, of course, that there are only a few recognized title-types. Each title element needs its own (arbitrary) unique id, and each meta element will reference that. For each of the "titles", you'd include a title element along with a meta element to specify which sort of title it is. The correct way to include these according to the EPUB 3.2 standard is as follows.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |