Courses/EPUB - Revision history

Andre at 19:44, 5 March 2015

2015-03-05T19:44:54Z

← Older revision		Revision as of 19:44, 5 March 2015
Line 20:		Line 20:
	** '''Gedit https://wiki.gnome.org/Apps/Gedit'''		** '''Gedit https://wiki.gnome.org/Apps/Gedit'''
	** '''Sublime Text http://www.sublimetext.com/'''		** '''Sublime Text http://www.sublimetext.com/'''


			[[Category:teaching]]

Andre at 15:42, 4 February 2015

2015-02-04T15:42:35Z

← Older revision		Revision as of 15:42, 4 February 2015
Line 2:		Line 2:
	* [[Courses/EPUB/day1]]		* [[Courses/EPUB/day1]]
	* [[Courses/EPUB/day2]]		* [[Courses/EPUB/day2]]
			* [[Courses/EPUB/day3]]



	==<span style="background:#CCFF66;">What is ePub?</span>==		==<span style="background:#CCFF66;">What is ePub?</span>==

Andre at 14:16, 21 January 2015

2015-01-21T14:16:11Z

← Older revision		Revision as of 14:16, 21 January 2015
Line 1:		Line 1:


	* [[Courses/EPUB/day1]]		* [[Courses/EPUB/day1]]
	* [[Courses/EPUB/day2]]		* [[Courses/EPUB/day2]]

	~~<span style="font-size:20px">http://publicationstation.wdka.hro.nl/wiki</span>~~


	==<span style="background:#CCFF66;">What is ePub?</span>==		==<span style="background:#CCFF66;">What is ePub?</span>==

Andre at 14:15, 21 January 2015

2015-01-21T14:15:48Z

← Older revision		Revision as of 14:15, 21 January 2015
Line 4:		Line 4:
	* [[Courses/EPUB/day2]]		* [[Courses/EPUB/day2]]

	<span style="font-size:20px">~~wiki~~ http://publicationstation.wdka.hro.nl/wiki</span>		<span style="font-size:20px">http://publicationstation.wdka.hro.nl/wiki</span>

Andre at 14:15, 21 January 2015

2015-01-21T14:15:34Z

@@ Line 4: / Line 4: @@
 * [[Courses/EPUB/day2]]
 <span style="font-size:20px">wiki http://publicationstation.wdka.hro.nl/wiki</span>
@@ Line 25: / Line 14: @@
 ''As the cherry on top of the cake you will experiments with small programs to turn the ePubs into gif animations, word maps, or remixed versions of themselves.''

Andre at 14:14, 21 January 2015

2015-01-21T14:14:49Z

Show changes

Andre: /* Change and zip the EPUB archive */

2015-01-14T19:17:25Z

Change and zip the EPUB archive

@@ Line 458: / Line 458: @@
 </source>
-==Change and zip the EPUB archive==
+==zip all the files into to an EPUB==
 ==experiment==

Andre: /* content.opf */

2015-01-14T17:18:00Z

content.opf

← Older revision		Revision as of 17:18, 14 January 2015
Line 163:		Line 163:
	<package xmlns="http://www.idpf.org/2007/opf" xmlns:dc="http://purl.org/dc/elements/1.1/" unique-identifier="epub-id-1" version="3.0">		<package xmlns="http://www.idpf.org/2007/opf" xmlns:dc="http://purl.org/dc/elements/1.1/" unique-identifier="epub-id-1" version="3.0">
	<metadata>		<metadata>
	~~<metadata>~~
	...		...
	</metadata>		</metadata>
