Courses/Hybrid publishing/Q8

<slidy theme="a" />

Professional development workshop on Hybrid Publishing

practicals

• software used (download to your computer):
  • Calibre,
  • Pandoc,
  • plain-text editors ( Sublime Text, Gedit )
  • Xcode (mac)

Plan

• Full concentration
• Hybrid publishing
• concepts,
• examples
• formats (markups)
• tools and strategies

publishing?

• hybrid publishing as an extension of efforts from Publication station - establishing dialog between analog & digital
• continuation of Alessandro Ludovico's research on Post-Digital Print at WdKA
• continuation of Digital Publishing Toolkit project & From Print to Ebooks – a Hybrid Publishing Toolkit for the Arts
• publishing as a way to expose the research undertaken within WdKA
• publishing as a learning tool

hybrid publication?

A publication that inhabits both analog and digital worlds.

hybrid publishing works

Traumawien [1] [2] http://rlv.zcache.com/traumawien_button-rb0a7981400224870838ec6aaa582161c_x7j3i_8byvr_512.jpg

Badlands Unlimited http://badlandsunlimited.com/wp-content/uploads/2013/06/book_small.gif http://badlandsunlimited.com/books/phaedrus-pron/

Books Scapes, Julien Levesque, 2012

http://p-dpa.net/wp-content/uploads/2015/03/Screen-Shot-2014-02-15-at-17.17.18-600x150.png

E-Book Backup, Jesse England, 2012

http://p-dpa.net/wp-content/uploads/2015/03/9_ebookbackup4-300x225.jpg

More hybrid publishing works in Post-Digital Publishing Archive

Multichannel publishing workflows

• ePub
• PDF (print book)
• website
• ebook trailer

Ebook trailer of From Print to Ebooks

Tools for hybrid publishing

open source, simple tools that work in combination, forming publishing pipelines

• Calibre
• Pandoc
• [3]

plain text files

Are only constituted by text. No images, no visual markings.

Are edited using plain text editors and NOT word processors.

Can be displayed using the terminal cat myfile.txt will print the content of myfile.txt

Markings are done using special (meta)characters

Historical examples of plain text file undeground publishing

Markups languages

Markups languages are ways of marking text, giving with words specific hierarchical and visual rendering.

By marking the text according to markup languages it is possible to:

• add reading aids, such bold, italic, blockquotes
• add a clear text hierarchy: section titles, sub-section titles, sub-sub-sub section titles
• convert between different markup languages - as they mostly compatible

Markup languages examples

Each markup uses a different markings

HTML:

<h1>Revenge of the Text</h1>
 <p>There is a room in the <strong>Musée d’Orsay</strong> that I call the <em>room of possibilities</em>.</p>
 <p>That room contains:</p>
 <ul>
  <li>a snow flake</li>
  <li>the end of a cloud</li>
  <li>a bit of nothing</li>
 </ul>

Markdown:

# Revenge of the Text
There is a room in the **Musée d’Orsay** that I call the *room of possibilities*.

That room contains:
* a snow flake
* the end of a cloud
* a bit of nothing

Wiki markup:

= Revenge of the Text =
There is a room in the '''Musée d’Orsay''' that I call the ''room of possibilities''.

That room contains:
* a snow flake
* the end of a cloud
* a bit of nothing

Hands on

• download the repository of texts for this project: https://github.com/wdka-publicationSt/editorial_design/archive/master.zip
• unzip
• from all its files there choose 1 file, you'll be working on, for today
• copy it to a folder dedicated to today's class
• open in a text editor: sublime, gedit,etc
• Look at the markdown syntax

More on Markdown syntax in http://daringfireball.net/projects/markdown/syntax

convert this file into other formats

Using Pandoc:

• html
• docx
• mediawiki

Pandoc - a markup converter

If you need to convert files from one markup format into another, pandoc is your swiss-army knife

But it runs on the command line.

Command Line or Shell

• a text-based interface to your computer's file system
• popularized before the period of personal computers,
  • when computers where shared (time-sharing) by many users
  • accessed by a dumb terminal (screen and keyboard interface to the main computer) File:Dumbterminal.jpg
• centeral to UNIX and descendant operating systems: Linux, Mac
• constituted by small programs that do one thing only and well

Command line cheat-sheet

Template:Terminal cheat sheet from Terminal_cheat_sheet

Command line exercise

TO DO

http://flossmanuals.net/command-line/

Pandoc - Convert from Markdown to HTML

pandoc --from markdown --to html5 --standalone input.mw -o output.html

• --from - option standing for “from”, is followed by the input format;
• --to - option standing for “to”, is followed by the output format;
• --standalone - option standing for “standalone”, produces output with an appropriate header and footer;
• -o - option for file output

editing the HTML file

Add CSS files

<!DOCTYPE html>
<html>

<head>
  <link rel="stylesheet" type="text/css" href="style.css" />
</head>

<body>
  <h1>my html file</h1>
</body>
</html>

Pandoc - converting to ICML

TO DO

pandoc --from markdown --to icml input.html --output=ouput.icml

Pandoc - converting to ePub

Simple:

pandoc --from html --to epub3 input.html --output=mybook.epub

Advanced (including stylesheet, cover image, chapter level ):

pandoc --from html --to epub3 input.html --output=mybook.epub --epub-stylesheet=styles.css --epub-cover-image=cover.jpg --epub-chapter-level=1

• --epub-stylesheet - CSS file that will style the Epub
• --epub-cover-image - cover file - can either be .jpg or .png
• --epub-chapter-level - at what heading level will the chapter brakes occur

ASSIGNMENT

For May 27: Choose 1 publication you want to work in. From the 3 possible publications (https://github.com/wdka-publicationSt/editorial_design/archive/master.zip)

Using at least 1 file from the chosen one

• convert it to: an HTML file & an ICML file

• use CSS to make different sketches for the digital (html) identity of this book
• use inDesign style to create different sketches of the paper identity of this book

This will be the starting points for the publication you will do in quarter 8.

Bring these sketches to next class, on May 27;

</references>