Draft for an "Online Publishing House":
Based on "oph-usage-paper_0.5.odt"
This Application will show of the full power of collaborative content creation and the strength of Tiki in this collaborative Authoring environment.
Tiki for Online Publishers
The goal is to be able to present the complete supply chain of an "Online Publishing House" including collaborative Authoring, Quality Assurance, Project Management, Team Building, CRM, Selling and Invoicing, Representation of the Business Logic and Printing to a Paperbook or publish online.
The Business Plans project will be the first step.
Online Publishing House
Some Ideas from Rick
- Support for multiple (custom) XML schema: DITA, Docbook, custom DTD, etc.
- Ability to create an Index in the paper book, based on:
- use of Tiki Freetags
- unique plugin/identifier
- Automatic conversion of internal links to (on page XX) cross-references
- Automatic conversion of external links to URLs:
- with a text-title
- with a QR code
- Ability to create a Glossary in the paper book that:
- will include pop-up/mouseover definitions (and unique styling) for E-book versions
- Ability to "embed" non-printing resources (such as Flash movies) in the wiki, that will be included in E-book version
- Versioning/history of printed/delivered output
- Export Tiki comments as "notes" in the E-book version or PDF
- DRM support (if available in the selected output format)
- Determination of left/right pagination, section tabs, numbering, etc.
- Decide Wikipublisher vs Booki/Objavi vs other -> Online Publishing House - Output formats
- MultiTiki vs Namespaces and Online Publishing House - Workspaces
- Community of developers & users
- Revamp Structures
- To make it easy for Online Publishing House - Chapters, Structure and Table of Content
- File Gallery -> Make it possible to keep original high-resolution images, while having a modified version for print or web (resize, crop, change colors, etc.)
- Revamp Structures
- Online Publishing House - Commerce
- Look into Offline with HTML5 -> Offline
- Online Publishing House - WYSIWYG editing
We should not call it book as the functionality covers more than this (eg. Letters, Business Reports, Websites, Slide Shows)
Options so far:
- (on demand) publication
- any idea?
Some wisdom from Adam Hyde
Questions for Adam Hyde
- Wiki syntax vs HTML WYSIWYG (Why Xinha)?
- Book vs chapter vs index
- CSS Book Design vs LaTeX or XeTeX
- Why the Webkit PDF rendering engine?
- Has the need for "reverse binding for printing right-to-left texts on a left-to-right press and vice versa" ever actually popped up, or is it mentioned because the webit PDF rendering engine does it
- Export formats
- static HTML for linking from a website, to .odt (OpenOffice rich text format), standalone HTML, epub, and screen readable PDF. Other XML, and 'e-book' output options can be developed as Extensions.
- Own project vs add-on of existing project
- Collaboration with other projects & code re-used
- Why Python?
- SVG edit
- Image raw, srgb & colormanagement
- Books with alternate endings
- IRC gateway, system level notifications, and chapter status markers, book progress indicators, work flow tools, messaging, and live user status listings.
- Localisation: Pootle
- Translation: We are considering a World Wide Lexicon Extension to add machine translation to the work flow
- importing of Archive.org epubs
- Embed API
- Interactive media
- http://razorjack.net/quicksand/ UI for genres
- http://helios.de/ and http://webshare.helios.de
- Links related to Print on Demand: XML->TEX, See www.tug.org/TUGboat/Articles/tb21-3/tb68carl.pdf
- http://www.booki.cc/ used for http://flossmanuals.net/ at http://booki-dev.flossmanuals.net/
- Onix standards
- training in Tunis about Open Source for editing books, for African publishing houses in the education sector
Links realted to the XeTeX typesetting system
- O'Reilly Webcast: Designing And Creating A Social Book App(YouTube)