{'fraction_non_alphanumeric': 0.01652892561983471, 'fraction_numerical': 0.0, 'mean_word_length': 5.053125, 'pattern_counts': {'":': 0, '<': 0, '<?xml version=': 0, '>': 0, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
One-Document Scientific Publishing for Print and Web / CD

When a document must be published in more than one version and must also undergo periodic revision, the use of a different stored manuscript for each version may easily result in the versions getting out of step with each other, so it is considered good practice to make arrangements to have just one stored master version. This is especially important if the different versions vary greatly in the order in which the content elements are presented, as they are likely to do when one version is for the print medium and another for the Web or for CD-ROM. With all versions sharing the same master content document, each version must have its own auxiliary non-content documents specifying the version’s unique architecture and formatting. Then any content revisions are made only to the master content document and any format revisions for a particular version are made only to the document which specifies the formatting of that particular version. This process is quite familiar to LTEX document managers who often separate formatting from content in order to maintain uniform formatting throughout a document, throughout a product line, or across revisions. In LATEX, the formatting information is usually placed in one or more auxiliary “style files”, some of which are shared among different printed versions of the material or between different documents, a kind of “inheritance.” In this paper we discuss some experiences with extending that publication model, of one master content document and auxiliary architecture and content documents, to the case of simultaneous print and Web publication. Along the way, we discuss the differences between the screen and print media and the implications for the auxiliary files, new linking opportunities in the Web version, and ways to move the content document toward compatibility with the new Extensible Markup Language, XML.