Line 287:		Line 287:

	It often points to [[#TOC\|nav]] file.		It often points to [[#TOC\|nav]] file.



	== Navigation - table of contents ==		== Navigation - table of contents ==

Andre: /* fonts */

2015-01-14T15:51:43Z

fonts

← Older revision		Revision as of 15:51, 14 January 2015
Line 460:		Line 460:
	</source>		</source>

			==Change and zip the EPUB archive==



	==experiment==		==experiment==

Andre at 15:50, 14 January 2015

2015-01-14T15:50:17Z

← Older revision		Revision as of 15:50, 14 January 2015
Line 366:		Line 366:
	* Ampersands (&) must be escaped as &.		* Ampersands (&) must be escaped as &.

	Example content document:		Example of a content document:

	<source lang="xml">		<source lang="xml">
	<?xml version="1.0" encoding="UTF-8"?>		<?xml version="1.0" encoding="UTF-8"?>
Line 390:		Line 389:

	=== semantic inflection ===		=== semantic inflection ===
	~~These additions make~~ possible the ~~inclusion of~~ [http://www.idpf.org/epub/30/spec/epub30-contentdocs.html#sec-xhtml-semantic-inflection '''semantic inflection''']~~, or in~~ other words, to attach meaning about the purpose or nature an element to itself. Semantic inflections use the epub:type attribute to describe the content contained within that element. The terms that can be used in these inflections can be found at http://www.idpf.org/epub/vocab/structure/		It is possible to enrich the content documents with [http://www.idpf.org/epub/30/spec/epub30-contentdocs.html#sec-xhtml-semantic-inflection '''semantic inflection''']. In other words, to attach meaning about the purpose or nature an element to itself.

			Semantic inflections use the <code>epub:type</code> attribute to describe the content contained within that element. The terms that can be used in these inflections can be found at http://www.idpf.org/epub/vocab/structure/

	In the previous example epub:type appears in <code><section class="level1" epub:type="acknowledgments frontmatter" id="acknowledgments"></code>. It informs us, and the reading system that the current section belongs to the book's frontmatter and constitutes the acknowledgments.		In the previous example epub:type appears in <code><section class="level1" epub:type="acknowledgments frontmatter" id="acknowledgments"></code>. It informs us, and the reading system that the current section belongs to the book's frontmatter and constitutes the acknowledgments.
Line 396:		Line 397:

	== images ==		== images ==
	Images can either be a raster (jpg or png) or an SVG, however it is safer to opt for a raster.		Images can either be a raster (jpg or png) or an SVG, however it is safer to opt for a raster as it is more likely that all eredears will render it.

	They need to be included in ''package document''(.opf)'s manifest:		They need to be included in ''package document''(.opf)'s manifest:
Line 412:		Line 413:
	A cover is essentially an image, either a raster image (jpg or png) or an SVG, however it is safer to opt for a raster.		A cover is essentially an image, either a raster image (jpg or png) or an SVG, however it is safer to opt for a raster.

	Within the ''package document''(.opf), the cover is declared both within the manifest, as item with properties="cover-image", so that the reading systems identify the image in question as the cover of the ePub ~~in question~~.		Within the ''package document''(.opf), the cover is declared both within the manifest, as item with '''properties="cover-image"''', so that the reading systems identify the image in question as the cover of the ePub.
	<item id="cover-img" href="cover.jpg" media-type="image/jpeg" properties="cover-image"/>		<item id="cover-img" href="cover.jpg" media-type="image/jpeg" properties="cover-image"/>

	If you want the cover to also appear ~~inline,~~ when ~~you~~ start the book, make sure to include a ''content document''~~, just with~~ the image:		If you want the cover to also appear as the first content the reader sees when she start the book, make sure to include a ''content document'' that includes the image:

	<source lang="xml">		<source lang="xml">
Line 438:		Line 439:

	== style ==		== style ==
	~~If you want to use~~ CSS style-~~sheet, sure each~~ ''~~content~~ document'' ~~links~~ to ~~the sheet.~~		CSS style-sheets need to be declared in the ''package document''(.opf)'s manifest.

			And

			Linked to in every content document's <code><head></code>
	<link rel="stylesheet" type="text/css" href="stylesheet.css" />		<link rel="stylesheet" type="text/css" href="stylesheet.css" />