|
|
<!DOCTYPE html>
|
|
|
<html xmlns="http://www.w3.org/1999/xhtml" lang="" xml:lang="">
|
|
|
<head>
|
|
|
<meta charset="utf-8" />
|
|
|
<meta name="generator" content="pandoc" />
|
|
|
<meta name="viewport" content="width=device-width, initial-scale=1.0, user-scalable=yes" />
|
|
|
<title>glossary</title>
|
|
|
<style type="text/css">
|
|
|
code{white-space: pre-wrap;}
|
|
|
span.smallcaps{font-variant: small-caps;}
|
|
|
span.underline{text-decoration: underline;}
|
|
|
div.column{display: inline-block; vertical-align: top; width: 50%;}
|
|
|
</style>
|
|
|
<link rel="stylesheet" href="style.css" />
|
|
|
</head>
|
|
|
<body>
|
|
|
<h1>EPUB</h1>
|
|
|
<p>⤷ Acronym for Electronic Publication. An ebook format developed by the international Digital Publishing Forum (IDPF). EPUB is an open standard and the most commonly used and supported file format for electronic books. EPUB was designed to accommodate reflow-able content. (by a tool kit for hybrid publishing)</p>
|
|
|
<h1>electronic publication</h1>
|
|
|
<p>⤷ Beyond EPUB, A Electronic Publication is a publication generated, created and shown by an electronic device.</p>
|
|
|
<h1>book</h1>
|
|
|
<p>⤷ The codex. By folded Paper. Unfolded stapled paper. Drawn space. Wrapped by glue, staples, threads. Telling drawings, letters, words, images. contains containers such as prologues, colophon. An interface. Index. Simple. Whole. a format.</p>
|
|
|
<h1>art-oriented publisher</h1>
|
|
|
<p>⤷ Commonly those who relate their publishing practice to the arts. As a practice, it may refers to the act of publish art related content such as an art catalogue, art history book, art picture book, etc. Furthermore: to publish an art piece itself.</p>
|
|
|
<h1>autonomous practice</h1>
|
|
|
<p>⤷ On publishing, to be able and have the energy to create, make, produce and share with self autonomy. Etymologicaly, autonomous comes from auto- (“self”) and -nomy (“a system of rules or laws about a particular field”). Autonomous practice suggests drawing your own rules and own systems of creating, making, producing and distributing in order to make something public.</p>
|
|
|
<h1>design-oriented publisher</h1>
|
|
|
<p>⤷</p>
|
|
|
<h1>publishing</h1>
|
|
|
<p>⤷ to make something public. to circulate. to filter and amplify.</p>
|
|
|
<h1>hybrid publishing</h1>
|
|
|
<p>⤷ the act of publishing through differents mediums and techniches in order to adapt and contextualize to a specific project or part of it. A hybrid publication can offer a varied spectrum of objects and processes that together construct the body of it.</p>
|
|
|
<h1>printed publishing</h1>
|
|
|
<p>⤷ A type of publication that uses a printing techniche such as offset, inkyet, risoprint as its physicall</p>
|
|
|
<h1>RISO printing</h1>
|
|
|
<p>⤷</p>
|
|
|
<h1>agency</h1>
|
|
|
<p>⤷</p>
|
|
|
<h1>word processors</h1>
|
|
|
<p>⤷ Like Microsoft word. There is plenty open-source ones.</p>
|
|
|
<h1>desktop publishing suites (DTP)</h1>
|
|
|
<p>⤷ The design of printed matter on a personal computer using graphical What-You-See-Is-What-You-Get (WYSIWYG) software such as Adobe InDesign or QuarkXpress. DTP software uses a graphical user interface to visually simulate the analog desks used in pre-digital times by graphic and editorial designers.</p>
|
|
|
<h1>future-trash</h1>
|
|
|
<p>⤷ Resisting burnout and future trash puts artist and their work in a good position to solve problems. By sustaining a publishing practice over time and creating objects that persist with meaning as their inherent value, artist publishers can continue to create, contribute to, and maintain the radically open, imaginative, accessible and inclusive community that makes up artist publishing. (Alex Arzt, pag 20, What Problems Can Artist Publishers Solve?)</p>
|
|
|
<h1>do-it-yourself (DIY)</h1>
|
|
|
<p>⤷</p>
|
|
|
<h1>fanzine</h1>
|
|
|
<p>⤷</p>
|
|
|
<h1>festival</h1>
|
|
|
<p>⤷</p>
|
|
|
<h1>markdown: word processing format</h1>
|
|
|
<p>⤷</p>
|
|
|
<h1>small-edition</h1>
|
|
|
<p>⤷</p>
|
|
|
<h1>low cost</h1>
|
|
|
<p>⤷</p>
|
|
|
<h1>easy to use</h1>
|
|
|
<p>⤷</p>
|
|
|
<h1>sustainability</h1>
|
|
|
<p>⤷</p>
|
|
|
<h1>platform independence</h1>
|
|
|
<p>⤷</p>
|
|
|
<h1>open source</h1>
|
|
|
<p>⤷</p>
|
|
|
<h1>layout</h1>
|
|
|
<p>⤷</p>
|
|
|
<h1>e-reader hardware</h1>
|
|
|
<p>⤷</p>
|
|
|
<h1>e-reader software</h1>
|
|
|
<p>⤷</p>
|
|
|
<h1>book-binding</h1>
|
|
|
<p>⤷</p>
|
|
|
<h1>plain text</h1>
|
|
|
<p>⤷ Text without any visual formatting (such as bold, italic, font types and sizes, clickable hyperlinks, etc.) ASCII is the oldest and still most common plain-text format</p>
|
|
|
<h1>grain direction</h1>
|
|
|
<p>⤷</p>
|
|
|
<h1>WYSIWYG (what you see is what you get)</h1>
|
|
|
<p>⤷</p>
|
|
|
<h1>logical-semantic markup</h1>
|
|
|
<p>⤷</p>
|
|
|
<h1>HTML (hyper text Markup Language)</h1>
|
|
|
<p>⤷</p>
|
|
|
<h1>electronic text</h1>
|
|
|
<p>⤷</p>
|
|
|
<h1>paged-centred</h1>
|
|
|
<p>⤷</p>
|
|
|
<h1>reflow-able layout</h1>
|
|
|
<p>⤷</p>
|
|
|
<h1>optical character recognition (OCR)</h1>
|
|
|
<p>⤷</p>
|
|
|
<h1>hyperlinks</h1>
|
|
|
<p>⤷</p>
|
|
|
<h1>bitstreams</h1>
|
|
|
<p>⤷</p>
|
|
|
<h1>one-to-one:</h1>
|
|
|
<p>⤷ single book published in different media</p>
|
|
|
<h1>one-to-many:</h1>
|
|
|
<p>⤷ single book that has different appearances in different media</p>
|
|
|
<h1>one-to-database:</h1>
|
|
|
<p>⤷ book based on the content of the data base which can be used in a number of ways</p>
|
|
|
<h1>discourse</h1>
|
|
|
<h1>timeframe</h1>
|
|
|
<h1>speed</h1>
|
|
|
<h1>quality</h1>
|
|
|
<h1>afterlife</h1>
|
|
|
<p>⤷ how to make the content relevant again? Re-using it for different contexts.</p>
|
|
|
<h1>non-hasty</h1>
|
|
|
<p>⤷</p>
|
|
|
<h1>reader</h1>
|
|
|
<p>⤷</p>
|
|
|
<h1>post-digital</h1>
|
|
|
<p>⤷</p>
|
|
|
<h1>anaphora</h1>
|
|
|
<p>⤷</p>
|
|
|
<h1>manifesto</h1>
|
|
|
<p>⤷</p>
|
|
|
<h1>post-colonial</h1>
|
|
|
<p>⤷</p>
|
|
|
<h1>fragmented</h1>
|
|
|
<p>⤷</p>
|
|
|
<h1>small press</h1>
|
|
|
<p>⤷</p>
|
|
|
<h1>private press</h1>
|
|
|
<p>⤷</p>
|
|
|
<h1>habit</h1>
|
|
|
<p>⤷</p>
|
|
|
<h1>frustration</h1>
|
|
|
<p>⤷</p>
|
|
|
<h1>urgency</h1>
|
|
|
<p>⤷</p>
|
|
|
<h1>open access</h1>
|
|
|
<p>⤷</p>
|
|
|
<h1>newsletter</h1>
|
|
|
<p>⤷</p>
|
|
|
<h1>audience</h1>
|
|
|
<p>⤷</p>
|
|
|
<h1>to reach</h1>
|
|
|
<p>⤷</p>
|
|
|
<h1>meme-ability</h1>
|
|
|
<p>⤷</p>
|
|
|
<h1>communal</h1>
|
|
|
<p>⤷</p>
|
|
|
<h1>community-building</h1>
|
|
|
<p>⤷</p>
|
|
|
<h1>political act</h1>
|
|
|
<p>⤷</p>
|
|
|
<h1>editor</h1>
|
|
|
<p>⤷</p>
|
|
|
<h1>filtering</h1>
|
|
|
<p>⤷</p>
|
|
|
<h1>amplification</h1>
|
|
|
<p>⤷</p>
|
|
|
<h1>caring</h1>
|
|
|
<p>⤷</p>
|
|
|
<h1>ambiguity</h1>
|
|
|
<p>⤷</p>
|
|
|
<h1>continuity</h1>
|
|
|
<p>⤷</p>
|
|
|
<h1>dialogue</h1>
|
|
|
<p>⤷</p>
|
|
|
<h1>determination</h1>
|
|
|
<p>⤷</p>
|
|
|
<h1>dissonance</h1>
|
|
|
<p>⤷</p>
|
|
|
<h1>gathering</h1>
|
|
|
<p>⤷</p>
|
|
|
<h1>groundly</h1>
|
|
|
<p>⤷</p>
|
|
|
<h1>mutation</h1>
|
|
|
<p>⤷</p>
|
|
|
<h1>reciprocity</h1>
|
|
|
<p>⤷</p>
|
|
|
<h1>autopoiesis</h1>
|
|
|
<p>⤷ The term autopoiesis (from Greek αὐτo- (auto-) 'self', and ποίησις (poiesis) 'creation, production') refers to a system capable of reproducing and maintaining itself by creating its own parts and eventually further components.</p>
|
|
|
<h1>sym-poiesis</h1>
|
|
|
<h1>transformation</h1>
|
|
|
<h1>amplification</h1>
|
|
|
<h1>drawing</h1>
|
|
|
<h1>knoting</h1>
|
|
|
<h1>Table contents</h1>
|
|
|
<h1>Footnotes</h1>
|
|
|
<h1>Endnotes</h1>
|
|
|
<h1>Cross.references</h1>
|
|
|
<h1>Citations</h1>
|
|
|
<h1>Bibliography</h1>
|
|
|
<h1>Real-time data</h1>
|
|
|
<h1>RSS: Really Simple Syndication</h1>
|
|
|
<h1>screen</h1>
|
|
|
<p>⤷ “screen based publishing is intimate in my opinion, as it reaches the space of personal screens often in intimate spaces, but it establishes a remote intimacy, as the publisher is not necessarily meant to be present on the other side and his or her body is certainly distant and invisible” (alessandro Ludovico)</p>
|
|
|
</body>
|
|
|
</html>
|