When a scheme is identified, a subject code MUST be attached using the term property. The values of the subject element and term property are case sensitive only when the designated scheme requires. As child of the metadata element.
Each meta element defines a metadata expression. The property attribute takes a property data type value that defines the statement being made in the expression, and the text content of the element represents the assertion.
Refer to Vocabulary Association Mechanisms for more information. This specification defines two types of metadata expressions that can be defined using the meta element:.
Subexpressions are not limited to refining only primary expressions and resources; they may be used to refine the meaning of other subexpressions, thereby creating chains of information. This specification reserves the Meta Properties Vocabulary for use with the property attribute.
Terms from other vocabularies MAY be used provided they have a prefix refer to Reserved Prefixes for a list of prefixes that do not have to be declared.
The scheme attribute identifies the system or scheme that the element's value is drawn from. The value of the attribute MUST be a property data type that resolves to the resource that defines the scheme.
Unless an individual property explicitly defines a different white space normalization algorithm, Reading Systems MUST trim all leading and trailing white space [ XML ] from the meta element values before further processing them. Every meta element MUST express a value that is at least one character in length after white space normalization.
The link element is used to associate resources with the given Rendition , such as metadata records. As a child of metadata. Reading System do not have to use or present linked resources, even if they recognize the relationship defined in the rel attribute. The value of the media-type attribute is not always sufficient to identify the type of linked resource e. To aid Reading Systems in the identification of such generic resources, the properties attribute can be attached with a semantic identifier.
Authors MAY add relationships and properties from other vocabularies via the metadata extensibility mechanism defined in this specification. Authors also MAY create new values by defining their own prefixes. Linked records are intended to enhance the information available to Reading Systems, and the package metadata typically contains important rendering information. Reading Systems MAY compile metadata from multiple linked records; they do not have to select only one record.
When it comes to resolving discrepancies and conflicts between metadata expressed in the Package Document and in linked metadata records, Reading Systems MUST use the document order of link elements in the Package Document to establish precedence i. Due to the variety of metadata record formats and serializations that can be linked to an EPUB Publication, and the complexity of comparing metadata properties between them, this specification does not require Reading Systems to process linked records.
The manifest element provides an exhaustive list of the Publication Resources that constitute the given Rendition , each represented by an item element. This specification supports internationalized resource naming, so elements and attributes that reference Publication Resources accept IRIs as their value. The item element represents a Publication Resource. As a child of manifest. Fallback requirements for Foreign Resources are defined in Manifest Fallbacks.
Authors MUST declare all applicable descriptive metadata properties for each Publication Resource in this attribute, as Reading Systems MAY optimize the rendering depending on the properties that have been set e. Refer to Packaging [ MediaOverlays32 ] for more information. The order of item elements in the manifest is not significant.
The presentation sequence of content documents is provided in the spine. The following example shows a manifest that contains only Core Media Type Resources. Foreign Resources MAY be referenced in contexts in which an intrinsic fallback cannot be provided e. Manifest fallbacks MUST be provided in such cases. Manifest fallbacks are provided using the fallback attribute on the manifest item element that represents the Publication Resource.
This fallback item MAY itself specify another fallback item , and so on. The ordered list of all the ID references that can be reached starting from a given item's fallback attribute represents the fallback chain for that item.
The order of the resources in the fallback chain represents the Author's preferred fallback order. A Reading System that does not support the Media Type of a given Publication Resource MUST traverse the fallback chain until it has identified at least one supported Publication Resource to be used in place of the unsupported resource.
If a Reading System does not support any resource in the fallback chain, it MUST alert the reader that content could not be displayed. Fallback chains MUST conform to one of the following requirements, as appropriate:.
User agents MUST terminate the fallback chain at the first reference to a manifest item that has already been encountered. An example of when this feature can be utilized is when providing fallbacks for scripted content [ ContentDocs32 ]. The bindings element defines a set of custom handlers for media types not supported by this specification. Its use is deprecated. Refer to [ Publications ] for more information about this element.
The spine element defines an ordered list of manifest item references that represent the default reading order of the given Rendition. Reading Systems MUST provide a means of rendering the Rendition in the order defined in the spine , which includes: 1 recognizing the first primary itemref as the beginning of the default reading order; and, 2 rendering successive primary items in the order given in the spine.
All Publication Resources that are hyperlinked to from Publication Resources in the spine MUST themselves be listed in the spine , where hyperlinking is defined to be any linking mechanism that requires the user to navigate away from the current resource.
Common hyperlinking mechanisms include the href attribute of the [ HTML ] a and area elements and scripted links e. The requirement to list hyperlinked resources applies recursively i. As Remote Resources referenced from hyperlinks are not Publication Resources, they are not subject to the requirement to include in the spine e. Embedded Publication Resources e.
The page-progression-direction attribute sets the global direction in which the content flows. Allowed values are ltr left-to-right , rtl right-to-left and default. When the default value is specified, the Author is expressing no preference and the Reading System can choose the rendering direction. The default value MUST be assumed when the attribute is not specified. In this case, the reading system SHOULD choose a default page-progression-direction value based on the first language element.
Although the page-progression-direction attribute sets the global flow direction, individual Content Documents and parts of Content Documents MAY override this setting e. Reading Systems MAY also provide mechanisms to override the default direction e. The page-progression-direction attribute defines the flow direction from one fixed-layout page to the next. The order of the itemref elements defines the default reading order of the given Rendition.
As a child of spine. The linear attribute indicates whether the referenced item contains content that contributes to the primary reading order and has to be read sequentially " yes " or auxiliary content that enhances or augments the primary content and can be accessed out of sequence " no ". Examples of auxiliary content include: notes, descriptions and answer keys. The linear attribute allows Reading Systems to distinguish content that a user needs to access as part of the default reading order from supplementary content which might, for example, be presented in a popup window or omitted from an aural rendering.
This specification does not mandate which model Reading Systems have to use. Each Rendition MUST include at least one itemref whose linear attribute value is either explicitly or implicitly set to " yes ". An itemref that omits the linear attribute is assumed to have the value " yes ". Authors MUST provide a means of accessing all non-linear content e.
Terms from any other vocabulary MAY be used provided they have a prefix refer to Reserved Prefixes for a list of prefixes that do not have to be declared. Reading Systems MUST ignore all metadata properties expressed in the properties attribute that they do not recognize.
In this order: metadata [0 or 1] , collection [1 or more] or collection [0 or more] , link [1 or more]. The collection element allows resources to be assembled into logical groups for a variety of potential uses: enabling content that has been split across multiple EPUB Content Documents to be reassembled back into a meaningful unit e.
The collection element, as defined in this section, represents a generic framework from which specializations are intended to be derived e. Such specializations MUST define the purpose of the collection element within a Rendition, as well as all requirements for its valid production and use specifically any requirements that differ from the general framework presented below.
Each specialization MUST define a role value that uniquely identifies all conformant collection elements. No roles are defined in this section. To facilitate interoperability of custom roles across Reading Systems, implementers are strongly encouraged to document their use of the collection element in [ RoleExtensions ].
The OPTIONAL metadata element child of collection is an adaptation of the package metadata element, with the following differences in syntax and semantics:. Package-level restrictions on the use of metadata elements MAY be overridden. All primary metadata expressions apply to the collection. A collection MAY define sub-collections through the inclusion of one or more child collection elements. The link element child of collection is an adaptation of the metadata link element, with the following differences in syntax and semantics:.
The properties attribute also accepts manifest item properties without a prefix e. Each link element MUST reference a resource that is a member of the group. The order of link elements is not significant. Specializations of the collection element MAY tailor the requirements defined above to better reflect their needs e. However, the resulting content model MUST represent a valid subset of the one defined in this section e.
The content MUST remain consumable by a user without any information loss or other significant deterioration. The meta element [ OPF2 ] is a legacy feature that previously provided a means of including generic metadata. It is replaced in EPUB 3 by the updated meta element , which uses different attributes and requires text content. For more information about the meta element, refer to its definition in [ OPF2 ].
For more information about the guide element, refer to its definition in [ OPF2 ]. This Unique Identifier , whether chosen or assigned, MUST be stored in the dc:identifier element and be referenced as the Unique Identifier in the package element unique-identifier attribute. Determining whether two EPUB Publications with the same Unique Identifier represent different versions of the same publication see Release Identifier , or different publications, might require inspecting other metadata, such as the titles or authors.
Each release of an EPUB Publication normally requires that the new version be uniquely identifiable, however, which results in the contradictory need for reliable Unique Identifiers that are changeable. To redress this problem of identifying minor modifications and releases without changing the Unique Identifier, this specification defines the semantics for a Release Identifier , or means of distinguishing and sequentially ordering EPUB Publications with the same Unique Identifier.
The Release Identifier is not an actual property in the package metadata section, but is a value that can be obtained from two other mandatory pieces of metadata: the Unique Identifier and the last modification date of the Rendition. When the taken together, the combined value represents a unique identity that can be used to distinguish any particular version of an EPUB Publication from another.
Although not a part of the package metadata, for referencing and other purposes all string representations of the identifier MUST be constructed using the at sign as the separator i. The Release Identifier consequently MUST be split on the last instance of the at sign when decomposing it into its component parts. The Release Identifier does not supersede the Unique Identifier, but represents the means by which different versions of the same EPUB Publication can be distinguished and identified in distribution channels and by Reading Systems.
The sequential, chronological order inherent in the format of the timestamp also places EPUB Publications in order without requiring knowledge of the exact identifier that came before. When an EPUB Container includes more than one Rendition of an EPUB Publication, updating the last modified date of the default rendition for each release — even if it has not been updated — will help ensure that the EPUB Publication does not appear to be the same version as an earlier release, as Reading Systems only have to process the default rendition.
The property , properties , rel and scheme attributes use the property data type to represent terms from metadata vocabularies. A property value is an expression that consists of a prefix and a reference, where the prefix — whether literal or implied — is a shorthand mapping of an IRI that typically resolves to a term vocabulary. To assist Reading Systems in processing property values, this specification defines three mechanisms to establish the IRI a prefix maps to:.
A default vocabulary is a vocabulary that does not require a prefix to be declared in order to use its terms, and whose terms MUST always be unprefixed. As the Package Document has multiple unrelated uses for metadata terms, a single default vocabulary is not defined for all attributes. Instead, different default vocabularies are defined for use in attributes that accept a property data type as follows:. The Meta Properties Vocabulary is defined to be the default vocabulary for the meta property attribute.
The Metadata Link Vocabulary is defined to be the default vocabulary for the link rel and properties attributes. The Manifest Properties Vocabulary is defined to be the default vocabulary for the item properties attribute. The Spine Properties Vocabulary is defined to be the default vocabulary for the itemref properties attribute. This specification reserves the following set of prefixes that Authors MAY use in package metadata without having to declare.
Although reserved prefixes are an authoring convenience, reliance on them can lead to interoperability issues. Validation tools will often reject new prefixes until the tools are updated, for example. Authors are strongly encouraged to declare all prefixes they use to avoid such issues. The prefix attribute defines additional prefix mappings not reserved by this specification.
The value of the prefix attribute is a white space-separated list of one or more prefix-to-IRI mappings of the form:. If the prefix attribute includes a declaration for a predefined prefix , Reading Systems MUST use the URI mapping defined in the prefix attribute, regardless of whether of it maps to the same URI as the predefined prefix. After processing , this property would expand to the following IRI:. When a prefix is omitted from a property value, the expressed reference represents a term from the default vocabulary for that attribute.
An empty string does not represent a valid property value, even though it is valid to the definition above. If the property consists only of a reference, the IRI is obtained by concatenating the IRI stem associated with the default vocabulary to the reference. If the property consists of a prefix and reference, the IRI is obtained by concatenating the IRI stem associated with the prefix to the reference. The Calibre "Annotations" will help you import highlights, notes, and other annotations from supported eBook readers and platforms.
How cool it is to pull your annotations made on your device and add them to your calibre library! The supported devices and platforms include: Kindle - annotations fetched from "My Clippings. Kobo eReaders - annotations fetched from database. Tolino eReaders - annotations fetched from notes.
Download Annotations V1. Are you running of Calibre screen space on your toolbar from adding plugins? Then probably you need Favourites Menu to help you. It lets you create a customized toolbar menu button with your favourite menu options.
Also, you can add specific menu actions, submenus, or entire plugins to your own menu. In a word, this plugin helps you to save screen space. Download Favourites Menu V1. Count Pages is a very useful Calibre plugin that will count the pages in a book, tell you how many words are in the file, and store the result in a custom column.
Download Count Pages V1. However, the whole process can be very complicated and difficult. Why not give it a try? Never, fear if you prefer the old icons they are also available, as an icon theme. Alongside the support for conversion from Word, you can now go back and forth between Word documents and e-book formats to your hearts desire.
This is an appropriate time to throw out a big thank you to the calibre community who have contributed selflessly of their energy and enthusiasm — without which many of the features above would never have seen the light of day. Note that some of these features were actually introduced during the lifetime of the 2. This document describes new features as compared to 2. See what was new in previous major calibre releases: 2.
New in calibre 3. There are a few minor backwards incompatibilities to be aware of in calibre 3. The Content server was completely re-written. While we have tried hard to make sure the functionality used by third party programs that connect to calibre remains compatible, there is likely to be some breakage.
Also, no changes you have made to any server options will be preserved.
0コメント