Thematic-Making It Public/publication workshop

From XPUB & Lens-Based wiki
Revision as of 16:08, 10 February 2016 by Castrobot (talk | contribs)

Goal: hands-on work session to help develop the publication. We'll work towards getting everyone to integrate their contribution in the publication and see the result from his/her contribution right away.


State of matter

Where are we with the publication:

roles & tasks

    • Natalya: content transformations from videos onto still images ( pixel scan) + code snipets
    • Pleun: design
    • Colm: gathering and preface
    • Samira: write, editor
    • Nadine: coordinator
    • Max: translation onto code
    • Stone: content translation
    • Julia: reflective text (TBA)
    • Sara:

content

What content will make it to the book?


structure

What is the structure of the book? thinking through its organization


generative & interactivity

Will the book contain generative or interactivity elements? If so, which and why?


Resources

git repository

https://github.com/pietzwart/making-it-public 

.
├── book
│   ├── ashes.epub
│   ├── assets
│   │   ├── epubcover.jpg
│   │   ├── jquery-1.11.3.min.js
│   │   ├── jquery-1.7.0.min.js
│   │   ├── jquery-1.7.0.min.txt
│   │   ├── jquery.js
│   │   ├── script.js
│   │   └── script.txt
│   ├── chapter1.html
│   ├── epubcover.jpg
│   ├── generatebook.sh
│   ├── meta.xml
│   ├── mybook.epub
│   ├── _old
│   │   └── report.html
│   ├── report1.html
│   ├── report.html
│   ├── styles.css
│   └── title.html
├── Index_Sketch.ai
├── intro.md
├── Makingitpublic-report - Media Design- Networked & Lens-Based wiki.pdf
├── README.md
├── report.html
├── report.wiki
├── scans
│   ├── OCR
│   │   ├── archivingbooklet.jpg
│   │   ├── MER_3586.pdf
│   │   └── scanepud.rtf
│   └── wordexchange
│       ├── index.html
│       └── script.js
├── Screen Shot 2016-01-28 at 3.28.22 AM.png
└── test-mip
    ├── iTunesMetadata.plist
    ├── META-INF
    │   ├── com.apple.ibooks.display-options.xml
    │   └── container.xml
    ├── mimetype
    └── OEBPS
        ├── cover.xhtml
        ├── css
        │   └── style.css
        ├── images
        │   ├── book_cover.jpg
        │   ├── img_p01.jpg
        │   ├── img_p02.jpg
        │   ├── img_p03.jpg
        │   ├── img_p04.jpg
        │   └── img_p05.jpg
        ├── p01.html
        ├── p02.html
        ├── package.opf
        ├── report.html
        └── toc.xhtml
11 directories, 47 files
  • a very messy repository
    • unnecessary are tracked - not all files are needed. If one is doing experiments is better not to add or push those files to the repository; Instead a new local repository can be created (or a separate branch)
  • difficult to navigate and know what is important and what irrelevant
  • need more structure
  • need for a common format for text based content (Markdown files would be ideal)



Tools

Software overview

EPUB editor)

Chrome/Chromium browser that aims to be "a reference system for rendering EPUB 3 publications".

    • ibooks (if you have Mac)

from github, but right now the repository is there)

  • Markdown editor (Not essential. Most plain-text editors provide syntax highlighting for Markdown, yet you might want to use a WYSIWYG editor that renders that Markdown on-the-fly)


A markup language: Markdown

Suggestion: unify the all content for the book under 1 plain text markup format - Markdown.

  • Marking the text

"In electronic processing of texts, this hierarchical ordering of words into sentences, sentences into paragraphs and so on, as well as additional reading aids such bold or italic text, is made possible by using specific formatting codes. This process is called markup and the codes are called markup element"

  • WYSIWYG - visual markup

"'What You See Is What You Get' (WYSIWYG) markup languages used in word processors such as Microsoft Word, WordPerfect or OpenOffice, where text which is marked up in a certain way (such as italic or bold) is immediately displayed that way, so that there is no visible distinction between the conceptual structure and the visual representation."

