| { | |
| "paper_id": "C80-1039", | |
| "header": { | |
| "generated_with": "S2ORC 1.0.0", | |
| "date_generated": "2023-01-19T13:05:35.328220Z" | |
| }, | |
| "title": "ON FROFF: A TEXT PROCESSING SYSTEM FOR ENGLISH TEXTS AND FIGURES", | |
| "authors": [ | |
| { | |
| "first": "Norihiro", | |
| "middle": [], | |
| "last": "Abe", | |
| "suffix": "", | |
| "affiliation": { | |
| "laboratory": "", | |
| "institution": "Osaka University", | |
| "location": {} | |
| }, | |
| "email": "" | |
| }, | |
| { | |
| "first": "Nobutaka", | |
| "middle": [], | |
| "last": "Uemura", | |
| "suffix": "", | |
| "affiliation": { | |
| "laboratory": "", | |
| "institution": "Osaka University", | |
| "location": {} | |
| }, | |
| "email": "" | |
| }, | |
| { | |
| "first": "Masahiro", | |
| "middle": [], | |
| "last": "Higashlde", | |
| "suffix": "", | |
| "affiliation": {}, | |
| "email": "" | |
| }, | |
| { | |
| "first": "Saburo", | |
| "middle": [], | |
| "last": "Tsujl", | |
| "suffix": "", | |
| "affiliation": {}, | |
| "email": "" | |
| } | |
| ], | |
| "year": "", | |
| "venue": null, | |
| "identifiers": {}, | |
| "abstract": "In order to meet the needs of a publication of papers in English, many systems to tun off texts have been developed. In this paper, we report a system FROFF which can make a fair copy of not only texts but also graphs and tables indispensable to our papers. Its selection of fonts, specification of character size are dinamically changeable, and the typing location can be also changed in lateral or longitudinal directions\u2022 Each character has its own width and a line length is counted by the sum of each cha~racter. By using commands or rules which are defined to facilitate the construction of format expected or some mathematical expressions, elaborate and pretty documments can be successfully obtained.", | |
| "pdf_parse": { | |
| "paper_id": "C80-1039", | |
| "_pdf_hash": "", | |
| "abstract": [ | |
| { | |
| "text": "In order to meet the needs of a publication of papers in English, many systems to tun off texts have been developed. In this paper, we report a system FROFF which can make a fair copy of not only texts but also graphs and tables indispensable to our papers. Its selection of fonts, specification of character size are dinamically changeable, and the typing location can be also changed in lateral or longitudinal directions\u2022 Each character has its own width and a line length is counted by the sum of each cha~racter. By using commands or rules which are defined to facilitate the construction of format expected or some mathematical expressions, elaborate and pretty documments can be successfully obtained.", | |
| "cite_spans": [], | |
| "ref_spans": [], | |
| "eq_spans": [], | |
| "section": "Abstract", | |
| "sec_num": null | |
| } | |
| ], | |
| "body_text": [ | |
| { | |
| "text": "With a rapid advancement of scientific exchages, a high qualitative text processing system have been expected. Under these circumstances, many systems which run off texts have been implemented. In our laboratory, a typewiriter-based word processor with a fixed widths of characters (it is called ROFF) was designed. Its output is, however, inferior in its quality to the one printed by phototypesetter or manual operations.", | |
| "cite_spans": [], | |
| "ref_spans": [], | |
| "eq_spans": [], | |
| "section": "Introduction", | |
| "sec_num": "1." | |
| }, | |
| { | |
| "text": "The Flexible Run OFF(FROFF) system is an integrated system that is designed for setting not only ordinary texts but also figures or tables indispensable to our documents, and utilizes a dot-printer as its output device. Here we must make mention of the TROFF designed for setting running text including mathematics, but as this system drives an expensive phototypesetter on the UNIX operating system, member of the almost all standard research institutes can not adopt this system configuration when he comes to think of its cost performance. This FROFF system is easy to realize in a standard computer system with the basic I/O devices including a display, dot-printer. Recently, a laboratory provided such devices incrementally increasing, it can be known for sure to be true that the circumstances under which a system with equivalent equipments to FROFF is implemented has been prepared. This program is written in mainly FLISP (a descendant of INTERLISP) and partly in Fortran, Assembler. A reason for selection of FLISP as a programming language is an easiness of programming, debugging, and extension of the system.", | |
| "cite_spans": [], | |
| "ref_spans": [], | |
| "eq_spans": [], | |
| "section": "Introduction", | |
| "sec_num": "1." | |
| }, | |
| { | |
| "text": "The FROFF system is implemented on . a mini-computer system HP2108A (64Kbytes) with an auxiliary memory (256Kbytes) which is designed to be used asa free-list region of FLISP and an image processing memory (see Fig.l ). When an image input/output is required, the auxiliary memory is partitioned, into the two parts for: list and image regions and a manipulation of image memory is performed by the simple FLISP commands.", | |
| "cite_spans": [], | |
| "ref_spans": [ | |
| { | |
| "start": 211, | |
| "end": 216, | |
| "text": "Fig.l", | |
| "ref_id": null | |
| } | |
| ], | |
| "eq_spans": [], | |
| "section": "Hardware for FROFF", | |
| "sec_num": "2." | |
| }, | |
| { | |
| "text": "The basic I/0 devices necessary for a picture processing including keyboad, dot-printer, display, TV-camera, so on are required to input pictures and process them. If no image outputs is expected, only the keyboad and dot-printer are necessary.", | |
| "cite_spans": [], | |
| "ref_spans": [], | |
| "eq_spans": [], | |
| "section": "Hardware for FROFF", | |
| "sec_num": "2." | |
| }, | |
| { | |
| "text": "1) A variety kinds of command provided by the system allows us to produce various kinds of type styles including line-drawing, picture output. An easy application of this system being realized by making use of rules installed into the system, to whom isn't satisfied: with a specification of such standard rules, he can define rules corresponding to, his own demands. Using rules, Subscripts are automatically printed in an appropriately size with no special intervention.", | |
| "cite_spans": [], | |
| "ref_spans": [], | |
| "eq_spans": [], | |
| "section": "Main Functions", | |
| "sec_num": "3." | |
| }, | |
| { | |
| "text": "2) Dynanic change in a font or a size of characters are permitted and its computation of the widths of strings of characters is done automatically.", | |
| "cite_spans": [], | |
| "ref_spans": [], | |
| "eq_spans": [], | |
| "section": "Main Functions", | |
| "sec_num": "3." | |
| }, | |
| { | |
| "text": "3) An Automatic conversion of the head of sentences into capital letters enables a text to be input from a computer terminal not equipped with small characters.", | |
| "cite_spans": [], | |
| "ref_spans": [], | |
| "eq_spans": [], | |
| "section": "Main Functions", | |
| "sec_num": "3." | |
| }, | |
| { | |
| "text": "A Dynamic motions of a text to arbitary horizontal and vertial directions is allowed, being utilized in a rule to print mathematics.", | |
| "cite_spans": [], | |
| "ref_spans": [], | |
| "eq_spans": [], | |
| "section": "4)", | |
| "sec_num": null | |
| }, | |
| { | |
| "text": "A variety of kind of lines bcan be drawn, table formats and pictures stored in the disc file being printed and a input devices Such as TV-camera, joystic make it easy to input those pictures.", | |
| "cite_spans": [], | |
| "ref_spans": [], | |
| "eq_spans": [], | |
| "section": "5)", | |
| "sec_num": null | |
| }, | |
| { | |
| "text": "We want to add explanations for each of them.", | |
| "cite_spans": [], | |
| "ref_spans": [], | |
| "eq_spans": [], | |
| "section": "5)", | |
| "sec_num": null | |
| }, | |
| { | |
| "text": "1) There are about 60 commands to fullfill forms processing requirements, by taking imaximum advantage of them we are able to specify any text formats and to get an elaborate output document. It, is, however, not easy for ,the users inexperienced to this system to master functions of these commands and to handle them effectively. In regard to this problem, an application of rules is taken into the system as one of its .primal functions. By the way, note that there is another merit brought with the rule definition.", | |
| "cite_spans": [], | |
| "ref_spans": [], | |
| "eq_spans": [], | |
| "section": "5)", | |
| "sec_num": null | |
| }, | |
| { | |
| "text": "Using FROFF, user can utilize any set of rules provided with the system by declearing names of the rules he wants to use: It is needless to say that there are many conventional styles in documents and that FROFF should provide all of facillltieS that one needs for doing them, but it is also true that there exists various kind of requirements peculiar to him. Those who are not satisfied with such system-installed functions of rules can define suitable rules to their own demands and also these rules are easy to beh taken into the system as its library rules. Here note that a primal reason for using rules in specification of forms is that the system should be easy to be extended to have more facilities, since requirements In format will vary ocassionally and it is necessary that the modification be easy to implement at any time. The method taken 2) As each character is given its own width, a well-balanced arrangement is obtained as its consequence. For example, sample pattern for character I and W are shown in Fig.2 , whose width are 13x12, 29x32 respectively, where the size is shown in a \"dot\". As has already been understood, this paper is printed by FROFF, a Various kind of fonts including roman, B01tl etc: are dynamically available and their typeset in italic is also done easily. At present fourteen kinds of fonts are prepared,and 60 fonts will be in use near future.", | |
| "cite_spans": [], | |
| "ref_spans": [ | |
| { | |
| "start": 1023, | |
| "end": 1028, | |
| "text": "Fig.2", | |
| "ref_id": null | |
| } | |
| ], | |
| "eq_spans": [], | |
| "section": "5)", | |
| "sec_num": null | |
| }, | |
| { | |
| "text": "Of cource~ commands for size specification of characters enable a variety sizes of output to be accomplised. To my regret, characters enlarged too much are not necessarily good with respect to its grace, but there is no inconvenience to our usual purposes (see Fig.3 for example).", | |
| "cite_spans": [], | |
| "ref_spans": [ | |
| { | |
| "start": 261, | |
| "end": 266, | |
| "text": "Fig.3", | |
| "ref_id": "FIGREF1" | |
| } | |
| ], | |
| "eq_spans": [], | |
| "section": "Flg.2. Sample patterns I and W.", | |
| "sec_num": null | |
| }, | |
| { | |
| "text": "3) An input text can be processed at a terminal not equipped with small characters such as the conventional TTY and graphic displays. The decision whether a heading Of words must be printed in capital or not is automatically decided by the system using common-sense rules that a head character of the sentence, which usually follows to \".\", should be printed in capital and that any words following to \"i.e.\", \"e.g.\" etc. be in small. As a result of these settlement being assumed, there is a disadvantage in the case where one wants to type alI characters in capital like \"FLISP SYSTEM\". ", | |
| "cite_spans": [], | |
| "ref_spans": [], | |
| "eq_spans": [], | |
| "section": "Flg.2. Sample patterns I and W.", | |
| "sec_num": null | |
| }, | |
| { | |
| "text": "To cover up such a weak point which are occasionally encounterd when there are some mixtures of big and small characteres in a string, sevaral rules to change fonts or sizes of characters ot to concatenate them are prepared. (Another way o! handling this problem will be stated in 9 ).", | |
| "cite_spans": [], | |
| "ref_spans": [], | |
| "eq_spans": [], | |
| "section": "1-i-~", | |
| "sec_num": null | |
| }, | |
| { | |
| "text": "We are able to avoid writing a sophisticated procedure such as one needed to produce a mathematical expression enclosed by a box (shown in Fig.4 ) because some commands permits an output location to be shifted relatively to any directions in respect to the previous output position.", | |
| "cite_spans": [], | |
| "ref_spans": [ | |
| { | |
| "start": 139, | |
| "end": 144, | |
| "text": "Fig.4", | |
| "ref_id": null | |
| } | |
| ], | |
| "eq_spans": [], | |
| "section": "4)", | |
| "sec_num": null | |
| }, | |
| { | |
| "text": "5) It can be thought of as true thing that there is no paper without any figures or tables. Especially for a laboratory investigating picture processings and their related fields, commands for a picture output or rules for a tabulation make it easy to insert computed results into the document. In this case, it is, of cause, possible to add simple operations such as, inversion, partial extraction of pictures to them. Restricted to holizontal or vertical directions, various types of lines can be readily drawn (see Fig.6 ).", | |
| "cite_spans": [], | |
| "ref_spans": [ | |
| { | |
| "start": 518, | |
| "end": 523, | |
| "text": "Fig.6", | |
| "ref_id": "FIGREF4" | |
| } | |
| ], | |
| "eq_spans": [], | |
| "section": "4)", | |
| "sec_num": null | |
| }, | |
| { | |
| "text": "Previous to the detailed explanation of rules and commands, an overall structure of FROFF must be given to guide an easy comprehension of it.", | |
| "cite_spans": [], | |
| "ref_spans": [], | |
| "eq_spans": [], | |
| "section": "A Coustruction of FROFF.", | |
| "sec_num": "4." | |
| }, | |
| { | |
| "text": "At first, input text is given using the text editor. As shown in Fig.7 , when texts are fed into the system, interpretation of rules is conducted in the following way. It scanning the sequence of texts for symbols defined as user specified or system library rules, they are replaced with their definitions when found. Upon completion of this stage, evaluation of commands is executed, which is done in the way where a LISP function corresponding to each command is invoked. A result obtained from this step, as described in a flowchart in Fig.7 , is converted to the binary data in order to drive the versatec dot-printer by several programs written in Fortran, Assembler.", | |
| "cite_spans": [], | |
| "ref_spans": [ | |
| { | |
| "start": 65, | |
| "end": 70, | |
| "text": "Fig.7", | |
| "ref_id": "FIGREF5" | |
| }, | |
| { | |
| "start": 539, | |
| "end": 544, | |
| "text": "Fig.7", | |
| "ref_id": "FIGREF5" | |
| } | |
| ], | |
| "eq_spans": [], | |
| "section": "A Coustruction of FROFF.", | |
| "sec_num": "4." | |
| }, | |
| { | |
| "text": "A source text of FROFF comprises text lines and command lines, which begines with a period, and blanks are regared as delimiters. A string of characters punctuated with a delimiter is called a Fig. 4 . A mathematical expression enclosed lay a box. \"unit\", an allocation of texts including justifications and a page segmentation is accompleshed in terms of this \"unit\". Any combinations of variables and values with units such as \"MM\", \"CM\" involving the arithmetical rules are permitted as arguments for these commands (if a unit is abbreviated, a unit is regarded as a \"dot\", :where 1 cm equals to 78.8177 dots). These commands are partitioned into two classes, those for formats and for controllng forms.", | |
| "cite_spans": [], | |
| "ref_spans": [ | |
| { | |
| "start": 193, | |
| "end": 199, | |
| "text": "Fig. 4", | |
| "ref_id": null | |
| } | |
| ], | |
| "eq_spans": [], | |
| "section": "Commands and their examples.", | |
| "sec_num": "5." | |
| }, | |
| { | |
| "text": "The former is used to specify the type form like an indentation, spacing, font change, centering etc. and the latter serves for dynamic control of such type styles. The general command form is the following command-name arg-1 arg-2 ---arg-n where arguments can be default according to the specification of the command. Some examples of the format commands are listed in Table 1 .", | |
| "cite_spans": [], | |
| "ref_spans": [ | |
| { | |
| "start": 370, | |
| "end": 377, | |
| "text": "Table 1", | |
| "ref_id": null | |
| } | |
| ], | |
| "eq_spans": [], | |
| "section": "Commands and their examples.", | |
| "sec_num": "5." | |
| }, | |
| { | |
| "text": "As mentioned earlier, there is no need for being troubled with detailed restrictions on commands if a people not skilled with them takes maximum advantages of library rules. To apply those rules, the following declaration is required.", | |
| "cite_spans": [], | |
| "ref_spans": [], | |
| "eq_spans": [], | |
| "section": "utilization and Definition of rules", | |
| "sec_num": null | |
| }, | |
| { | |
| "text": ".. rule rule-1 rule-2 .... rule-n (.) where rule-i must be the system rule. To whom wants to define rules for his own purpose, the command \"..\" allows him to formulate them in the following way.", | |
| "cite_spans": [], | |
| "ref_spans": [], | |
| "eq_spans": [], | |
| "section": "utilization and Definition of rules", | |
| "sec_num": null | |
| }, | |
| { | |
| "text": ". ", | |
| "cite_spans": [], | |
| "ref_spans": [], | |
| "eq_spans": [], | |
| "section": "utilization and Definition of rules", | |
| "sec_num": null | |
| }, | |
| { | |
| "text": "To fulfill various requirements for format, the needs for chaging a width of page or variety of control are expected. For doing so, in this system the application of rules ~are provided to users. Yet, proper side-effects by each rule must be resulted from the rule evaluation and the old status of parameters must be recovered as soon as its execution terminates. For example, assume now texts are printed in Roman, and some strings are expected to be in BOLD, where of course this is done by a rule R, and then the specification of font must be tailored to suit a condition that a font specification is free from the old one. For this purpose, the following rules are required.", | |
| "cite_spans": [], | |
| "ref_spans": [], | |
| "eq_spans": [], | |
| "section": "System parameters and control commands", | |
| "sec_num": null | |
| }, | |
| { | |
| "text": ". where gA is one of system variables, the value of which is altered by subjecting to an effect of.\".A'. To supply flexibilities for controlling formats, almost all parameters used in commands are opened to users. Those variables and their relation to page style is demonstrated in Fig.8 . Several samples of control commands and their meaning are listed in Table 2 . where an object of output is a fnum-th picture in a picture file, whose name is name, stored in a cartridge cr and the real output is enlarged by rex, my after an extraction from the original picture. Parameters such as sx, ey indicate this extraction domain. It's needless to say that they are printed in a top location in the next page when sufficient lines can't be found.", | |
| "cite_spans": [], | |
| "ref_spans": [ | |
| { | |
| "start": 282, | |
| "end": 287, | |
| "text": "Fig.8", | |
| "ref_id": "FIGREF6" | |
| }, | |
| { | |
| "start": 358, | |
| "end": 365, | |
| "text": "Table 2", | |
| "ref_id": null | |
| } | |
| ], | |
| "eq_spans": [], | |
| "section": "System parameters and control commands", | |
| "sec_num": null | |
| }, | |
| { | |
| "text": "To be out of Order, we show briefly a mechanism and meaning of this command. When this command is encountered in the course of scanning of texts, program protects its current system parameters described in Fig.8 and by checking arguments of this command it computes a necessary longitudinal length, allocating the explanatory texts by assuming enough lines are remained in the current page. In effect, even if a true end of page was found, this is not suspended. In case all texts are successfully settled, the stored parameters are neglected and the subsequent texts are processed in an ordinary way. Otherwise, on completion of execution of \".pie\" command, its result including the retained parameters are removed from the consequence so far acheived, and preserved for a next page. ~Space not occupied in so doing are used to allocate the rest of texts, and when an end of page is detected, system parameters at that time are stored in a reserved location. On a new page encountered, the above mentioned: result is reverted, as if \".pie\" command was written immediately after a page changing command, after adding a slight modification to its vertical coordinate values. Then, the stored system parameters are reset to as their old values and the system proceeds with successive procedures.", | |
| "cite_spans": [], | |
| "ref_spans": [ | |
| { | |
| "start": 206, | |
| "end": 211, | |
| "text": "Fig.8", | |
| "ref_id": "FIGREF6" | |
| } | |
| ], | |
| "eq_spans": [], | |
| "section": "Figure outputs", | |
| "sec_num": "6." | |
| }, | |
| { | |
| "text": "Any types of lines expected should be drawn in relation to the current output location or to the pre-specified coordinates for ready achievment of tabulations and others. For this purpose next commands are prepared.", | |
| "cite_spans": [], | |
| "ref_spans": [], | |
| "eq_spans": [], | |
| "section": "Line drawing and Tabulations", | |
| "sec_num": "7." | |
| }, | |
| { | |
| "text": ".line? sx sy ex ey size nt n2 ---ni .line sx sy ex ey size nl n2 ---nt Their relations between arguments and allocations are given in Fig.9 , where an origine of \".line?\" refers to the previous vertical location and that of \".line\" to the location given explicitly by user (regarding their horizontal one, both refer to %LX shown in Fig.8) . Especially, the former command brings easy achievement of tabulations or mathematics, like a horizontal line in a fraction or a root symbol. For tabulations, all specifications needed for achieving various types of forms desired are not necessarily implemented In the current version because quite many styles on tabulation being required, it is impossible to supply enough rules to fulfill them. But from experiences, it seems apparant that tables shown in Table 1 ,2 are most familiar to us in comparison to any other types, and it is enough for practical uses if rules corresponding to them are prepared. Still yet, this leacis to easy achievement of tables and easy learning of such rules.", | |
| "cite_spans": [], | |
| "ref_spans": [ | |
| { | |
| "start": 134, | |
| "end": 139, | |
| "text": "Fig.9", | |
| "ref_id": "FIGREF7" | |
| }, | |
| { | |
| "start": 333, | |
| "end": 339, | |
| "text": "Fig.8)", | |
| "ref_id": "FIGREF6" | |
| }, | |
| { | |
| "start": 800, | |
| "end": 807, | |
| "text": "Table 1", | |
| "ref_id": null | |
| } | |
| ], | |
| "eq_spans": [], | |
| "section": "Line drawing and Tabulations", | |
| "sec_num": "7." | |
| }, | |
| { | |
| "text": "Let explain a first rule to make a list with equal line widths in the following. ,table X Y ZAB M N sets a window on a current page as shown in Fig.10 , and a rule, *tb text, causes its contents to be enterd in a specific order. The rule, *tbn F, completes the current row, switching from a current row to the next one with a vertical line-drawing. When a completion of table required, rule *endtb cancells its current settlement of window and the old status for formattings is reverted.", | |
| "cite_spans": [], | |
| "ref_spans": [ | |
| { | |
| "start": 144, | |
| "end": 150, | |
| "text": "Fig.10", | |
| "ref_id": "FIGREF0" | |
| } | |
| ], | |
| "eq_spans": [], | |
| "section": "Line drawing and Tabulations", | |
| "sec_num": "7." | |
| }, | |
| { | |
| "text": "On the other hand, it's difficult to give a convenient method for tables with variable line widths as shown in Table 2 , only a means are arranged with which lines are drawn to the entries ofi tabl\u00a2 after allocation of them in a similar way mentioned above. However to my regret, results created by manual operations seems superior to that generated by rule with respect to its easiness of a construction. As already stated in [3] , this is known as difficult to set in type than any other kind of texts. In TROFF, a language was designed to translate a convenient expression for mathematics into a form readily evaluated with TROFF. This methodology quite suits to a easy extension of system facility and excels in the point that any person not skilled with details of the system are' able to use it. But its easiness in extension depends most on existence of a good compiler-compiler which permits the system to be added new facilities. On the contrary, for our system not assumed such tools, another way of simplifying the specification of mathematics is requisite.", | |
| "cite_spans": [ | |
| { | |
| "start": 427, | |
| "end": 430, | |
| "text": "[3]", | |
| "ref_id": "BIBREF2" | |
| } | |
| ], | |
| "ref_spans": [ | |
| { | |
| "start": 111, | |
| "end": 118, | |
| "text": "Table 2", | |
| "ref_id": null | |
| } | |
| ], | |
| "eq_spans": [], | |
| "section": "Line drawing and Tabulations", | |
| "sec_num": "7." | |
| }, | |
| { | |
| "text": "As a typical user of this system can be considered to have common sense, on :technology, mathematical expressions must be described in a Polish notation as descrived below. Of course, standard 'things in mathematics, like subscripts, superscripts and their locations, are automatically adjusted irk an appropriate, size. But in this system, there is a weakness in that special commands or rules must be written to concatenate subexpressions as in *fra a b+ *omega, which generates a b+t0", | |
| "cite_spans": [], | |
| "ref_spans": [], | |
| "eq_spans": [], | |
| "section": "Line drawing and Tabulations", | |
| "sec_num": "7." | |
| }, | |
| { | |
| "text": "The reason why such inconvenience occurs should be elucidated. Unlike the TROFF, this system treats mathematics in a similar manner to ordinal texts, which means that any expressions delimitted with a blank is regarded as a \"unit\" and this fact causes the expressions to be broken up. In this regard, TROFF is superior to our system. But except for this defect, almost all of the facilities that one needs for doing mathematics are defined using, rules. As has been discussed, new facilities needed for mathematics are easily added to the system by using rules. Now let us show some examples in the following. First of all, subexpressions are defined and by using defined symbols main expressions are printed.", | |
| "cite_spans": [], | |
| "ref_spans": [], | |
| "eq_spans": [], | |
| "section": "Line drawing and Tabulations", | |
| "sec_num": "7." | |
| }, | |
| { | |
| "text": ".D ,xl ,2 *delta *() t-n : 6(t-n)", | |
| "cite_spans": [], | |
| "ref_spans": [], | |
| "eq_spans": [], | |
| "section": "Line drawing and Tabulations", | |
| "sec_num": "7." | |
| }, | |
| { | |
| "text": ". where, symbol *k concatenates k\"units\".", | |
| "cite_spans": [], | |
| "ref_spans": [], | |
| "eq_spans": [], | |
| "section": "Line drawing and Tabulations", | |
| "sec_num": "7." | |
| }, | |
| { | |
| "text": "At last, we show a rule bringing a square root expression. The relation of ~arameters to the style is shown in Fig. 11 ", | |
| "cite_spans": [], | |
| "ref_spans": [ | |
| { | |
| "start": 111, | |
| "end": 118, | |
| "text": "Fig. 11", | |
| "ref_id": "FIGREF0" | |
| } | |
| ], | |
| "eq_spans": [], | |
| "section": "Line drawing and Tabulations", | |
| "sec_num": "7." | |
| }, | |
| { | |
| "text": "Problems such as, how well this system satisfies a goal of being easy to use, how easy it was to build or extend beyond:its original limitations should be discussed. As to ease of use, from,our experinces, FROFF is found to be useful tool for making fair copy of documents except for a few deficiencies. They are inconvenient in doing mathematics,and has a weakpoints in its speed and a lack of small characters, which have been already mentioned in this paper, Though there is obviously a great deal more to be done in order to improve these deficiencies, any other way of supplementing the first problem is not taken at present.", | |
| "cite_spans": [], | |
| "ref_spans": [], | |
| "eq_spans": [], | |
| "section": "9.Experiences", | |
| "sec_num": null | |
| }, | |
| { | |
| "text": "For the rest of those problems, the following method is adopted. That is, we decided to use FROFF as a device to accomplish a complete document, and use the above mentioned ROFF with fixed character sizes as that for a draft or a debugging. As shown in this figure, the text which was typed in accordance with the prospectus of ROFF are translated into that for FROFF. In this case, commands or rules for mathematics and figures are not affected with this translation; only a conversion from mixtures of big or small characters into a description corresponding to the restrictions of FROFF is conducted.", | |
| "cite_spans": [], | |
| "ref_spans": [], | |
| "eq_spans": [], | |
| "section": "~267--", | |
| "sec_num": null | |
| }, | |
| { | |
| "text": "As this ROFF: and its translator are written in Assembler, steps needed for obtaining a complete result are decreased to a large extent. This paper is, of course, typeset by the authors using first the ROFF, secondly the translator and at last using FROFF.", | |
| "cite_spans": [], | |
| "ref_spans": [], | |
| "eq_spans": [], | |
| "section": "~267--", | |
| "sec_num": null | |
| }, | |
| { | |
| "text": ". ", | |
| "cite_spans": [], | |
| "ref_spans": [], | |
| "eq_spans": [], | |
| "section": "TYPE SYMBOL DEFINITION", | |
| "sec_num": null | |
| } | |
| ], | |
| "back_matter": [ | |
| { | |
| "text": "The authors would like to thank Fumihide Itoh, Itsuya Soga for their contribution in preparation of this paper.", | |
| "cite_spans": [], | |
| "ref_spans": [], | |
| "eq_spans": [], | |
| "section": "Acknowledgements", | |
| "sec_num": null | |
| }, | |
| { | |
| "text": "If pred is true, textl is regarded as a text, else text2. Table 2 . Examples of control commands.", | |
| "cite_spans": [], | |
| "ref_spans": [ | |
| { | |
| "start": 58, | |
| "end": 65, | |
| "text": "Table 2", | |
| "ref_id": null | |
| } | |
| ], | |
| "eq_spans": [], | |
| "section": "annex", | |
| "sec_num": null | |
| } | |
| ], | |
| "bib_entries": { | |
| "BIBREF0": { | |
| "ref_id": "b0", | |
| "title": "The Soft Display Word Processor", | |
| "authors": [ | |
| { | |
| "first": "Jack", | |
| "middle": [ | |
| "E" | |
| ], | |
| "last": "Shermer", | |
| "suffix": "" | |
| }, | |
| { | |
| "first": "Lortnda", | |
| "middle": [ | |
| "L" | |
| ], | |
| "last": "Cherry", | |
| "suffix": "" | |
| } | |
| ], | |
| "year": 1978, | |
| "venue": "", | |
| "volume": "ll", | |
| "issue": "", | |
| "pages": "", | |
| "other_ids": {}, | |
| "num": null, | |
| "urls": [], | |
| "raw_text": "Jack E. Shermer and Lortnda L. Cherry : The Soft Display Word Processor, Computer, Vol.ll, No.12 p.39 (DEC. 1978)", | |
| "links": null | |
| }, | |
| "BIBREF1": { | |
| "ref_id": "b1", | |
| "title": "Design of a Raster Display Processor for Office Applications : IEEE Computers", | |
| "authors": [ | |
| { | |
| "first": "H", | |
| "middle": [], | |
| "last": "David", | |
| "suffix": "" | |
| }, | |
| { | |
| "first": "Warren", | |
| "middle": [ | |
| "M" | |
| ], | |
| "last": "Hartke", | |
| "suffix": "" | |
| }, | |
| { | |
| "first": "Jack", | |
| "middle": [ | |
| "E" | |
| ], | |
| "last": "Sterling", | |
| "suffix": "" | |
| }, | |
| { | |
| "first": "", | |
| "middle": [], | |
| "last": "Shermer", | |
| "suffix": "" | |
| } | |
| ], | |
| "year": 1978, | |
| "venue": "", | |
| "volume": "27", | |
| "issue": "", | |
| "pages": "337--348", | |
| "other_ids": {}, | |
| "num": null, | |
| "urls": [], | |
| "raw_text": "David H. Hartke, Warren M. Sterling, and Jack E. Shermer : Design of a Raster Display Processor for Office Applications : IEEE Computers, C-27, No.4, pp.337-348 (APR. 1978)", | |
| "links": null | |
| }, | |
| "BIBREF2": { | |
| "ref_id": "b2", | |
| "title": "A System for Typesetting Mathematics, CACM", | |
| "authors": [ | |
| { | |
| "first": "B", | |
| "middle": [ | |
| "W" | |
| ], | |
| "last": "Kernighan", | |
| "suffix": "" | |
| }, | |
| { | |
| "first": "L", | |
| "middle": [ | |
| "L" | |
| ], | |
| "last": "Cherry", | |
| "suffix": "" | |
| } | |
| ], | |
| "year": 1975, | |
| "venue": "", | |
| "volume": "18", | |
| "issue": "", | |
| "pages": "", | |
| "other_ids": {}, | |
| "num": null, | |
| "urls": [], | |
| "raw_text": "B. W. Kernighan, L. L. Cherry, A System for Typesetting Mathematics, CACM, Vol.18, No.3, p.151 (1975)", | |
| "links": null | |
| }, | |
| "BIBREF4": { | |
| "ref_id": "b4", | |
| "title": "Computer Typesetting of Technical Journals on UNIX, Proc. of NCC", | |
| "authors": [ | |
| { | |
| "first": "M", | |
| "middle": [ | |
| "E" | |
| ], | |
| "last": "Lesk", | |
| "suffix": "" | |
| }, | |
| { | |
| "first": "B", | |
| "middle": [ | |
| "W" | |
| ], | |
| "last": "Kernighan", | |
| "suffix": "" | |
| } | |
| ], | |
| "year": 1977, | |
| "venue": "", | |
| "volume": "", | |
| "issue": "", | |
| "pages": "879--888", | |
| "other_ids": {}, | |
| "num": null, | |
| "urls": [], | |
| "raw_text": "M. E, Lesk and B. W. Kernighan : Computer Typesetting of Technical Journals on UNIX, Proc. of NCC, pp.879-888 (1977)", | |
| "links": null | |
| } | |
| }, | |
| "ref_entries": { | |
| "FIGREF0": { | |
| "uris": null, | |
| "text": "Configuration of FROFF system. on this system simplifies this improvement of its functions.", | |
| "num": null, | |
| "type_str": "figure" | |
| }, | |
| "FIGREF1": { | |
| "uris": null, | |
| "text": "An example of available character sizes.", | |
| "num": null, | |
| "type_str": "figure" | |
| }, | |
| "FIGREF2": { | |
| "uris": null, | |
| "text": "a) and (b) shows examples of picture outputs.", | |
| "num": null, | |
| "type_str": "figure" | |
| }, | |
| "FIGREF3": { | |
| "uris": null, | |
| "text": "(a)/5-(b). Picutre output from a disc file.", | |
| "num": null, | |
| "type_str": "figure" | |
| }, | |
| "FIGREF4": { | |
| "uris": null, | |
| "text": "An output of lines.", | |
| "num": null, | |
| "type_str": "figure" | |
| }, | |
| "FIGREF5": { | |
| "uris": null, | |
| "text": "Text processing system should provide feasibilities to insert several sizes of figures. Allocations of figures -:J~. ---\"'l-i I ~,'~'~'-~-I . ~ ;IDISPLAY l [ UUFtI[E' ) I OUTPUT A I DOCUMMENT I A system flowchart of FROFF.", | |
| "num": null, | |
| "type_str": "figure" | |
| }, | |
| "FIGREF6": { | |
| "uris": null, | |
| "text": "A: page format and its relation to parameters: are known as difficult because the program neccessitates a modification to texts allocation if there doesn't remain enough space for displaying the picture in a current page, and this procedure must be suspended and the remaining space must be filled with the subsequent texts. And this interrupted commands should be resumed when a new page is encountered (This is not restricted to figures, the same is true for tables or mathematics). Figure outputs are conducted with the following commands. .pic name cr fnum Xo Yo mx my sx sy ex ey type an explanation statement ,for this figure", | |
| "num": null, | |
| "type_str": "figure" | |
| }, | |
| "FIGREF7": { | |
| "uris": null, | |
| "text": "Parameters of a line command.", | |
| "num": null, | |
| "type_str": "figure" | |
| }, | |
| "FIGREF8": { | |
| "uris": null, | |
| "text": ". 10. A rule for a typical tabulation.", | |
| "num": null, | |
| "type_str": "figure" | |
| }, | |
| "FIGREF9": { | |
| "uris": null, | |
| "text": "D *x2 *sp e *2 -jn *omega : e -j\"= .D ,x3 *fra *sp *lambda n .2 n ! : -~-.D *x4 *sigma3 n=0 *inf *x3 : ~ n! .D *sub *2 *sp e *2 -,lambda *x4 : e-~/~ n=0 *5 f *() t = *sub *xl *5 F *() *omega = *sub *x2 oo f(t)=e-x'~l~ 6(t-n). , F(=)=e \"~ . e -in= n:0 n=0", | |
| "num": null, | |
| "type_str": "figure" | |
| }, | |
| "TABREF0": { | |
| "num": null, | |
| "content": "<table><tr><td>.</td><td>.</td><td>.</td><td>.</td><td>.</td><td>.</td><td>.</td><td>.</td><td>.</td><td>.</td><td>.</td><td>.</td><td>.</td><td>.</td><td>.</td><td>.</td><td>.</td><td>.</td><td>.</td><td>.</td><td>.</td><td>.</td><td>.</td><td>.</td><td>.</td><td>.</td><td>.</td><td>.</td><td>.</td><td>.</td><td>.</td><td>.</td><td>.</td><td>.</td><td>.</td><td>.</td></tr><tr><td colspan=\"36\">IIIIIl[llll[lllllllllllllllllllllllltllillillllllllllllllPllllllr</td></tr></table>", | |
| "html": null, | |
| "text": "n i mum .............................................................", | |
| "type_str": "table" | |
| } | |
| } | |
| } | |
| } |