{"title":"Interactive effectivity control: design and applications","authors":"R. Ilson","doi":"10.1145/62506.62522","DOIUrl":"https://doi.org/10.1145/62506.62522","url":null,"abstract":"WYSIWYG systems are plagued by their inability to do tasks that traditional batch formatting systems have been doing for years. Such systems have been justifiably criticized for their failings. But these lacks are not inherent in the WYSIWYG nature of a system--they are not antithetical to WYSIWYG capabilities. A WYSIWYG document processing system provides a presentation of the document that shows how the document will look when printed. This includes multiple fonts, graphics, and final composition and pagination. The user edits this final-form presentation directly and the system responds immediately, interactively updating the WYSIWYG presentation. WYSIWYG is an important capability, but not a broad, defining concept of a document processing system. A more important distinction is whether a document processing system is structure-driven or layout-driven [1]. In a structure-driven system, the document's presentation is derived from the user's structural identification of the elements of his document, combined with a database of formatting specifications for each type o f structural element. Most batch formatting systems are structure-driven, either by explicit design (e.g., in Scribe [2]), or by de facto use o f a standard macro package (e.g., -ms macros in T R O F F [3, 4], LaTeX macros for TEX [5, 6]). Some WYSIWYG systems are also structure-driven. Alternatively, in a layout-driven system, the user is responsible for specifying the detailed compositional parameters for his document. (Because o f the difficulty of doing this \"blind,\" layout-driven systems are either WYSIWYG, or require an expert user.)","PeriodicalId":357486,"journal":{"name":"Proceedings of the ACM conference on Document processing systems","volume":"9 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2000-01-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"115382369","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
{"title":"Formalizing the figural: aspects of a foundation for document manipulation","authors":"D. Levy, Daniel C. Brotsky, Kenneth Ray Olson","doi":"10.1145/62506.62531","DOIUrl":"https://doi.org/10.1145/62506.62531","url":null,"abstract":"These are exciting times in the development of computational tools for document manipulation. The wealth of developments in text and graphics editors, page description languages, window systems, and document interchange languages, along with regular discussion in the daily newspapers, Sunday supplements, and PC magazines, is a sure sign that the technology once confined to the academic and industrial research laboratories has decisively entered the public realm. But if one steps back from the details of individual systems, features, competing claims and buzz words, one is led to notice that very little of this work, if any, is based on a sound theoretical understanding of the subject matter. That this is the case can be seen by analogy. Compiler construction is today guided by an impressive body of theory: formal language and finite automata theory, programming language semantics, and so on. Textbooks are written and courses taught presenting the whys and wherefores of compiler construction; significantly, this theory exists independently of the implementation details of particular compilers. But this was not always the case. There was a pretheoretical stage in the development of compilers when they were simply implemented by the seat of the pants, without a clear understanding of the foundation that was needed, or perhaps even an awareness that a theoretical foundation was desirable or achievable. We believe that document manipulation too is in its pretheoretical stage. Where are the courses on editor construction, for example? If such courses were to be offered today, what would they teach, other than the implementation details of particular systems? More generally, where are the theories that might guide the implementation of future systems and what would such theories look like?","PeriodicalId":357486,"journal":{"name":"Proceedings of the ACM conference on Document processing systems","volume":"68 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2000-01-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"116259236","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
{"title":"The role of modularity in document authoring systems","authors":"Janet H. Walker","doi":"10.1145/62506.62526","DOIUrl":"https://doi.org/10.1145/62506.62526","url":null,"abstract":"Modularity is a fundamental concept in documents and document development as well as in programming. I hypothesized that the effectiveness of writing professionals could be increased by providing a working environment to support explicit modularity in documents and document development. This paper briefly describes an environment designed to enable testing this hypothesis and evaluates it by means of discussions with professional writers who used it for large, real-world, development projects.","PeriodicalId":357486,"journal":{"name":"Proceedings of the ACM conference on Document processing systems","volume":"51 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2000-01-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"126007813","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
{"title":"The laserROM project: a case study in document processing systems","authors":"Mike Rafeld","doi":"10.1145/62506.62510","DOIUrl":"https://doi.org/10.1145/62506.62510","url":null,"abstract":"Each year, Hewlett-Packard maintains, updates, and distributes over 8000 unique publications which are used by thousands of customers worldwide. This translates into hundreds of thousands of pages. Documentation distribution is now the province of an entire operation within HP. Because the effective use of HP products depends on the effective use of supporting publications and manuals, HP is constantly trying to improve their documentation distribution. Early in 1987, the compact disc audio (CD-Audio) market was quickly maturing. At the same time, an offshoot of this technology was just beginning, called Compact Disc-Read Only Memory (CD-ROM). The Application Support Division at Hewlett-Packard realized that this new technology for data storage might make a significant impact on the problem of documentation distribution. It could provide large amounts of documentation and support information to HP's customers in a timely, reliable, and consistent manner. This would, in turn, increase the usefulness of HP's documentation, thereby helping the customer make better support decisions and solidifying our relationship with them. Thus, the LaserROM project was created to determine how to put the thousands of publications produced by Hewlett-Packard onto CD-ROM. CD-ROM was seen as a viable delivery vehicle for a number of reasons. Mastering costs run $3,000 to $5,000 for the first few discs, and then pressing of additional discs costs approximately three to ten dollars per disc.The storage capacity of a CD-ROM is greater than","PeriodicalId":357486,"journal":{"name":"Proceedings of the ACM conference on Document processing systems","volume":"105 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2000-01-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"115297173","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
{"title":"Adding browsing semantics to the hypertext model","authors":"P. D. Stotts, R. Furuta","doi":"10.1145/62506.62516","DOIUrl":"https://doi.org/10.1145/62506.62516","url":null,"abstract":"We present a new model of hypertext that represents both the relationships that tie individual pieces of information together into the hypertext (i.e., the adjacencies) and also the browsing semantics to be associated with the hypertext (i.e., the manner in which the information is to be visited). The model is based on Petri nets, and is a generalization of existing directed graph based models. Consequently, the model permits development of browsing and authoring systems that can benefit from the analytical techniques that have been developed for Petri nets and also from the user interface designs that have been developed for hypertext systems. The Petri net base also permits more powerful specification of what is to be displayed when the hypertext is browsed. These include the ability to synchronize simultaneous traversals of separate paths through the hypertext and the ability to incorporate security considerations into the hypertext, specifying nodes that can be proven to be accessible only to certain classes of browsers. The paper includes a practical example demonstrating these specification techniques.","PeriodicalId":357486,"journal":{"name":"Proceedings of the ACM conference on Document processing systems","volume":"53 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2000-01-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"131489362","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
{"title":"A library for incremental update of bitmap images","authors":"D. Dobkin, E. Koutsofios, R. Pike","doi":"10.1145/62506.62533","DOIUrl":"https://doi.org/10.1145/62506.62533","url":null,"abstract":"To achieve the maximum performance from bitrnap displays, the screen must be used not just as an output device, but as a data structure that may cache computed images. In an interactive text or picture editor, that may mean converting the internal representation of what's being edited into a set of rectangles that tile the screen. Incremental updates of the image may then be done by rearranging some subset of the filing using bitmap operations, independently of how the tiling was derived. We have taken t_he ideas used in the screen update algorithms for the sam text editor and generalized them so they may be applied to more structured documents than the simple character stream sam edits. The ideas have been tested by building a library and a simple interactive document editor that treat a document as a hierarchical structure that may include text, pictures, and variable spacing. The core of the library is operators to make incremental changes to the display while maintaining the hierarchical data structure that describes it.","PeriodicalId":357486,"journal":{"name":"Proceedings of the ACM conference on Document processing systems","volume":"22 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2000-01-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"121532817","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
{"title":"Incremental document formatting","authors":"Pehong Chen, M. Harrison, I. Minakata","doi":"10.1145/62506.62523","DOIUrl":"https://doi.org/10.1145/62506.62523","url":null,"abstract":"The incremental techniques reported in this paper are an outgrowth of work on the VORTEX system [6]. Although, the techniques and algorithms developed extend beyond this particular system per se, it does remain our canonical example. Since our prototype implementation is for VORTEX, we will describe the overall idea of the system first. Many more details may be found in References [5,6,7]. VORTEX is an integrated document preparation environment capable of producing high quality technical documents which involve mathematics, text, and graphics. In VORTEX, both source and target representations of a document are maintained and presented. The source representation refers to a TEEX document in its original unformatted form; the target representation presents its formatted result. The user can edit both representations using a text editor and what is called a proof editor, respectively. Our editor is an Emacs-like editor written in our own VLisp (VORTEX Lisp). Changes made to one representation propagate to the other version automatically. It is easy to support source modifications that cause the target representation to change, but a major research issue is the transformation from a target version back to the source version. The system reformats a document and redisplays it on the screen incrementally. Only the part of the document or the subregion of the screen that is affected by recent changes is reprocessed. This is part of a larger environment","PeriodicalId":357486,"journal":{"name":"Proceedings of the ACM conference on Document processing systems","volume":"54 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2000-01-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"124628116","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
{"title":"Expert assistance for manipulating of SGML document type definitions","authors":"W. Polk, L. Bassham","doi":"10.1145/62506.62521","DOIUrl":"https://doi.org/10.1145/62506.62521","url":null,"abstract":"The DTD editing tool is a window and icon based tool for creation, manipulation and comprehension of SGML Document Type Definitions (DTDs). This tool allows users to manipulate SGML DTDs without any knowledge of the rather complex SGML syntax. More generally, the tool allows users to manipulate context-free grammars without any knowledge of the syntax used to describe them. The tool generates SGML DTDs, and has features specific to that application; however, the approach could also be applied to the manipulation of context-free grammars represented in other grammar description languages.","PeriodicalId":357486,"journal":{"name":"Proceedings of the ACM conference on Document processing systems","volume":"12 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2000-01-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"125316535","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}