Quotations from [http://www.publishinglab.nl/blog/publication/from-print-to-ebooks-a-hybrid-publishing-toolkit-for-the-arts/ From Print to Ebooks: a Hybrid Publishing Toolkit for the Arts]

  • Different Markup languages use different markup elements

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>

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

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


  • Why a Markup
    • text structure becomes explicitly
    • different markups and markup based formats (epub) are mostly equivalent easily translatable:
eg. markdown -> html -> latex(pdf)
  • Why Markdown ?
    • simple
    • compatible with HTML, but easier to read and write
    • allows the inclusion of HTML tags.
    • any plain text editor such as Sublime Text or Gedit can edit Markdown files.
    • there are WYSIWYG Markdown editors such as MacDown.

Always use plain-text editors or Markdown-dedicate-WSIWYG-editors to write in Markdown. Using a text-processor like MS Word,Libreoffice or Mac text editor will result on binary or rich text formats. We need to work with plain-text files

Pandoc

pandoc: software for converting between markups with

Pandoc diagram.jpg 


pandoc --from markdown --to html5 --standalone input.md -o output.html
  • --from / -f - option standing for “from”, is followed by the input format;
  • --to / -t - option standing for “to”, is followed by the output format;
  • --standalone / -s - option standing for “standalone”, produces output with an appropriate header and footer;
  • -o - option for file output

converting the Markdown to EPUB.

Simple: pandoc --from markdown --to epub3 --self-contained mymarkdownfile.md --output=mybook.epub

Advanced (indicating chapter level, stylesheet, cover image, metadata, TOC depth): pandoc --from markdown --to epub3 --self-contained --epub-chapter-level=1 --epub-stylesheet=styles.epub.css --epub-cover-image=cover.jpg --epub-metadata=metadata.xml --toc-depth=1 --output=mybook.epub mymarkdownfile.md

  • --epub-chapter-level - at what heading level will the chapter brakes occur
  • --toc-depth - what heading level will be present in the Table of Contents


Hybrid Publishing Resources - streamlining production

Hybrid Publishing Resources

This previous approach of converting between markups using Pandoc can be automated.

Since computers are good at doing repetitive and boring tasks, we can take advantage from it.

We can store commands in script files and have them perform the same task on multiple source files, producing multiple outputs (E.G. EPUB, ICML, HTML).


Overview

  • From several markdown source files will create one single EPUB
  • Any changes to the source files are easily incorporated in the EPUB
  • keeping a connection between the source and its outcomes.

Steps

This hybrid publishing recipe will involve the following steps:

  1. .docx - manuscript - editing the manuscript using word styles
  2. Markdown - source - editing the manuscripts(source files) in Markdown (.md) files.
  3. EPUB - output -converting the Markdown files onto an EPUB

Note: The section "6.3. Do-it-yourself EPUB using Pandoc" form From Print to Ebooks is an important complement to this tutorial and set of tools

Hybrid-workflow.png

Makefile

My proposal involves using a Makefile to automate the conversions between markups.

  • Makefiles are often used within the free-software community to compile source code into binary programs ready to run
  • Makefiles can also be seen as notebooks of commands to process stuff and generate other stuff from it.
  • There is nothing stopping us from using makefiles to automate conversions between markup-languages.
More on about Makefiles in the context of hybrid publishing:

Recipe Preparation

clone Hybrid Publishing Resources

  • Download the Hybrid Publishing Resources code repository into your computer as .zip file or using ssh
    • as zip: Move the downloaded .zip into a dedicated folder; Unzip
    • with ssh: git clone --depth 1 --branch wdka git@gitlab.com:DigitalPublishingToolkit/Hybrid-Publishing-Resources.git
  • In terminal
    • change directory cd to the unzip folder
    • remove .git folder, so this can become a new repository, dedicate to your publication rm -r .git

Folder structure

To create folder structure, which will be understood by the scripts from this repository, you need to run:

make folders

This script will generate the following folder structure, which you'll use to store the files essentially for the creation of the EPUB. 

├── docx/
├── epub/
│   ├── cover.jpg
│   ├── metadata.xml
│   └── styles.epub.css
├── icml/
├── lib/
├── makefile
├── md/
│   └── imgs/
├── README.md
└── scripts/
    ├── md_stripmetada.py
    └── md_unique_footnotes.py
  • docx/ - (not applicable) folder used to store .docx files that are converted onto markdown files
  • epub/ - folder used to store resource files for epub
  • docx/ - (not applicable) folder used to store .icml files to be imported onto inDesign
  • lib/ - folder used to store custom font files for the epub
  • makefile - the recipe-book file - can be edited and changed to fit the publication needs
  • md/ - folder used to store the source markdown files
  • md/imgs/ - folder used to store the images files
  • scripts/ - folder used to store scripts necessary for the production of the epub


Images in Markdown

Images for the publication need to be:

  • saved in the folder md/imgs/
  • placed in the markdown document: ![My image caption](imgs/myImage.jpg)
  • Note: Don't forget to include captions, if the image has them. Markdown captions will become visible, and associated to the image in the EPUB output.


make book.epub

  • make book.epub creates the epub from the markdown files, images, and epub resources
  • to create the epub a single Markdown file book.md will be created and save inside the md/ folder. You don't have to perform this step, as the makefile does it for you.
  • book.md consists of the content from all the individual Markdow files inside the md/ folder, in alphabetical order (00 to ZZ). If you want to change the order the publication, you can change the filenames in order to do so.
  • Note: the Markdown filenames should NOT contain spaces or dots, except for the extension .md

To generate this single book.md, run: make book.md .

Essential files for EPUB

cover image, metadata, stylesheet, and fonts strongly influence the EPUB's outcome, and consequently should be edited for each publication or series of publication.

  • epub/metadata.xml - EPUB metadata
  • epub/styles.epub.css - EPUB css style-sheet '
  • epub/cover.jpg - EPUB cover
  • lib/ is folder for storing custom fonts, that will be used in the EPUB

Note on the use of custom fonts: If you choose to use fonts, make sure to change the makefile to include the use of fonts in the makefile epub rule, such as in the rule bellow, where --epub-embed-font=lib/UbuntuMono-B.ttf \ was added to allow for the use of the Ubuntu Mono font. Also include the font on th EPUB style-sheet with @font-face rule


An iterative process

make book.epub works as an cyclical process, that starts with changing the source files (markdown files, the EPUB's stylesheet, the EPUB's metadata) and seeing the results of those changes in Calibre (or other ebook-viwerer), several times until achieving the desired result.

EPUB check

The health of the created EPUB can be checked with http://validator.idpf.org/


Git

If there is one distributed Git repository, containing the HPR as well as the content,

  • anyone who is part of the repository can edit content, resources, or scripts;
  • make the epub, to see the result of her changes and see the result
  • if satisfied she can add the change files, commit the changes and push to the remote repository.
  • other collaborators can receive her changes by pulling the changes from the remote repository

Integrate it

  • a new repository, based on Hybrid Publishing Resources structure
  • 1 pushes initial repository
  • others clone, start working on their bits change, adding, commiting, pushing.

Future dev

  • what will be done by Open day?
  • wish-list
  • plan
Retrieved from "https://pzwiki.wdka.nl/mw-mediadesign/index.php?title=Thematic-Making_It_Public/publication_workshop&oldid=91790"