135:
add-on functions developed by a contractor. 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. 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.
131:, 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.
102:. 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
134:
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
69:
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
154:
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
146:. It is still regarded as the most efficient method of publishing the same material in different languages. 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.
78:(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.
175:
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
928:
163:
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.
150:
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.
500:
57:
to the underlying content (A poor conceptualization can make single-source publishing less useful). Single-source publishing is sometimes used synonymously with
53:. The user benefits from the consistency that single-sourcing brings to terminology and information. This assumes the content manager has applied an organized
497:
423:
240:
46:) can then be stored in one place and reused. This reduces the potential for error, as corrections are only made one time in the source document.
740:
748:
298:
813:
643:
155:
documentation, there is a perception that the choice is to embrace single-source publishing or render one's operations obsolete.
54:
198:
765:
520:
854:
668:
575:
547:
439:
793:
574:
Doug
Wallace and Anthony Levinson, "The XML e-Learning Revolution: Is Your Production Model Holding You Back?" Taken from
911:
892:
873:
801:
781:
712:
704:
684:
676:
583:
563:
555:
536:
483:
455:
373:
349:
110:, but rather they became authors of central documents which could be reused multiple times across multiple formats.
971:
303:
723:
Cornelia
Hofmann and Thorsten Mehnert, "Multilingual Information Management at Schneider Automation." Taken from
976:
142:
Starting from the early 2000s, single-source publishing was used with an increasing frequency in the field of
955:
181:
177:
619:
125:
to automatically create paper documentation in multiple languages based on a single original source file.
773:
98:, help files went from being unreadable text along the bottom of the screen to hypertext systems such as
595:
475:
39:
737:
981:
95:
939:
885:
Document
Engineering: Analyzing and Designing Documents for Business Informatics and Web Services
136:
70:
creation of one source document in an authoring tool and converting that document into different
576:
Best of The eLearning Guild's
Learning Solutions: Articles from the eMagazine's First Five Years
949:
103:
43:
365:
143:
107:
35:
384:
528:
443:
8:
820:
524:
647:
548:
Translating Into
Success: Cutting-edge Strategies for Going Multilingual in a Global Age
139:
also used the concept to tag its articles for
American and British versions of English.
49:
The benefits of single-source publishing primarily relate to the editor rather than the
360:
Lucas Walsh, "The
Application of Single-Source Publishing to E-Government." Taken from
193:
168:
114:
27:
113:
The first single-source publishing project was started in 1993 by
Cornelia Hofmann at
907:
888:
869:
850:
797:
777:
708:
680:
579:
559:
532:
479:
451:
392:
369:
345:
288:
265:
934:
447:
225:
167:
While heavily used in technical translation, there are risks of error in regard to
50:
410:. Copyright © 2010 WritersUA. Published November 16, 2010; accessed June 11, 2013.
407:
744:
504:
208:
31:
106:
did not simply move from being writers of traditional bound books to writers of
313:
230:
42:
need only be carried out once, on only one document; that source document (the
61:
though whether or not the two terms are synonymous is a matter of discussion.
965:
752:
388:
337:
235:
86:
The origins of single-source publishing lie, indirectly, with the release of
940:
Single Sourcing Information - An Agile Practice for Effective Documentation
283:
118:
945:
Society for Technical Communication Single-sourcing Special Interest Group
931:(A paper presented by Peter Meyer at OpenPublish, Sydney, on 29 July 2005)
935:
Single-source publishing in multiple formats for different output devices
814:"Sphinx is released! » And now for something completely Pythonic..."
435:
260:
87:
71:
929:
Planning a Single Source Publishing Application for Business Documents
958:(Articles about Information Development and Single Source Publishing)
700:
672:
551:
471:
122:
792:
Sarah S. O'Keefe, Sheila A. Loring, Terry Smith and Lydia K. Wong,
278:
250:
147:
75:
578:, pg. 63. Ed. Bill Brandon. Hoboken: John Wiley & Sons, 2008.
38:
and more than one time. The labor-intensive and expensive work of
769:
213:
172:
99:
699:, pg. 228. Volume 4 of Language international world directory.
341:
245:
91:
944:
270:
203:
667:
Bert Esselink, "Localisation and translation." Taken from
901:
255:
219:
128:
440:
Managing Enterprise Content: A Unified Content Strategy
364:, pg. 64. Eds. Ari-Veikko Anttiroiko and Matti Mälkiä.
550:, pg. 227. Eds. Robert C. Sprung and Simone Jaroniec.
308:
293:
424:
Single-Source Publishing: Creating Customized Output
904:Developing SGML DTDs: From Text to Model to Markup
882:
794:Publishing Fundamentals: Unstructured FrameMaker 8
963:
426:. CMS Wire, 3 April 2012. Accessed 10 June 2013.
902:Maler, Eve; Jeanne El Andaloussi (1995-12-15).
847:Single Sourcing: Building Modular Documentation
669:Computers and Translation: A Translator's Guide
498:Single-Source & Multi-Channel Publishing
866:Content Management for Dynamic Web Delivery
817:And now for something completely Pythonic..
883:Glushko, Robert J.; Tim McGrath (2005).
515:
513:
796:, pg. 6. Scriptorium Publishing, 2008.
403:
401:
964:
863:
507:. © 2013 Mekon, accessed 23 June 2013.
442:, Chapter 5: Product content. 2nd ed.
220:List of single-source publishing tools
199:Darwin Information Typing Architecture
844:
510:
493:
491:
418:
416:
34:to be used across different forms of
398:
30:method which allows the same source
738:The Myth of Single-Source Authoring
408:Single-Source Publishing with Flare
13:
906:. Prentice Hall PTR. p. 560.
838:
596:"Pratt And Whitney Canada Manuals"
488:
413:
362:Encyclopedia of Digital Government
14:
993:
950:What Is Single Source Publishing?
922:
705:John Benjamins Publishing Company
697:A Practical Guide to Localization
677:John Benjamins Publishing Company
556:John Benjamins Publishing Company
755:. Mashstream, November 18, 2009.
918:(the "bible" for Data Modeling)
864:Hackos, JoAnn T. (2002-02-14).
849:. William Andrew. p. 245.
806:
786:
758:
730:
717:
689:
661:
636:
620:"Getting Started with SGML/XML"
612:
588:
568:
541:
90:in 1990. With the eclipsing of
819:. Georg Brandl. Archived from
460:
429:
378:
354:
326:
1:
644:"The World Book Encyclopedia"
319:
64:
671:, pg. 73. Ed. H. L. Somers.
646:. 2012-06-19. Archived from
158:
7:
774:University of Chicago Press
187:
171:. While two words might be
10:
998:
887:. MIT Press. p. 728.
845:Ament, Kurt (2007-12-17).
476:Cambridge University Press
121:, using software based on
81:
24:single-sourcing publishing
395:. Accessed June 11, 2013.
96:graphical user interfaces
16:Content publishing method
725:Translating Into Success
521:Content Management Bible
391:. Copyright © 2005-2013
385:Single-Source Publishing
59:multi-channel publishing
20:Single-source publishing
972:Technical communication
137:World Book Encyclopedia
868:. Wiley. p. 432.
468:The Editor's Companion
104:software documentation
44:single source of truth
977:Computer file systems
529:John Wiley & Sons
144:technical translation
108:electronic publishing
438:and Charles Cooper,
368:: IGI Global, 2007.
768:, pg. 154. 2nd ed.
743:2013-09-29 at the
624:www.oasis-open.org
503:2010-04-06 at the
334:XML and FrameMaker
194:Content management
115:Schneider Electric
28:content management
856:978-0-8155-1491-6
466:Janet Mackenzie,
422:Barry Schaeffer,
393:Progress Software
289:Oxygen XML editor
275:Help & Manual
266:DITA Open Toolkit
55:conceptualization
989:
917:
898:
879:
860:
832:
831:
829:
828:
810:
804:
790:
784:
762:
756:
734:
728:
721:
715:
693:
687:
665:
659:
658:
656:
655:
640:
634:
633:
631:
630:
616:
610:
609:
607:
606:
592:
586:
572:
566:
545:
539:
517:
508:
495:
486:
464:
458:
448:New Riders Press
433:
427:
420:
411:
405:
396:
382:
376:
358:
352:
330:
226:Adobe FrameMaker
22:, also known as
997:
996:
992:
991:
990:
988:
987:
986:
982:Data management
962:
961:
925:
914:
895:
876:
857:
841:
839:Further reading
836:
835:
826:
824:
812:
811:
807:
791:
787:
764:Nancy Mulvany,
763:
759:
745:Wayback Machine
735:
731:
722:
718:
695:Burt Esselink,
694:
690:
666:
662:
653:
651:
650:on 19 June 2012
642:
641:
637:
628:
626:
618:
617:
613:
604:
602:
594:
593:
589:
573:
569:
546:
542:
518:
511:
505:Wayback Machine
496:
489:
465:
461:
434:
430:
421:
414:
406:
399:
383:
379:
359:
355:
331:
327:
322:
222:
209:Markup language
190:
182:target language
180:, while in the
178:source language
161:
84:
67:
17:
12:
11:
5:
995:
985:
984:
979:
974:
960:
959:
953:
947:
942:
937:
932:
924:
923:External links
921:
920:
919:
912:
899:
893:
880:
874:
861:
855:
840:
837:
834:
833:
805:
785:
766:Indexing Books
757:
751:2013-04-27 at
729:
716:
688:
660:
635:
611:
587:
567:
540:
509:
487:
459:
428:
412:
397:
377:
353:
324:
323:
321:
318:
317:
316:
314:XPLM Publisher
311:
306:
301:
296:
291:
286:
281:
276:
273:
268:
263:
258:
253:
248:
243:
241:Apache Forrest
238:
233:
231:Adobe RoboHelp
228:
221:
218:
217:
216:
211:
206:
201:
196:
189:
186:
184:they are not.
160:
157:
83:
80:
66:
63:
15:
9:
6:
4:
3:
2:
994:
983:
980:
978:
975:
973:
970:
969:
967:
957:
954:
951:
948:
946:
943:
941:
938:
936:
933:
930:
927:
926:
915:
913:0-13-309881-8
909:
905:
900:
896:
894:0-262-57245-1
890:
886:
881:
877:
875:0-471-08586-3
871:
867:
862:
858:
852:
848:
843:
842:
823:on 2012-03-22
822:
818:
815:
809:
803:
802:9780970473349
799:
795:
789:
783:
782:9780226550176
779:
775:
771:
767:
761:
754:
753:archive.today
750:
746:
742:
739:
733:
726:
720:
714:
713:9781588110060
710:
706:
702:
698:
692:
686:
685:9789027216403
682:
678:
674:
670:
664:
649:
645:
639:
625:
621:
615:
601:
597:
591:
585:
584:9780470277157
581:
577:
571:
565:
564:9789027231871
561:
557:
553:
549:
544:
538:
537:9780764583643
534:
530:
526:
522:
516:
514:
506:
502:
499:
494:
492:
485:
484:9781107402188
481:
477:
473:
469:
463:
457:
456:9780132931649
453:
449:
445:
441:
437:
432:
425:
419:
417:
409:
404:
402:
394:
390:
389:Stylus Studio
386:
381:
375:
374:9781591407904
371:
367:
363:
357:
351:
350:9781430207191
347:
343:
339:
335:
329:
325:
315:
312:
310:
307:
305:
302:
300:
297:
295:
292:
290:
287:
285:
282:
280:
277:
274:
272:
269:
267:
264:
262:
259:
257:
254:
252:
249:
247:
244:
242:
239:
237:
236:Apache Cocoon
234:
232:
229:
227:
224:
223:
215:
212:
210:
207:
205:
202:
200:
197:
195:
192:
191:
185:
183:
179:
174:
170:
165:
156:
152:
149:
145:
140:
138:
132:
130:
126:
124:
120:
116:
111:
109:
105:
101:
97:
93:
89:
79:
77:
73:
62:
60:
56:
52:
47:
45:
41:
37:
33:
29:
25:
21:
956:tekom Europe
903:
884:
865:
846:
825:. Retrieved
821:the original
816:
808:
788:
760:
736:Mick Hiatt,
732:
724:
719:
696:
691:
663:
652:. Retrieved
648:the original
638:
627:. Retrieved
623:
614:
603:. Retrieved
599:
590:
570:
543:
467:
462:
431:
380:
361:
356:
333:
332:Kay Ethier,
328:
284:MadCap Flare
166:
162:
153:
141:
133:
127:
119:Seligenstadt
112:
85:
72:file formats
68:
58:
48:
23:
19:
18:
952:at WiseGeek
600:pdflife.one
523:, pg. 162.
519:Bob Boiko,
436:Ann Rockley
261:DocBook XSL
88:Windows 3.0
966:Categories
827:2011-04-03
654:2022-02-17
629:2022-02-17
605:2022-02-17
470:, pg. 92.
336:, pg. 19.
320:References
65:Definition
727:, pg. 67.
701:Amsterdam
673:Amsterdam
552:Amsterdam
472:Cambridge
256:ClickHelp
159:Criticism
123:Interleaf
76:languages
74:or human
776:, 2009.
749:Archived
741:Archived
707:, 2000.
679:, 2003.
558:, 2000.
531:, 2005.
501:Archived
478:, 2011.
450:, 2012.
444:Berkeley
344:, 2004.
338:New York
279:HelpNDoc
251:Booktype
188:See also
173:synonyms
169:indexing
148:Metadata
770:Chicago
525:Hoboken
366:Hershey
299:Scenari
271:Heretto
214:DocBook
100:WinHelp
82:History
40:editing
32:content
26:, is a
910:
891:
872:
853:
800:
780:
711:
683:
582:
562:
535:
482:
454:
372:
348:
342:Apress
309:Typefi
304:Sphinx
294:Paligo
246:Altova
92:MS-DOS
36:media
908:ISBN
889:ISBN
870:ISBN
851:ISBN
798:ISBN
778:ISBN
709:ISBN
681:ISBN
580:ISBN
560:ISBN
533:ISBN
480:ISBN
452:ISBN
370:ISBN
346:ISBN
204:EPUB
51:user
387:at
129:XML
117:in
94:by
968::
772::
747:,
703::
675::
622:.
598:.
554::
527::
512:^
490:^
474::
446::
415:^
400:^
340::
916:.
897:.
878:.
859:.
830:.
657:.
632:.
608:.
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.