3.0 BookManager BUILD/2 2.0 and 2.1 Questions =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- 旼컴 Note about BUILD/2 1.2.1 컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴커 � � � Note: As of December 31, 1995, BUILD/2 1.2.1 is no longer supported. � � All following information pertains to BUILD/2 2.0 or 2.1 and not to � � BUILD/2 1.2.1. � � � 읕컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴켸 3.1 Features of BUILD/2 2.0 and BUILD/2 2.1 =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- 3.1.1 New features since BUILD/2 1.2. =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- The following is a list of improvements or enhancements which are included in BUILD/2 Version 2. � Improved recognition of author's intent by using word processor styles. A new filter component of BUILD/2 accurately maps the elements of your word processor source files and provides true spacings and formatting information to BUILD/2. � Performance improvements. With style-based processing, BUILD/2 spends less processor cycles trying to identify the author's intent of the word processor document. The analyzing phase of processing source documents is significantly faster. � Formula Suppoprt Forumlas are imbedded as graphics in the softcopy book only if the word processors support formulas as imbedded graphics. This capability allow forumlas and any accompanying text to display together on the same page (this support is available in BookManager READ products, Version 2 or above). � Reflow Support All books built with BUILD/2 Version 2 have reflow codes placed into the book structure. This enables BookManager READ products, Version 2 or above, to format text to fit into the defined window. The following text elements are reflowable: - Paragraphs - List items - Definition and Glossary lists - Quotes The following text elements are not reflowable: - Blank lines - Tables - Figures - Example text - Text with boxes around them - Footnotes - Right and center justified text - Pictures and graphics - Special topics (table of contents, index) � Application Launch A hypertext link called application launch allow authors to define links that start applications. Application launch is supported by BookManager READ products, Version 2 or above. � Cross-book linking Another type of link allow authors to define links that open other softcopy books. For READ products that support cross book linking (host READ products and BookManager READ products, Version 2 or above), a reader detecting a highlighted link opens another window of the target book and can navigate throughout that book. � Processing non-standard numbering schemes in headings Three types of numbering schemes for headings are supported by BUILD/2 Version 2. - Author-entered numbering - Word processor automatic numbering - BUILD/2 default numbering Author-entered numbering allows the author to include the heading number directly into the heading text. A heading rule is defined which allows BUILD/2 to filter out this author-entered numbering scheme and apply it to the heading numbering. � Use of any workstation BookManager READ product You can have BUILD/2 automatically start BookManager READ/2, READ/DOS or Read for Windows at the end of the build to inspect the softcopy book. � Definition list and Glossary list Support Authors can create definition lists and glossary lists in their word processor document using two column tables. � Expanded heading Support BUILD/2 Version 2 allow authors to identify the Abstract, Glossary, Preface, Synopsis and Appendix headings. This support allows for easier searching and grouping of vital book elements. � Auto-document recognition With BUILD/2 Version 2, you no longer have to specify the word processor source file type or rules file type. � Expanded installation methods You can install BUILD/2 Version 2 using any of the following modes: - CD install - LAN install - Service update install - CID-enabled install � Expanded graphics support TIFF support is added primarily for FrameMaker graphic support. 3.1.2 Difference between BUILD/2 2.0 and BUILD/2 2.1 =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Basically BUILD/2 2.0 and BUILD/2 2.1 are the exact same product. The only difference is that BUILD/2 2.1 contains all of the fixes for the BUILD/2 2.0 product since it became generally available. The BUILD/2 2.1 product is the new base level of the product. Any future Corrective Service (CSDs) will be based off of the BUILD/2 2.1 level. 3.2 File Input Questions =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- 1. Question: What word processor formats are supported by BUILD/2 2.0? Answer: The following formats are supported by BUILD/2 2.0: � Microsoft Word(**) for Windows, Version 2.0 and Version 6.0 � Microsoft Word for DOS, Version 5.0, Version 5.5, and Version 6.0 � WordPerfect(**) for DOS 5.0, 5.1 and 6.0 � WordPerfect for Windows 5.1, 6.0 and 6.1 � WordPerfect for OS/2 Version 5.2 � AmiPro(**) for Windows and OS/2 Version 3.0, Version 3.1 for Windows � FrameMaker** Version 4.0 (MIF Format only) 2. Question: What additional word processor formats are supported by BUILD/2 2.1? Answer: The following additional formats are supported by BUILD/2 2.1: � Microsoft Word Version 7.0 � FrameMaker Version 5.0 (MIF Format only) 3. Question: Can I use FrameMaker 4.0 or 5.0 native or MIF files as input to BUILD/2? Answer: You cannot use the native FrameMaker 4.0 or 5.0 formats. If you are using FrameMaker 4.0 or 5.0, you must save the document in a .MIF format. 4. Question: Can I use a "Master Document" format as input to BUILD/2? Answer: You can use a "Master Document" format with any of the input formats. 5. Question: Can I use my BUILD/2 1.2 Notebooks or Rules files with BUILD/2 2.0 or BUILD/2 2.1? Answer: The BUILD/2 1.2 Notebooks are not supported with BUILD/2 2.0 or BUILD/2 2.1. The BUILD/2 1.2 Rules files are supported though. When you try to use a BUILD/2 1.2 Rules file, you will be told that the rules file needs to be converted. To convert the BUILD/2 1.2 Rules file, just open the Rules file and then resave it. The Rules file will now be usable by BUILD/2 2.0 or BUILD/2 2.1. 3.3 Formatting Questions =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- 1. Question: In my Word Processing document, my tables are indented. However in the built book, the tables are left justified. How can I make my tables be indented? Answer: All tables will be left justified in the built book. Our book format does not support indented tables. However, to give the appearance that your table is indented, you should create a new column at the beginning of the table. This column will not contain any text. Also, you should not have any lines or borders turned on for this column. In the built book, the table will now appear to be indented, but actually there is a blank column there. 2. Question: In my Word Processing document I have indented regular text and text in tables with spaces. In the built book they are no longer indented. How do I indent my text? Answer: For regular text, you should either use tabs or the indent feature available. This will not be removed during the building of the book. For tables however, this is a limitation in this version of the product. Our book format does not allow text to be indented in the table, either by spaces or tabs. 3. Question: Can I have index entries on my heading styles in my WordPerfect documents? Answer: Yes you can. But, the index entries have to be placed after the style off code. If the index entry codes are placed within the style on/style off codes, then the index entry codes are not recognized. 4. Question: How do styles work in the Word Processors with BUILD/2? Answer: If you are familiar with building books on the host and using a tagging language like BookMaster, then styles are similar to different tags. For example, if you define a :h1. for your heading level 1, then when you build the book you will get 1.0 and the text you have indicated. A style works very similar. If you use the style name of "heading 1" around a piece of text, then BUILD/2 would recognize this and create a topic 1.0. BUILD/2 supports the use of paired styles or character styles. Paired styles must be used on document elements such as headings. A character style can be used on document elements such as application launch or cross-book links. Styles can just be blank and contain no formatting codes. Or they can contain formatting information such as bolding, underlining and font control. With the Word Processors, they have 'controls' that let you define a style and then apply it to certain parts of a document. The style names themselves do not appear in the physical body of the document. They are control words that appear around the text. Once you have added styles to your document, you then take the style names that you have and you create a rules file for the book you are building. You can define rules for headings (levels 1-7), examples, alerts, captions, etc. When defining your rules file, if you used a "heading 1" style in your document, then in the Heading 1 tab of the Headings section, you would add the style name of "heading 1". You would not type the quotes and you must have the space. Style names in the rules file are case sensitive and space sensitive. "Heading1" is not the same as "heading 1". Styles help in the formatting and the recognition of different elements within your document. When using a style name, you are explicitly telling the Analyzing Phase how to recognize different parts of your document. 5. Question: Do I have to use styles in my Word Processing documents? Answer: No you do not have to use styles in your Word Proccessing documents. However, it is highly recommended that you do. If you do not use styles for your headings in your documents, then you will end up with one big topic called FRONT. 6. Question: If I have any type of list in my tables, that uses indents or tabs, the indents and tabs are being removed. How can my lists be formatted so that they appear like I want them to? Answer: You need to place the bullet (or list number) into its own column. This can be a small column. Then you place the text of the bullet in another column. This will give the affect of having an indent or a tab. Based on the Word Processor used, you may want to turn off the border or not place a border between these two columns. 7. Question: I have placed a border around my example text and I want there to be blank lines between some of my text lines. How do I get the blanks to appear in the built book? Answer: The blank lines must only contain a hard return. If there are any spaces on that line, they must be removed so that only a hard return is there. Then when you rebuild the book, the blank lines will appear. 8. Question: In my Word 6.0 document, I have placed a border around "example" text. In the built book, the border is there but the right hand side of the border is way past the screen boundary. How do I get the right border to be in closer? Answer This is a current limitation in our product. 9. Question: Are MS Line Draw graphics supported by BUILD/2 2.0 or BUILD/2 2.1? Answer: No they are not. MS Line Draw graphics are considered "Absolute Positioned". The BookManager Book format and the BookManager READ products do not support absolute positioned graphic/text. If you have text and graphics that you want to be included into the built book, you must first create them as one physical entity and then include this graphic into your Word document. 10. Question: In my FrameMaker document I have a paragraph style and a character style with the name of "Example" and this style name is defined in the rules file under the example tag. When I build my book, the text that was part of the character style is now on its own line. Why is this happening? Answer: To resolve this, you must rename the character style name to something else. What is happening is that the character style text is being recognized as example text. Example text must begin on its own line. It cannot be mixed with non-example text. This is why the weird brekage is occurring. 11. Question: In my FrameMaker document I am using the automatic numbering feature to add numbers to my headings. When I build the book I get an extra period. For example, "Chapter 1." appears as "Chapter_1.." in the built book. How do I keep from getting the extra period. Answer: You will need to modify the style definition for the automatic numbering. You should remove the period from the automatic numbering section and then add a blank space from the keyboard. When you rebuild your book, you will no longer get the double periods. 3.4 Graphic Questions =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- 1. Question: I have created a graphic with a graphic product (not the word processor). When I build this graphic in the book, the background of the picture is now black. Why is this? Answer: When you created the graphic you most likely did not indicate that you wanted the background to be white. It was most likely defined to be transparent. You need to resave your graphic with a white background and then place it back in your document and rebuild. 2. Question: In my graphic I have added some text to it. After I have built the book, if I look at the graphic with READ/DOS, READ/2, READ/VM or READ/MVS, the text is bigger than what I originally created. How can I get the text to be smaller and fit with the graphic? Answer: There are two options to resolve this. First, you can resave the graphic as an image. This will prevent any text from being converted to another size or font. The Second choice is to "stroke out the text" in your graphic package. Not all graphic packages have this option or they may call it something else. Basically, if you "stroke out the text" you are creating the text as a graphic and not text. 3. Question: I am using both WordPerfect 5.x and 6.x and I have graphics in my document. I created the graphics outside of WordPerfect and have imported them into my document. After I build the document into a book, my pictures are not there. Why not? Answer: You need to verify the settings you have defined in WordPerfect for inclusion of graphics. There are three settings that you can select: a. Windows Metafiles b. WordPerfect Graphics Files c. Windows Metafiles and WordPerfect Graphics files You need to make sure that you have one of the choices with the WordPerfect Graphics format selected as your setting. BUILD/2 will only recognize WordPerfect Graphic format from WordPerfect files. 3.5 Warning Message Questions =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- 1. Question: When building a FrameMaker document with native FrameMaker graphics, I receive the message "EZW7023 The file being processed contains unsupported graphics." What does this message mean? Answer: This means that the graphic used in the FrameMaker document will not be incorporated into the built book. Native FrameMaker graphics are considered "Absolute Positioned". This means that text and graphics are absolutely positioned with respect to each other. Our book format and our READ products do not allow this type of graphic/text combination. The graphic and the text must exist as one single entity for it to be processed correctly. 2. Question: When building a book that has tables in it, I sometimes get the message EZW5124 or the message EZW5122. They both indicate that some characters have been truncated from my table cells. I have looked at the tables and do not see any text missing. What does this error message mean then? Answer: What has happened is that you have some extra hard returns (carriage controls) in your table cells. When BUILD/2 encounters these extra characters, they get removed (truncated) from the table cells. When you get these messages, this is all that is happening. If you go back into your source document and remove all of the extra returns, then you should not get these messages when building your book the next time. 3.6 Miscellaneous Questions =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- 1. Question: If I copy a notebook file (.NBK) or a rules file (.RUL) onto a diskette and then place it on another machine, BUILD/2 will not display the file when I do an "open" of a notebook or a rules file. If I then display all of the files the .NBK or the .RUL file is there. Why doesn't it appear when I do the "open"? Answer: Both the BUILD/2 .NBK and the .RUL files have extended attributes with them. When you copy the files to diskette the extended attributes are not copied. You should just get the list of files and then open the .NBK or the .RUL file and then resave it. Once you do this the extended attributes will be added back. When you do the copy of the files to a diskette, make sure that you are in OS/2. If you are in DOS, then the extended attributes will be lost. Under OS/2, they will not be lost. 3.7 Word Processor Guidelines =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- The following items are some additional hints and tips that may be helpful when creating your documents. � Turn off automatic hyphenation in the word processor. This will allow BUILD/2 to reformat the text as appropriate. � Microsoft Word 2.0 has a Fast Save option that may result in lost formatting. Turn off the Fast Save option. This is also recommended when using Microsoft Word 6.0. � When creating list items with bullets, try to use the default bullets provided with the bullet tool of the word processor being used. � When creating your figure/table captions, do not use any tabs or indents to separate the caption text from the caption number. Use the space bar to separate the caption number from the caption text. � When creating a style definition for an application launch in your word processor, do not add any codes for bolding. 3.8 BUILD/2 Graphic Guidelines =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Note: The following information is additional information about the types of graphics that can be used with BUILD/2 2.0 and BUILD/2 2.1. In general, BUILD/2 can handle any graphic that has been successfully incorporated into your word processor document. Your word processor converts the graphics into one or two data types that are stored in your word processor document. BUILD/2 is then presented with this new version of the graphic rather than the original graphic. The general rule-of-thumb is that if you can see a graphic in your word processor document while you are editing it, then BUILD/2 will be able to incorporate it into your book. There are three exceptions to this rule: 1. Encapsulated PostScript graphics (other than Adobe Illustrator format and those containing 'headers') 2. Composite graphics composed of several separate graphics 3. Composite graphics composed of a combination of graphics and true text. These exceptions are each described more fully: 1. Encapsulated PostScript graphics. Many word processors can accept graphics imported in a PostScript format. These graphics are not, however, converted to a form preferred by the word processor. They remain as PostScript data and can be presented only by a suitable PostScript printer. Usually their presence in the document is indicated on the screen by an empty box the approximate size of the graphic. Like the word processor, BUILD/2 is unable to process graphics in a PostScript format. Fortunately, there are two instances where this exception does not hold: � Adobe Illustrator. The Adobe Illustrator format is a subset of the PostScript format. Adobe Illustrator data can be processed by BUILd/2 and is printable on a PostScript printer. � PostScript graphics that contain a TIFF, WMF or PICT header. Many graphics editors that create PostScript files can include a 'snapshot' of the graphic in the TIFF, WMF or PICT format. Because these 'snapshots' are at a low resolution suitable for display on a screen, they can also be displayed by the word processor and processed by BUILD/2. 2. Composite graphics composed of a number of separate graphics. Some authors will juxtapose several graphics, creating a group that appears to be one single graphic. BUILD/2 cannot detect this condition and processes each graphic as a single entity. To prevent BUILD/2 and READ from processing these as individual graphics, authors can simply combine the individual graphics into one single graphic before incorporating it into the document. 3. Composite graphics composed of a combination of graphics and true text. Many word processors contain a graphics editor that authors can use to create graphics to include in their documents. This type of graphic is a single entity that BUILD/2 can process. A small number of editors, such as Word 6.0 and FrameMaker, provide a suite of graphics tools rather than a separate graphics editor. Authors can use these tools to create graphics objects, such as circles and lines, that they can freely intermix with the text of the document. The viewer then groups these entities, including the text, into a single 'graphic'. This situation is similar to that described in Exception 2, with the added complexity of text being mixed with graphics. BUILD/2, however, like many word processors, cannot group these individual objects into a single entity. Therefore, these graphics cannot be readily translated to another word processor format nor can they be accurately processed by BUILD/2.