Jump to content

Single-source publishing: Difference between revisions

From Wikipedia, the free encyclopedia
Browse history interactively
← Previous edit
Content deleted Content added
VisualWikitext
VenrAmD (talk | contribs)
114 edits
m Added in 'RWS Tridion Docs' to the list as it's a single-source publishing tool.
 
(14 intermediate revisions by 12 users not shown)
Line 1: Line 1:
{{Short description|Content publishing method}}
'''Single-source publishing''', also known as '''single-sourcing publishing''', is a [[content management]] method which allows the same source [[Content (media)|content]] to be used across different forms of [[Media (communication)|media]] and more than one time.<ref>Kay Ethier, ''XML and FrameMaker'', pg. 19. [[New York City|New York]]: [[Apress]], 2004. {{ISBN|9781430207191}}</ref><ref>Lucas Walsh, "The Application of Single-Source Publishing to E-Government." Taken from ''Encyclopedia of Digital Government'', pg. 64. Eds. Ari-Veikko Anttiroiko and Matti Mälkiä. [[Hershey, Pennsylvania|Hershey]]: IGI Global, 2007. {{ISBN|9781591407904}}</ref><ref>[http://www.stylusstudio.com/single_source_publishing.html Single-Source Publishing] at [[Stylus Studio]]. Copyright © 2005-2013 [[Progress Software]]. Accessed June 11, 2013.</ref><ref name=petra>[http://www.writersua.com/articles/singlesource/ Single-Source Publishing with Flare]. Copyright © 2010 WritersUA. Published November 16, 2010; accessed June 11, 2013.</ref> The labor-intensive and expensive work of [[Technical editing#Technical editing|editing]] need only be carried out once, on only one document;<ref name=cms>Barry Schaeffer, [http://www.cmswire.com/cms/information-management/single-source-publishing-creating-customized-output-015069.php Single-Source Publishing: Creating Customized Output]. CMS Wire, 3 April 2012. Accessed 10 June 2013.</ref> that source document (the [[single source of truth]]) can then be stored in one place and reused.<ref>[[Ann Rockley]] and Charles Cooper, [https://books.google.com/books?id=82X6jGY_dHMC&pg=PT75&dq=single+source+publishing&hl=en&sa=X&ei=rRehU_TxFs2W0QXT6YCQAQ&ved=0CDoQ6AEwBg#v=onepage&q=single%20source%20publishing&f=false Managing Enterprise Content: A Unified Content Strategy], Chapter 5: Product content. 2nd ed. [[Berkeley, California|Berkeley]]: [[New Riders Press]], 2012. {{ISBN|9780132931649}}</ref> This reduces the potential for error, as corrections are only made one time in the source document.<ref>Janet Mackenzie, ''The Editor's Companion'', pg. 92. [[Cambridge]]: [[Cambridge University Press]], 2011. {{ISBN|9781107402188}}</ref>
'''Single-source publishing''', also known as '''single-sourcing publishing''', is a [[content management]] method which allows the same source [[Content (media)|content]] to be used across different forms of [[Media (communication)|media]] and more than one time.<ref>Kay Ethier, ''XML and FrameMaker'', pg. 19. [[New York City|New York]]: [[Apress]], 2004. {{ISBN|9781430207191}}</ref><ref>Lucas Walsh, "The Application of Single-Source Publishing to E-Government." Taken from ''Encyclopedia of Digital Government'', pg. 64. Eds. Ari-Veikko Anttiroiko and Matti Mälkiä. [[Hershey, Pennsylvania|Hershey]]: IGI Global, 2007. {{ISBN|9781591407904}}</ref><ref>[http://www.stylusstudio.com/single_source_publishing.html Single-Source Publishing] at [[Stylus Studio]]. Copyright © 2005-2013 [[Progress Software]]. Accessed June 11, 2013.</ref><ref name=petra>[http://www.writersua.com/articles/singlesource/ Single-Source Publishing with Flare]. Copyright © 2010 WritersUA. Published November 16, 2010; accessed June 11, 2013.</ref> The labor-intensive and expensive work of [[Technical editing#Technical editing|editing]] need only be carried out once, on only one document;<ref name=cms>Barry Schaeffer, [http://www.cmswire.com/cms/information-management/single-source-publishing-creating-customized-output-015069.php Single-Source Publishing: Creating Customized Output]. CMS Wire, 3 April 2012. Accessed 10 June 2013.</ref> that source document (the [[single source of truth]]) can then be stored in one place and reused.<ref>[[Ann Rockley]] and Charles Cooper, [https://books.google.com/books?id=82X6jGY_dHMC&dq=single+source+publishing&pg=PT75 Managing Enterprise Content: A Unified Content Strategy], Chapter 5: Product content. 2nd ed. [[Berkeley, California|Berkeley]]: [[New Riders Press]], 2012. {{ISBN|9780132931649}}</ref> This reduces the potential for error, as corrections are only made one time in the source document.<ref>Janet Mackenzie, ''The Editor's Companion'', pg. 92. [[Cambridge]]: [[Cambridge University Press]], 2011. {{ISBN|9781107402188}}</ref>


The benefits of single-source publishing primarily relate to the editor rather than the [[User (computing)|user]]. The user benefits from the consistency that single-sourcing brings to terminology and information. This assumes the content manager has applied an organized [[Conceptualization (information science)|conceptualization]] to the underlying content (A poor conceptualization can make single-source publishing less useful).<ref name=petra/> Single-source publishing is sometimes used synonymously with '''multi-channel publishing''' though whether or not the two terms are synonymous is a matter of discussion.<ref name=mek>[http://www.mekon.com/index.php/pages/knowledge_zone/single-sourcing-multi-channel-publishing/technology_standards Single-Source & Multi-Channel Publishing] {{webarchive|url=https://web.archive.org/web/20100406072258/http://www.mekon.com/index.php/pages/knowledge_zone/single-sourcing-multi-channel-publishing/technology_standards |date=2010-04-06 }}. © 2013 Mekon, accessed 23 June 2013.</ref>
The benefits of single-source publishing primarily relate to the editor rather than the [[User (computing)|user]]. The user benefits from the consistency that single-sourcing brings to terminology and information. This assumes the content manager has applied an organized [[Conceptualization (information science)|conceptualization]] to the underlying content (A poor conceptualization can make single-source publishing less useful).<ref name=petra/> Single-source publishing is sometimes used synonymously with '''multi-channel publishing''' though whether or not the two terms are synonymous is a matter of discussion.<ref name=mek>[http://www.mekon.com/index.php/pages/knowledge_zone/single-sourcing-multi-channel-publishing/technology_standards Single-Source & Multi-Channel Publishing] {{webarchive|url=https://web.archive.org/web/20100406072258/http://www.mekon.com/index.php/pages/knowledge_zone/single-sourcing-multi-channel-publishing/technology_standards |date=2010-04-06 }}. © 2013 Mekon, accessed 23 June 2013.</ref>
Line 7: Line 8:


==History==
==History==
The origins of single-source publishing lie, indirectly, with the release of [[Windows 3.0]] in 1990.<ref name=bob162>Bob Boiko, [https://books.google.com/books?id=p6nUDn3ZaBoC&pg=PA162&dq=Single+source+publishing&hl=en&sa=X&ei=CUiqU6LEDaLV0QXd44CQDw&ved=0CCoQ6AEwAzgK#v=onepage&q=Single%20source%20publishing&f=false Content Management Bible], pg. 162. [[Hoboken, New Jersey|Hoboken]]: [[John Wiley & Sons]], 2005. {{ISBN|9780764583643}}</ref> With the eclipsing of [[MS-DOS]] by [[graphical user interface]]s, help files went from being unreadable text along the bottom of the screen to hypertext systems such as [[WinHelp]]. On-screen help interfaces allowed software companies to cease the printing of large, expensive help manuals with their products, reducing costs for both producer and consumer. This system raised opportunities as well, and many developers fundamentally changed the way they thought about publishing. Writers of [[software documentation]] did not simply move from being writers of traditional bound books to writers of [[electronic publishing]], but rather they became authors of central documents which could be reused multiple times across multiple formats.<ref name=bob162/>
The origins of single-source publishing lie, indirectly, with the release of [[Windows 3.0]] in 1990.<ref name=bob162>Bob Boiko, [https://books.google.com/books?id=p6nUDn3ZaBoC&dq=Single+source+publishing&pg=PA162 Content Management Bible], pg. 162. [[Hoboken, New Jersey|Hoboken]]: [[John Wiley & Sons]], 2005. {{ISBN|9780764583643}}</ref> With the eclipsing of [[MS-DOS]] by [[graphical user interface]]s, help files went from being unreadable text along the bottom of the screen to hypertext systems such as [[WinHelp]]. On-screen help interfaces allowed software companies to cease the printing of large, expensive help manuals with their products, reducing costs for both producer and consumer. This system raised opportunities as well, and many developers fundamentally changed the way they thought about publishing. Writers of [[software documentation]] did not simply move from being writers of traditional bound books to writers of [[electronic publishing]], but rather they became authors of central documents which could be reused multiple times across multiple formats.<ref name=bob162/>


The first single-source publishing project was started in 1993 by Cornelia Hofmann at [[Schneider Electric]] in [[Seligenstadt]], using software based on [[Interleaf]] to automatically create paper documentation in multiple languages based on a single original source file.<ref>[https://books.google.com/books?id=inCeft4AkXcC&pg=PA65&dq=single+source+publishing&hl=en&sa=X&ei=rRehU_TxFs2W0QXT6YCQAQ&ved=0CCoQ6AEwAw#v=onepage&q=single%20source%20publishing&f=false Translating Into Success: Cutting-edge Strategies for Going Multilingual in a Global Age], pg. 227. Eds. Robert C. Sprung and Simone Jaroniec. [[Amsterdam]]: [[John Benjamins Publishing Company]], 2000. {{ISBN|9789027231871}}</ref>
The first single-source publishing project was started in 1993 by Cornelia Hofmann at [[Schneider Electric]] in [[Seligenstadt]], using software based on [[Interleaf]] to automatically create paper documentation in multiple languages based on a single original source file.<ref>[https://books.google.com/books?id=inCeft4AkXcC&dq=single+source+publishing&pg=PA65 Translating Into Success: Cutting-edge Strategies for Going Multilingual in a Global Age], pg. 227. Eds. Robert C. Sprung and Simone Jaroniec. [[Amsterdam]]: [[John Benjamins Publishing Company]], 2000. {{ISBN|9789027231871}}</ref>


[[XML]], developed during the mid- to late-1990s, was also significant to the development of single-source publishing as a method. XML, a markup language, allows developers to separate their documentation into two layers: a shell-like layer based on presentation and a core-like layer based on the actual written content. This method allows developers to write the content only one time while switching it in and out of multiple different formats and delivery methods.<ref>Doug Wallace and Anthony Levinson, "The XML e-Learning Revolution: Is Your Production Model Holding You Back?" Taken from [https://books.google.com/books?id=4RK7tJ-OO3cC&pg=PA65&dq=Single+source+publishing&hl=en&sa=X&ei=CUiqU6LEDaLV0QXd44CQDw&ved=0CEgQ6AEwCDgK#v=onepage&q=Single%20source%20publishing&f=false Best of The eLearning Guild's Learning Solutions: Articles from the eMagazine's First Five Years], pg. 63. Ed. Bill Brandon. Hoboken: John Wiley & Sons, 2008. {{ISBN|9780470277157}}</ref>
[[XML]], developed during the mid- to late-1990s, was also significant to the development of single-source publishing as a method. XML, a markup language, allows developers to separate their documentation into two layers: a shell-like layer based on presentation and a core-like layer based on the actual written content. This method allows developers to write the content only one time while switching it in and out of multiple different formats and delivery methods.<ref>Doug Wallace and Anthony Levinson, "The XML e-Learning Revolution: Is Your Production Model Holding You Back?" Taken from [https://books.google.com/books?id=4RK7tJ-OO3cC&dq=Single+source+publishing&pg=PA65 Best of The eLearning Guild's Learning Solutions: Articles from the eMagazine's First Five Years], pg. 63. Ed. Bill Brandon. Hoboken: John Wiley & Sons, 2008. {{ISBN|9780470277157}}</ref>


In the mid-1990s, several firms began creating and using single-source content for technical documentation (Boeing Helicopter, Sikorsky Aviation and Pratt & Whitney Canada) and user manuals (Ford owners manuals) based on tagged SGML and XML content generated using the Arbortext Epic editor with add-on functions developed by a contractor.<ref>{{Cite web|title=Pratt And Whitney Canada Manuals|url=https://pdflife.one/download/4574326-pratt-and-whitney-canada-manuals|access-date=2022-02-17|website=pdflife.one|language=EN}}</ref> The concept behind this usage was that complex, hierarchical content that did not lend itself to discrete componentization could be used across a variety of requirements by tagging the differences within a single document using the capabilities built into SGML and XML.
In the mid-1990s, several firms began creating and using single-source content for technical documentation (Boeing Helicopter, Sikorsky Aviation and Pratt & Whitney Canada) and user manuals (Ford owners manuals) based on tagged SGML and XML content generated using the Arbortext Epic editor with add-on functions developed by a contractor.<ref>{{Cite web|title=Pratt And Whitney Canada Manuals|url=https://pdflife.one/download/4574326-pratt-and-whitney-canada-manuals|access-date=2022-02-17|website=pdflife.one|language=EN}}</ref> The concept behind this usage was that complex, hierarchical content that did not lend itself to discrete componentization could be used across a variety of requirements by tagging the differences within a single document using the capabilities built into SGML and XML.<ref>{{Cite web|title=Getting Started with SGML/XML|url=https://www.oasis-open.org/docbook/documentation/reference/html/ch01.html|access-date=2022-02-17|website=www.oasis-open.org}}</ref>
Ford, for example, was able to tag its single owner's manual files so that 12 model years could be generated via a resolution script running on the single completed file. Pratt & Whitney, likewise, was able to tag up to 20 subsets of its jet engine manuals in single-source files, calling out the desired version at publication time. [[World Book Encyclopedia]] also used the concept to tag its articles for American and British versions of English.<ref>{{Cite web|date=2012-06-19|title=The World Book Encyclopedia|url=https://web.archive.org/web/20120619073314/http://www.indiana.edu/~librcsd/libguide/ency/12.html|access-date=2022-02-17|website=web.archive.org}}</ref>
Ford, for example, was able to tag its single owner's manual files so that 12 model years could be generated via a resolution script running on the single completed file. Pratt & Whitney, likewise, was able to tag up to 20 subsets of its jet engine manuals in single-source files, calling out the desired version at publication time. [[World Book Encyclopedia]] also used the concept to tag its articles for American and British versions of English.<ref>{{Cite web |date=2012-06-19 |title=The World Book Encyclopedia |url=http://www.indiana.edu/~librcsd/libguide/ency/12.html |access-date=2022-02-17 |website= |archive-url=https://web.archive.org/web/20120619073314/http://www.indiana.edu/~librcsd/libguide/ency/12.html |archive-date=19 June 2012 |url-status=dead}}</ref>


Starting from the early 2000s, single-source publishing was used with an increasing frequency in the field of [[technical translation]]. It is still regarded as the most efficient method of publishing the same material in different languages.<ref>Bert Esselink, "Localisation and translation." Taken from [https://books.google.com/books?id=a4W7lWgCqYoC&pg=PA73&dq=Single+source+publishing&hl=en&sa=X&ei=CUiqU6LEDaLV0QXd44CQDw&ved=0CCUQ6AEwAjgK#v=onepage&q=Single%20source%20publishing&f=false Computers and Translation: A Translator's Guide], pg. 73. Ed. H. L. Somers. [[Amsterdam]]: [[John Benjamins Publishing Company]], 2003. {{ISBN|9789027216403}}</ref> Once a printed manual was translated, for example, the online help for the software program which the manual accompanies could be automatically generated using the method.<ref>Burt Esselink, ''A Practical Guide to Localization'', pg. 228. Volume 4 of Language international world directory. [[Amsterdam]]: [[John Benjamins Publishing Company]], 2000. {{ISBN|9781588110060}}</ref> [[Metadata]] could be created for an entire manual and individual pages or files could then be translated from that metadata with only one step, removing the need to recreate information or even database structures.<ref>Cornelia Hofmann and Thorsten Mehnert, "Multilingual Information Management at Schneider Automation." Taken from ''Translating Into Success'', pg. 67.</ref>
Starting from the early 2000s, single-source publishing was used with an increasing frequency in the field of [[technical translation]]. It is still regarded as the most efficient method of publishing the same material in different languages.<ref>Bert Esselink, "Localisation and translation." Taken from [https://books.google.com/books?id=a4W7lWgCqYoC&dq=Single+source+publishing&pg=PA73 Computers and Translation: A Translator's Guide], pg. 73. Ed. H. L. Somers. [[Amsterdam]]: [[John Benjamins Publishing Company]], 2003. {{ISBN|9789027216403}}</ref> Once a printed manual was translated, for example, the online help for the software program which the manual accompanies could be automatically generated using the method.<ref>Burt Esselink, ''A Practical Guide to Localization'', pg. 228. Volume 4 of Language international world directory. [[Amsterdam]]: [[John Benjamins Publishing Company]], 2000. {{ISBN|9781588110060}}</ref> [[Metadata]] could be created for an entire manual and individual pages or files could then be translated from that metadata with only one step, removing the need to recreate information or even database structures.<ref>Cornelia Hofmann and Thorsten Mehnert, "Multilingual Information Management at Schneider Automation." Taken from ''Translating Into Success'', pg. 67.</ref>


Although single-source publishing is now decades old, its importance has increased urgently as of the 2010s. As consumption of information products rises and the number of target audiences expands, so does the work of developers and content creators. Within the industry of software and its documentation, there is a perception that the choice is to embrace single-source publishing or render one's operations obsolete.<ref name=cms/>
Although single-source publishing is now decades old, its importance has increased urgently as of the 2010s. As consumption of information products rises and the number of target audiences expands, so does the work of developers and content creators. Within the industry of software and its documentation, there is a perception that the choice is to embrace single-source publishing or render one's operations obsolete.<ref name=cms/>


==Criticism==
==Criticism==
Editors using single-source publishing have been criticized for below-standard work quality, leading some critics to describe single-source publishing as the "conveyor belt assembly" of content creation.<ref>Mick Hiatt, [http://mashstream.com/mashups/the-myth-of-single-source-authoring/ The Myth of Single-Source Authoring] {{webarchive|url=https://web.archive.org/web/20130929043721/http://mashstream.com/mashups/the-myth-of-single-source-authoring/ |date=2013-09-29 }}. Mashstream, November 18, 2009.</ref>
Editors using single-source publishing have been criticized for below-standard work quality, leading some critics to describe single-source publishing as the "conveyor belt assembly" of content creation.<ref>Mick Hiatt, [http://mashstream.com/mashups/the-myth-of-single-source-authoring/ The Myth of Single-Source Authoring] {{webarchive|url=https://web.archive.org/web/20130929043721/http://mashstream.com/mashups/the-myth-of-single-source-authoring/ |date=2013-09-29 }}, {{webarchive|url=https://archive.today/20130427015014/http://mashstream.com/mashups/the-myth-of-single-source-authoring/|date=2013-04-27}}. Mashstream, November 18, 2009.</ref>


While heavily used in technical translation, there are risks of error in regard to [[Index (publishing)|indexing]]. While two words might be [[synonym]]s in English, they may not be synonyms in another language. In a document produced via single-sourcing, the index will be translated automatically and the two words will be rendered as synonyms. This is because they are synonyms in the [[Source language (translation)|source language]], while in the [[Target language (translation)|target language]] they are not.<ref>Nancy Mulvany, [https://books.google.com/books?id=G0Eqm8FbiTMC&pg=PA312&dq=single+source+publishing&hl=en&sa=X&ei=rRehU_TxFs2W0QXT6YCQAQ&ved=0CEcQ6AEwCA#v=onepage&q=single%20source%20publishing&f=false Indexing Books], pg. 154. 2nd ed. [[Chicago]]: [[University of Chicago Press]], 2009. {{ISBN|9780226550176}}</ref>
While heavily used in technical translation, there are risks of error in regard to [[Index (publishing)|indexing]]. While two words might be [[synonym]]s in English, they may not be synonyms in another language. In a document produced via single-sourcing, the index will be translated automatically and the two words will be rendered as synonyms. This is because they are synonyms in the [[Source language (translation)|source language]], while in the [[Target language (translation)|target language]] they are not.<ref>Nancy Mulvany, [https://books.google.com/books?id=G0Eqm8FbiTMC&dq=single+source+publishing&pg=PA312 Indexing Books], pg. 154. 2nd ed. [[Chicago]]: [[University of Chicago Press]], 2009. {{ISBN|9780226550176}}</ref>


==See also==
==See also==
Line 33: Line 34:


===List of single-source publishing tools===
===List of single-source publishing tools===
* [[Adobe FrameMaker]]<ref>Sarah S. O'Keefe, Sheila A. Loring, Terry Smith and Lydia K. Wong, [https://books.google.com/books?id=b-yEKgcQmN8C&pg=PA6&dq=single+source+publishing&hl=en&sa=X&ei=rRehU_TxFs2W0QXT6YCQAQ&ved=0CE0Q6AEwCQ#v=onepage&q=single%20source%20publishing&f=false Publishing Fundamentals: Unstructured FrameMaker 8], pg. 6. Scriptorium Publishing, 2008. {{ISBN|9780970473349}}</ref>
* [[Adobe FrameMaker]]<ref>Sarah S. O'Keefe, Sheila A. Loring, Terry Smith and Lydia K. Wong, [https://books.google.com/books?id=b-yEKgcQmN8C&dq=single+source+publishing&pg=PA6 Publishing Fundamentals: Unstructured FrameMaker 8], pg. 6. Scriptorium Publishing, 2008. {{ISBN|9780970473349}}</ref>
* [[Adobe RoboHelp]]
* [[Adobe RoboHelp]]
* [[Apache Cocoon]]
* [[Apache Cocoon]]
Line 39: Line 40:
* [[Altova]]
* [[Altova]]
* [[Booktype]]
* [[Booktype]]
*[https://clickhelp.com/ ClickHelp]
* [[DocBook XSL]]
* [[DocBook XSL]]
* [[DITA Open Toolkit]]
* [[DITA Open Toolkit]]
*[https://easydita.com easyDITA]
*[https://www.heretto.com/ Heretto]
* [[Help & Manual]]
* Help & Manual
* [[HelpNDoc]]
* [[HelpNDoc]]
* [[MadCap Flare]]
* [[MadCap Flare]]
* [[Oxygen XML Editor|Oxygen XML editor]]
* [[Oxygen XML Editor|Oxygen XML editor]]
* [https://paligo.net/ Paligo]
* [https://paligo.net/ Paligo]
* [https://www.rws.com/content-management/tridion/docs/ RWS Tridion Docs]
* [[Scenari]]
* [[Scenari]]
* [[Sphinx (documentation generator)|Sphinx]]<ref>{{cite web | url = http://pythonic.pocoo.org/2008/3/21/sphinx-is-released | title = Sphinx is released! &raquo; And now for something completely Pythonic... | publisher = Georg Brandl | work = And now for something completely Pythonic... | access-date = 2011-04-03 | url-status = dead | archive-url = https://web.archive.org/web/20120322064904/http://pythonic.pocoo.org/2008/3/21/sphinx-is-released | archive-date = 2012-03-22 }}</ref>
* [[Sphinx (documentation generator)|Sphinx]]<ref>{{cite web | url = http://pythonic.pocoo.org/2008/3/21/sphinx-is-released | title = Sphinx is released! » And now for something completely Pythonic... | publisher = Georg Brandl | work = And now for something completely Pythonic... | access-date = 2011-04-03 | url-status = dead | archive-url = https://web.archive.org/web/20120322064904/http://pythonic.pocoo.org/2008/3/21/sphinx-is-released | archive-date = 2012-03-22 }}</ref>
* [https://typefi.com/ Typefi]
* [[XPLM Publisher]]
* [[XPLM Publisher]]


Latest revision as of 17:40, 30 September 2024

Single-source publishing, also known as single-sourcing publishing, is a content management method which allows the same source content to be used across different forms of media and more than one time.[1][2][3][4] The labor-intensive and expensive work of editing need only be carried out once, on only one document;[5] that source document (the single source of truth) can then be stored in one place and reused.[6] This reduces the potential for error, as corrections are only made one time in the source document.[7]

The benefits of single-source publishing primarily relate to the editor rather than the user. The user benefits from the consistency that single-sourcing brings to terminology and information. This assumes the content manager has applied an organized conceptualization to the underlying content (A poor conceptualization can make single-source publishing less useful).[4] Single-source publishing is sometimes used synonymously with multi-channel publishing though whether or not the two terms are synonymous is a matter of discussion.[8]

Definition

[edit]

While there is a general definition of single-source publishing, there is no single official delineation between single-source publishing and multi-channel publishing, nor are there any official governing bodies to provide such a delineation. Single-source publishing is most often understood as the creation of one source document in an authoring tool and converting that document into different file formats or human languages (or both) multiple times with minimal effort. Multi-channel publishing can either be seen as synonymous with single-source publishing, or similar in that there is one source document but the process itself results in more than a mere reproduction of that source.[8]

History

[edit]

The origins of single-source publishing lie, indirectly, with the release of Windows 3.0 in 1990.[9] With the eclipsing of MS-DOS by graphical user interfaces, help files went from being unreadable text along the bottom of the screen to hypertext systems such as WinHelp. On-screen help interfaces allowed software companies to cease the printing of large, expensive help manuals with their products, reducing costs for both producer and consumer. This system raised opportunities as well, and many developers fundamentally changed the way they thought about publishing. Writers of software documentation did not simply move from being writers of traditional bound books to writers of electronic publishing, but rather they became authors of central documents which could be reused multiple times across multiple formats.[9]

The first single-source publishing project was started in 1993 by Cornelia Hofmann at Schneider Electric in Seligenstadt, using software based on Interleaf to automatically create paper documentation in multiple languages based on a single original source file.[10]

XML, developed during the mid- to late-1990s, was also significant to the development of single-source publishing as a method. XML, a markup language, allows developers to separate their documentation into two layers: a shell-like layer based on presentation and a core-like layer based on the actual written content. This method allows developers to write the content only one time while switching it in and out of multiple different formats and delivery methods.[11]

In the mid-1990s, several firms began creating and using single-source content for technical documentation (Boeing Helicopter, Sikorsky Aviation and Pratt & Whitney Canada) and user manuals (Ford owners manuals) based on tagged SGML and XML content generated using the Arbortext Epic editor with add-on functions developed by a contractor.[12] The concept behind this usage was that complex, hierarchical content that did not lend itself to discrete componentization could be used across a variety of requirements by tagging the differences within a single document using the capabilities built into SGML and XML.[13] Ford, for example, was able to tag its single owner's manual files so that 12 model years could be generated via a resolution script running on the single completed file. Pratt & Whitney, likewise, was able to tag up to 20 subsets of its jet engine manuals in single-source files, calling out the desired version at publication time. World Book Encyclopedia also used the concept to tag its articles for American and British versions of English.[14]

Starting from the early 2000s, single-source publishing was used with an increasing frequency in the field of technical translation. It is still regarded as the most efficient method of publishing the same material in different languages.[15] Once a printed manual was translated, for example, the online help for the software program which the manual accompanies could be automatically generated using the method.[16] Metadata could be created for an entire manual and individual pages or files could then be translated from that metadata with only one step, removing the need to recreate information or even database structures.[17]

Although single-source publishing is now decades old, its importance has increased urgently as of the 2010s. As consumption of information products rises and the number of target audiences expands, so does the work of developers and content creators. Within the industry of software and its documentation, there is a perception that the choice is to embrace single-source publishing or render one's operations obsolete.[5]

Criticism

[edit]

Editors using single-source publishing have been criticized for below-standard work quality, leading some critics to describe single-source publishing as the "conveyor belt assembly" of content creation.[18]

While heavily used in technical translation, there are risks of error in regard to indexing. While two words might be synonyms in English, they may not be synonyms in another language. In a document produced via single-sourcing, the index will be translated automatically and the two words will be rendered as synonyms. This is because they are synonyms in the source language, while in the target language they are not.[19]

See also

[edit]

List of single-source publishing tools

[edit]

References

[edit]
  1. ^ Kay Ethier, XML and FrameMaker, pg. 19. New York: Apress, 2004. ISBN 9781430207191
  2. ^ Lucas Walsh, "The Application of Single-Source Publishing to E-Government." Taken from Encyclopedia of Digital Government, pg. 64. Eds. Ari-Veikko Anttiroiko and Matti Mälkiä. Hershey: IGI Global, 2007. ISBN 9781591407904
  3. ^ Single-Source Publishing at Stylus Studio. Copyright © 2005-2013 Progress Software. Accessed June 11, 2013.
  4. ^ a b Single-Source Publishing with Flare. Copyright © 2010 WritersUA. Published November 16, 2010; accessed June 11, 2013.
  5. ^ a b Barry Schaeffer, Single-Source Publishing: Creating Customized Output. CMS Wire, 3 April 2012. Accessed 10 June 2013.
  6. ^ Ann Rockley and Charles Cooper, Managing Enterprise Content: A Unified Content Strategy, Chapter 5: Product content. 2nd ed. Berkeley: New Riders Press, 2012. ISBN 9780132931649
  7. ^ Janet Mackenzie, The Editor's Companion, pg. 92. Cambridge: Cambridge University Press, 2011. ISBN 9781107402188
  8. ^ a b Single-Source & Multi-Channel Publishing Archived 2010-04-06 at the Wayback Machine. © 2013 Mekon, accessed 23 June 2013.
  9. ^ a b Bob Boiko, Content Management Bible, pg. 162. Hoboken: John Wiley & Sons, 2005. ISBN 9780764583643
  10. ^ Translating Into Success: Cutting-edge Strategies for Going Multilingual in a Global Age, pg. 227. Eds. Robert C. Sprung and Simone Jaroniec. Amsterdam: John Benjamins Publishing Company, 2000. ISBN 9789027231871
  11. ^ Doug Wallace and Anthony Levinson, "The XML e-Learning Revolution: Is Your Production Model Holding You Back?" Taken from Best of The eLearning Guild's Learning Solutions: Articles from the eMagazine's First Five Years, pg. 63. Ed. Bill Brandon. Hoboken: John Wiley & Sons, 2008. ISBN 9780470277157
  12. ^ "Pratt And Whitney Canada Manuals". pdflife.one. Retrieved 2022-02-17.
  13. ^ "Getting Started with SGML/XML". www.oasis-open.org. Retrieved 2022-02-17.
  14. ^ "The World Book Encyclopedia". 2012-06-19. Archived from the original on 19 June 2012. Retrieved 2022-02-17.
  15. ^ Bert Esselink, "Localisation and translation." Taken from Computers and Translation: A Translator's Guide, pg. 73. Ed. H. L. Somers. Amsterdam: John Benjamins Publishing Company, 2003. ISBN 9789027216403
  16. ^ Burt Esselink, A Practical Guide to Localization, pg. 228. Volume 4 of Language international world directory. Amsterdam: John Benjamins Publishing Company, 2000. ISBN 9781588110060
  17. ^ Cornelia Hofmann and Thorsten Mehnert, "Multilingual Information Management at Schneider Automation." Taken from Translating Into Success, pg. 67.
  18. ^ Mick Hiatt, The Myth of Single-Source Authoring Archived 2013-09-29 at the Wayback Machine, Archived 2013-04-27 at archive.today. Mashstream, November 18, 2009.
  19. ^ Nancy Mulvany, Indexing Books, pg. 154. 2nd ed. Chicago: University of Chicago Press, 2009. ISBN 9780226550176
  20. ^ Sarah S. O'Keefe, Sheila A. Loring, Terry Smith and Lydia K. Wong, Publishing Fundamentals: Unstructured FrameMaker 8, pg. 6. Scriptorium Publishing, 2008. ISBN 9780970473349
  21. ^ "Sphinx is released! » And now for something completely Pythonic..." And now for something completely Pythonic... Georg Brandl. Archived from the original on 2012-03-22. Retrieved 2011-04-03.

Further reading

[edit]
  • Ament, Kurt (2007-12-17). Single Sourcing: Building Modular Documentation. William Andrew. p. 245. ISBN 978-0-8155-1491-6.
  • Hackos, JoAnn T. (2002-02-14). Content Management for Dynamic Web Delivery. Wiley. p. 432. ISBN 0-471-08586-3.
  • Glushko, Robert J.; Tim McGrath (2005). Document Engineering: Analyzing and Designing Documents for Business Informatics and Web Services. MIT Press. p. 728. ISBN 0-262-57245-1.
  • Maler, Eve; Jeanne El Andaloussi (1995-12-15). Developing SGML DTDs: From Text to Model to Markup. Prentice Hall PTR. p. 560. ISBN 0-13-309881-8. (the "bible" for Data Modeling)
[edit]
Retrieved from "https://en.wikipedia.org/enwiki/w/index.php?title=Single-source_publishing&oldid=1248643139"