Publishing Futures A perfect world Lorna Priest SIL

Encoding • ANSI will be gone • Unicode – UTF-8 – UTF-16 – UTF-32

Data Structure • SFM gone! • XML, XSL and XSLT – XML is a standard for marking up data • clearly indicates structure of the data, generally in a way that indicates the meaning of different parts of it rather than how they will be displayed • has beginning and ending tags – XSL is a language for expressing stylesheets: • a language for transforming XML documents, and • an XML vocabulary for specifying formatting semantics – XSLT is a language for transforming XML documents into other documents (XML, HTML, etc)

General publishing overview Types of documents: 1. Scripture 2. Academic dictionaries complex charts tables TOC Index 3. Literacy Analysis Tool Output Process (Paratext / Field. Works) (Publishing Tool) Source document Editing (including Keyman, etc)

Input overview (future) Preprocessing/ Checking/ analysis Source Document: XML/Unicode XML editor DTD/Schema: XSEM, OSIS Doc. Book Output Process (Publishing Tool) Font: Open. Type, AAT, Graphite, Te. X keyman Typecaster Welder(? ) VOLT

Publishing overview (future) Style Sheet: XSL CSS Preprocessing/ Checking/ analysis Transformation Process: XSLT (xt, sax, msxml 3) Source Document: XML/Unicode Output Process: : MSPublisher Result Document: XML text Result Document: HTML Frame. Maker PERL XSL-FO Input: Keyman XML editor Te. X: mu. Te. X, Omega, etc. XSL-Formatter / Ultra. XML / Render. X Fonts graphics CSS RTF PDF SQL CD: TW / FW Web/Commerce Video/music Etc, etc.

Publishing Overview (past/present) Preprocessing/ checking/analysis: (ccount, diafind, cvchek, wdl, hyphenation, quotes uc/lc, etc. ) Source Document: sfm Output Process: Print/pdf Result Document: Text/Ventura tagged CC Ventura Publisher Style Sheet: template SFC Input Method: Keyman Win. Word film Transformation Process: Typecaster Welder Font Style Sheet: Scripture macros graphic Te. X (Te. Xg. X, Omega, etc. )

Conversion (perfect world) Preprocessing/ analysis: ? ? ? 8 -bit Unicode Mapping Repository Source Document: XML/Unicode sfm XML Input Method: Keyman XML editor Win. Word yles XSL/CSS nt it fo 8 -b K ey m an 3. sm art 2 fon K ey ts m an 5 DTD/Schema: XSEM TEI lite? Word/Ventura st Legacy Document: LL, Shoebox, sfm Output Process (Publishing Tool)

Conversion Overview (imperfect world) XML & Unicode Document SFM & Unicode Document Mapping Repository XML > sfm > XML 8 -bit > Unicode > 8 -bit Legacy Document: LL, Shoebox, sfm

Conversion Overview (imperfect world) XML & Unicode Document SFM & Unicode Document XML > sfm > XML 8 -bit > Unicode > 8 -bit Legacy Document: LL, Shoebox, sfm

Transition period scenarios… • How will this affect us? • Practical issues we will face – IPub will begin receiving • Unicode text – Will you convert it back to 8 -bit for publishing in Ventura? • 8 -bit text – Leave it for now until we switch publishing applications • XML text – Will you convert it back to sfm? – Or will you then switch publishing applications?

Practical things we can start doing • Work with NRSI on creating publishing fonts (typographical features) • Work with someone (LSDev? ) on preprocessing checks – works with Unicode and XML • Learn TECkit mapping • XML – Learning XSL/XSLT, creating XSL/XSLT stylesheets – Examine OSIS and XSEM from a publishing point of view and decide – Develop tools for markup conversion (to OSIS/XSEM) Yet to be decided (including C 2 X)

Practical things we can start doing… • Research and choose editing application • Research and choose publishing application – In. Design / Frame. Maker – Te. X related – XSL Formatter / Ultra. XML • Begin developing stylesheets, etc for application

For more information, contact: Non-Roman Script Initiative SIL International 7500 West Camp Wisdom Rd. Dallas, TX 75236 972 708 -7371 nrsi@sil. org http: //scripts. sil. org/ This presentation is © Copyright 2002 SIL International, and may not be reproduced without permission.