Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
Browse files

add cover; change name of ebook

  • Loading branch information...
commit f8069240f5a01c50c26192eda28cfdc93faecf15 1 parent 786aed0
@WalterBright WalterBright authored
Showing with 490 additions and 11 deletions.
  1. +140 −0 dlangspec.opf
  2. +339 −0 dlangspec.png
  3. +11 −11 win32.mak
View
140 dlangspec.opf
@@ -0,0 +1,140 @@
+<?xml version="1.0" encoding="utf-8"?>
+<!--
+ The unique identifier in <package unique-identifier=”XYZ”> is a reference to
+ the identifier specified in <metadata> as <dc:Identifier id=”XYZ”>.
+-->
+<package xmlns="http://www.idpf.org/2007/opf" version="2.0" unique-identifier="BookId">
+
+<!--
+ Metadata:
+ The required metadata element is used to provide information about the publication
+ as a whole.
+
+ For detailed info visit: http://www.idpf.org/2007/opf/OPF_2.0_final_spec.html#Section2.2
+-->
+
+<metadata xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:opf="http://www.idpf.org/2007/opf">
+
+ <!-- Title [mandatory]: The title of the publication. This is the title that will appear on the "Home" screen. -->
+
+ <dc:title>D Programming Language Specification</dc:title>
+
+ <!-- Language [mandatory]: the language of the publication. The language codes used are the same as in XML
+ and HTML. The full list can be found here: http://www.w3.org/International/articles/language-tags/
+ Some common language strings are:
+ "en" English
+ "en-us" English - USA
+ "en-gb" English - United Kingdom
+ "fr" French
+ "fr-ca" French - Canada
+ "de" German
+ "es" Spanish
+ -->
+ <dc:language>en-us</dc:language>
+
+ <!-- Cover [mandatory]. The cover image must be specified in <manifest> and referenced from
+ this <meta> element with a name="cover" attribute.
+ -->
+ <meta name="cover" content="My_Cover" />
+
+ <!-- The author of the book. For multiple authors, use multiple <dc:Creator> tags.
+ Additional contributors whose contributions are secondary to those listed in
+ creator elements should be named in contributor elements.
+ -->
+ <dc:creator>digitalmars.com</dc:creator>
+
+ <!-- Publisher: An entity responsible for making the resource available -->
+
+ <dc:publisher>digitalmars.com</dc:publisher>
+
+ <!-- Subject: A topic of the content of the resource. Typically, Subject will be
+ expressed as keywords, key phrases or classification codes that describe a topic
+ of the resource. The BASICCode attribute should contain the subject code
+ according to the BISG specification:
+ http://www.bisg.org/what-we-do-20-73-bisac-subject-headings-2008-edition.php
+ -->
+ <dc:subject>Reference</dc:subject>
+
+ <!-- Date: Date of publication in YYYY-MM-DD format. (Days and month can be omitted).
+ Standard to follow: http://www.w3.org/TR/NOTE-datetime
+ -->
+ <dc:date>2011-07-08</dc:date>
+
+ <!-- Description: A short description of the publication's content. -->
+ <dc:description>The specification of the D programming language.</dc:description>
+
+</metadata>
+
+<!--
+ Manifest:
+ The required manifest must provide a list of all the files that are part of the
+ publication (e.g. Content Documents, NCX table of contents, image files, CSS style sheets).
+ Kindlegen however does not require CSS and images to be specified in the manifest if they
+ are referenced from the content HTML.
+ The manifest element must contain one or more item elements with the following media-type attributes:
+
+ text/x-oeb1-document HTML content files
+ application/x-dtbncx+xml NCX table of contents
+ image/jpeg JPEG image
+ image/GIF GIF image
+
+ For detailed info visit: http://www.idpf.org/2007/opf/OPF_2.0_final_spec.html#Section2.3
+-->
+
+<manifest>
+ <!-- HTML content files [mandatory] -->
+ <item id="item3" media-type="application/xhtml+xml" href="dlangspec.html"></item>
+
+ <!-- table of contents [mandatory] -->
+<!--
+ <item id="My_Table_of_Contents" media-type="application/x-dtbncx+xml" href="KUG.ncx"/>
+-->
+ <!-- cover image [mandatory] -->
+ <item id="My_Cover" media-type="image/gif" href="dlangspec.png"/>
+</manifest>
+
+<!--
+ Spine:
+ Following manifest, there must be one and only one spine element, which contains one
+ or more itemref elements. Each itemref references an document designated
+ in the manifest. The order of the itemref elements organizes the associated content
+ files into the linear reading order of the publication.
+
+ The toc attribute refers to the id ref of the NCX file specified in the manifest.
+
+ For detailed info visit:
+ http://www.idpf.org/2007/opf/OPF_2.0_final_spec.html#Section2.4
+ http://www.niso.org/workrooms/daisy/Z39-86-2005.html#NCX
+-->
+
+<spine toc="My_Table_of_Contents">
+ <!-- the spine defines the linear reading order of the book -->
+ <itemref idref="item3"/>
+</spine>
+
+<!--
+ Guide:
+ Within the package there may be one guide element, containing one or more reference elements.
+ The guide element identifies fundamental structural components of the publication, to enable
+ Reading Systems to provide convenient access to them.
+
+ For detailed info visit: http://www.idpf.org/2007/opf/OPF_2.0_final_spec.html#Section2.6
+
+ The Kindle reading system support two special guide items which are both mandatory.
+ type="toc" [mandatory]: a link to the HTML table of contents
+ type="text" [mandatory]: a link to where the content of the book starts (typically after the front matter)
+
+ Kindle reading platforms need both thede guid items to provide a consistent user enxperience to the user.
+
+ It is good practice to include both a logical table of contents (NCX) and an HTML table of contents
+ (made of hyperlinks). The NCX enables various advanced navigation features but the HTML table of
+ contents can easily be discovered by the user by paging through the book. Both are useful.
+
+-->
+
+<guide>
+ <!-- <reference type="toc" title="Table of Contents" href="toc.html"></reference> -->
+ <reference type="text" title="Welcome" href="spec.html"></reference>
+</guide>
+
+</package>
View
339 dlangspec.png
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
View
22 win32.mak
@@ -299,19 +299,19 @@ windows.html : $(DDOC) windows.ddoc windows.dd
################ Ebook ########################
-specbook.d : $(SPECSRC) win32.mak
- catdoc -o=specbook.d $(SPECSRC)
+dlangspec.d : $(SPECSRC) win32.mak
+ catdoc -o=dlangspec.d $(SPECSRC)
-specbook.html : $(DDOC) ebook.ddoc specbook.d
- $(DMD) $(DDOC) ebook.ddoc specbook.d
+dlangspec.html : $(DDOC) ebook.ddoc dlangspec.d
+ $(DMD) $(DDOC) ebook.ddoc dlangspec.d
-specbook.zip : specbook.html ebook.css win32.mak
- del specbook.zip
- zip32 specbook specbook.html ebook.css
+dlangspec.zip : dlangspec.html ebook.css win32.mak
+ del dlangspec.zip
+ zip32 dlangspec dlangspec.html ebook.css
-specbook.mobi : specbook.html ebook.css win32.mak
- del specbook.mobi
- \kindlegen\kindlegen specbook.html
+dlangspec.mobi : dlangspec.opf dlangspec.html dlangspec.png ebook.css win32.mak
+ del dlangspec.mobi
+ \kindlegen\kindlegen dlangspec.opf
################# Pdf #########################
@@ -333,7 +333,7 @@ zip:
zip32 doc win32.mak $(DDOC) windows.ddoc linux.ddoc osx.ddoc freebsd.ddoc ebook.ddoc
zip32 doc $(SRC) $(PREMADE)
zip32 doc $(ASSETS)
- zip32 doc ebook.css
+ zip32 doc ebook.css dlangspec.opf dlangspec.png
clean:
del $(TARGETS)
Please sign in to comment.
Something went wrong with that request. Please try again.