DynaText 4.1 



Release Notes 



30 September 1998 



Inso Corporation 



299 Promenade Street 



Providence, Rhode Island 02908-5720 







Copyright (c) 1998 Inso Corporation. All Rights Reserved. DynaText, InStEd, Inso, and the Inso logo are either trademarks or registered

trademarks of Inso Corporation in the United States and/or other countries. All other company and product names are trademarks or registered

trademarks of their respective owners. 







Table of Contents 



1.0 About These Release Notes 



2.0 This DynaText Release 



2.1 Platforms 



2.2 System Requirements 



2.3 Components Included in This Release 



2.4 Documentation Provided in This Release 



3.0 Licensing for DynaText 4.1 



4.0 New Features and Enhancements in DynaText 4.1 



5.0 Documentation Update: Variable Assignment in Styles (introduced in DynaText 3.1) 



6.0 Problems Resolved in Release 4.1 



7.0 System Limitations and Known Problems 



7.1 System Limitations 



7.2 Known Problems 



1.0 About These Release Notes 



This document contains information about the release of DynaText 4.1. It lists new features and enhancements, provides last-minute information

about the product, and lists known problems and system limitations. For further descriptions of new features, please refer to the Features of

DynaText 4.1 book in the Sample DynaText Books collection. 



================================================ 



2.0 This DynaText Release 



With a few limitations, this release of DynaText 4.1 software is compatible with DynaText 4.0, DynaText 3.x and DynaText 2.3 (replicating most 2.3

features and supporting DynaText 2.3 books). 



--------------------------------------------------------------------- 



2.1 Platforms 



DynaText 4.1 software is available on the following platforms: 



     Sun Solaris 2.5.1/2.6 

     Windows 95/98 

     Windows NT 4.0 

     Windows 3.1 running Win32s (Browser only) 

     SGI IRIX 6.2 

     HP-UX 10.2 



--------------------------------------------------------------------- 



2.2 System Requirements 



2.2.1 RAM/Memory 



(all numbers assume virtual memory in use)

(Rec. = Recommended)

(Min. = Minimum)



                Publishing Environment          Browsing Environment



Platform        language: English               language: English         



UNIX            32 MB                           32 MB           



Windows         32 MB Rec.                      16 MB Rec.      

                16 MB Min.                      12 MB Min.      



2.2.2 Disk Space 



                Publishing Environment          Browsing Environment 



Platform              language: English         language: English         

 

Sun Solaris 2.5.1/2.6     47 MB                         25 MB           

SGI IRIX 6.2             112 MB                         25 MB

HP-UX 10.2               109 MB                         91 MB







                Publishing Environment          Browsing Environment



Windows         10 MB Minimum                   9  MB Minimum   

                27 MB Full                      17 MB Full      

                



2.2.3 Win32s Versions Required for Windows 3.1 Browsing 



The DynaText 4.1 Browser for Windows 3.1 requires Win32s version 1.30 for English and other European languages. The DynaText 4.1 Browser

for Windows 3.1 requires Win32s version 1.30J for the Japanese language. 



--------------------------------------------------------------------- 



2.3 Components Included in This Release 



This release may contain the following DynaText assemblies: 



     DynaText Publisher/SGML Edition 

          Publishing tools are: 

             1.mkbook 

             2.insted 

             3.mkcolidx 

             4.rvwbook (formerly sgmlrvw) 

             5.makept 

             6.buildmap 

             7.updannot 

             8.imconv 

     DynaText Browser Standalone 

     DynaText SIT (System Integrator's Toolkit) 



--------------------------------------------------------------------- 



2.4 Documentation Provided in This Release 



This release contains the following new English-language documents: 



     This document (relnotes.htm/relnotes.txt) 

     Installation Notes (install.txt) (platform specific) 



     These describe the installation package for Windows or for UNIX and how to install DynaText. 



This release includes the following documentation as DynaText books: 



     ImageMap Converter User Guide 

     HotSpot Sample Book 

     DynaText Reader Guide (separate versions for Windows and UNIX) 

     Introduction to DynaText 

     Configuration and Administration Guide (separate versions for Windows and UNIX) 

     Publishing: Document Preparation 

     Publishing: Setup, Production, and Distribution 

     InStEd User Guide 

     Updated Special Character Entities 

     Collection of sample documents 

        1.Features of DynaText 4.1 

        2.Providence Guide 

        3.sample2 

        4.Shuttle Press Kit 



================================================ 



3.0 Licensing for DynaText 4.1 



Unlike previous versions of DynaText, licensing is not software-controlled. There is no time-out feature on evaluation copies. Users are obligated to

comply with the terms of their written license agreement. 



================================================ 



4.0 New Features and Enhancements in DynaText 4.1 



The following is a list of the new features in DynaText 4.1: 



     Location feedback while scrolling 

     Improved access to advanced-query preferences 

     New buttons in the button bar 

     Expose Inline Manager 

     Japanese dictionary-based word-breaking 

     Improved locked table headers 

     Software-based licensing removed 

     InStEd runs in its own locale on Windows 

     Printing to a file on all platforms 

     Support for relative paths (Windows only) 

     Location irrelevant RAM books 

     CGM Plug-in option (availability is to be determined) 



4.1 Location feedback while scrolling 



Dragging the scrollbar now provides the user with location feedback in the form of a pop-up "tool-tip" that displays the title of the current section

from the TOC. This helps users scroll directly to the desired section of a book. 



4.2 Improved access to advanced-query preferences 



An Expand Search check-box, adjacent to the Search sliver (in both collection and book windows),  has been added which makes it easy to turn the

query expansion off or use the existing preferences. 



1) If the Expand Search check box is turned off, no Query Enhancement searching will be performed (it doesn't matter whether Query Enhancement

is or is not selected in the Advanced Search dialog window). 



2) If the Expand Search check box is turned on and no Query Enhancement options are selected in the Advanced Search dialog window, then the

search will use all of the Query Enhancement options. 



3) If the Expand Search check box is turned on and one or more Query Enhancement options are selected in the Advanced Search dialog window,

then the search will only use  the selected Query Enhancement options. 



If the Query Enhancement components are installed on Windows, the Query Enhancement preferences will be turned on when DynaText is first

executed. The user can change the preferences selectively. 



If the Query Enhancement components are installed on UNIX, the Query Enhancement preferences may or may not be turned on at first, depending

on the user's .Xebt file. For example, if DynaText is installed with the Query Enhancement options selected, the Query Enhancement preferences will

be turned on. If the user changes the Query Enhancement preferences, the .Xebt file is updated with these changes. If DynaText is reinstalled with

Query Enhancement options selected, the Query Enhancement preferences will be selected from the settings in the .Xebt file. 



If all the preferences are turned off by the user, the check-box is turned off. However, if the user turns on the check-box, then the query will be done

with complete expansion. This will be in effect as long as the check-box is on and the view is open. 



There is a new button called "Advanced Search Preferences" which displays the Preferences dialog. 



4.3 New buttons in the Button Bar 



The following buttons have been added to the button bar: 



1. An "Enlarge" button to enlarge the font sizes of the book/toc panes. (This is a short-cut to the View|Zoom|Enlarge menu item.) 



2. A "Reduce" button to reduce the font sizes of the book/toc panes. (This is a short-cut to the View|Zoom|Reduce menu item.) 



4.4 Expose Inline Manager 



The Inline Manager enables developers to more readily integrate non-SGML/XML data formats inline. For example, the Inline Manager is used by

Inso to display CGMs inline using the DynaText CGM Plug-in. 



4.5 Japanese dictionary-based word-breaking 



Word-breaking, line-breaking, word selection (highlighting, etc.), and queries use dictionary-based algorithms. Thus, Japanese text is parsed into

words in a way that is reasonable to a Japanese speaker. 



4.6 Improved locked table headers 



When scrolling horizontally in wide tables, locked table headers now stay synchronized with the table body so that the headers line up with the

correct body columns at all times. 



4.7 Software-based licensing removed 



All DynaText licensing is now based on a paper license agreement, whether for a full or evaluation license. Thus, there is no longer any need for

programs such as pubbook, ebtcert(ify), ebtserve, etc. There is no more need for the data/security directory. There is no more need for

DTEXT_AUTH or MKBOOK_AUTH settings in the configuration files. 



4.8 InStEd runs in its own locale on Windows 



You can now override the system locale and the DynaText standard locale when running InStEd on Windows operating systems. Assume you are

running on German Windows 95 or NT and you don't want InStEd to be localized in German. You can make InStEd run in English by adding the

following line to your DYNATEXT.INI file: 



INSTED_LOCALE=C 



4.9 Printing to a file on all platforms 



In past releases DynaText supported printing to a file on UNIX. This feature is now available on Windows as well. 



4.10 Support for relative paths (Windows only) 



All executables using the -col option with a relative path should be considered to be relative to the DynaText bin directory. It is highly discouraged to

put your bin directory on the windows path. For example, if DynaText is installed in c:\dtext41 and you enter the command 



mkbook -col ..\mycoll mybook 



from any directory, mkbook will look for the collection 



c:\dtext41\mycoll. 



4.11 Location irrelevant RAM books 



RAM books that live outside the normal book structure are allowed. If the publisher wishes to not use the normal book structure, it is acceptable to

mandate that all required files live co-located in the same directory. 



The user should be able to double-click (DynaText, Windows only) on the SGML or XML file to open the RAM book. 



4.12 CGM Plug-in option 



The DynaText CGM Plug-in provides superior support for CGM graphics. It is available as an extra option for DynaText customers; it is not part of

the standard DynaText installation. 



================================================ 



5.0 Documentation Update: Variable Assignment in Styles (introduced in DynaText 3.1)



Introduction 



DynaText 3.1 and later versions have a feature for advanced users called variable assignments, which can improve browser performance. A

property called set-var is used in the stylesheet to set variable values that get plugged into other property-value functions. Then the getvar property

retrieves the information from the value that was set using set-var. This feature is especially useful for extensive, complicated property-value functions

or for properties that are used repetitively in a stylesheet. There are examples at the end of this document that show how to use this feature. 



In addition, variable assignment, used with an option for mkbook called -cachevars, can be used to improve rendering performance. Without the use

of assigned variables, each property-value function is computed at runtime whenever the element is about to be displayed in the browser. If you have

used the set-var property to set variables in the stylesheet and you run mkbook -cachevars, variable values will be computed at mkbook time and

stored for later use by the DynaText Browser. This saves the Browser from having to recompute a particular property-value function at runtime, and

in certain cases, can result in a significant performance improvement. 



Important Notice: 



   1.This is an advanced stylesheet feature. Novices to DynaText should become thoroughly versed in the basic stylesheet language (see

     "Publishing: Document Preparation"). 

   2.It is best to delay variable assignments until a set of stylesheets is mature and generally stable. 



This documentation discusses the following: 



     Computation Strategies 

     Using Variables 

     The set-var Property 

     Property-Value Functions 

     When is Variable Assignment Most Appropriate? 

     Cautions 

     Examples of Variable Assignment 



=================================================================



Computation Strategies 



Book-specific values of assigned variables are computed in one of the following ways: 



     Caching 

     Mkbook now supports a variable-caching option, cachevars, (mkbook -cachevars ...). With the cachevars option, mkbook calculates

     variable assignments for each style, one by one. 

     When run with the cachevars option, mkbook performs an additional pass over an already built book (the binary book data). The additional

     pass can occur immediately after the first pass (during the initial mkbook run), or the cachevars pass(es) can be delayed and run separately. 

     For some operations, especially ID matches and queries, variable assignment and caching of variables significantly reduces rendering time in

     the Browser, helping to optimize performance. 

     Caution: Value caching is appropriate only for property-value functions that can be exclusively computed from data in the current DynaText

     book. 

     The Browser uses cached values first, if any exist. On encountering a style with a variable assignment, the Browser first looks in the current

     element for a cached value. If the value exists, the Browser substitutes it for the variable in the expression. 

     Dynamic computation 

     On encountering a variable assignment whose value is not cached in the book, the Browser dynamically computes the variable. InStEd always

     generates the values dynamically, whether cached values exist or not. This permits InStEd to validate each new or modified variable

     assignment immediately. 

     Dynamic computation of variables occurs on an element-by-element basis. Whenever an element is brought into view, all of its variable

     assignments are computed and stored in memory until the element scrolls out of the view. 

     Caution: To cache variables for any of the books that share a set of styles, ensure that all variable assignments require only the book's internal

     data or data available in other built books of the collection. However, if none of the books contain cached variables, it is feasible to use

     variable assignments for variables whose values depend on information that is not available to mkbook (environmentally-dependent

     variables). It it important to realize that dynamically computing a variable that requires disk access, combined with the overhead of variable

     assignments, can actually slow down the Browser. 



=================================================================



Using Variables 



Using variables involves two fundamental steps: 



   1.Assigning an expression to a variable name 



     The variable-assignment property, set-var, enables you to specify a set of variables on a specific style. To enable the value of an expression to

     be cached, add the expression to the set-var property of the current style; for example: 



     set-var         matchval=idmatch(id,attr(rid))  



   2.Accessing the variable value in one or more property-value functions of a style 



     The get-variable property-value functions include: getvar(), getinheritedvar(), and getnearestvar(); for example: 



     script          ebt-link target=getvar(matchval)



Reference: 



     Using variable assignment in table styles typically has little if any impact on table rendering. However, for extremely large and complex tables,

     variable assignment may sometimes improve rendering speed. If you use variable-assignment on tables that must respond dynamically to

     screen width, see the related property-value function: rescale(). 



================================================================= 



The set-var Property 



Overview 



If present in a style, set-var is always treated as if it were evaluated first. Evaluation of set-var assignments moves from left to right. The expression(s)

can depend on results from earlier set-vars on that property (for that element). 



Assigned variables can be used in any property values of the style. To reference these variables use the following property-value functions: getvar(),

getinheritedvar(), or getnearestvar() function. 



-----------------------------------------------------------------



Syntax 



The <set-var> property has the form: 



set-var  name1="expression1"  name2="expression2" ...



For example: 



Property setting(s) 



set-var matchval="idmatch(id,attr(rid))" mtsval="maketablestructure(cals,1000)"



The name parameter conforms to the same syntactical rules as attribute names. In the set-var property, line breaks and tabs are not valid. 



-----------------------------------------------------------------



Embedding quotation marks within an assigned variable 



Often in a variable assignment, parts of the expression are already enclosed by single (' ') quotation marks or double (" ") quotation marks. You can

enclose the whole expression within quotation marks, as follows: 



   1.Choose what type of quotation mark (either single or double) to use as the outer quotation marks of the expression. 

   2.If the expression contains any of the same type of quotation mark, double each of the internal marks. 



For example, assume an original expression of the following form: 



        "xyz" q 'w' z



To prepare to use single quotation marks for the whole expression, double pre-existing single quotation marks: 



        "xyz" q ''w'' z



To prepare to use double quotation marks for the whole expression, double the pre-existing double quotation marks: 



        ""xyz"" q 'w' z



Enclose the whole expression with single or double quotation marks. 



Enclosed using single quotation marks: 



        '"xyz" q ''w'' z'



Enclosed using double quotation marks: 



        """xyz"" q 'w' z"



=================================================================



Property-Value Functions 



getvar(name) 



returns the value of name as set in the set-var property for this element; for example: 



<script> ebt-link target=getvar(matchval)

  

<make> getvar(mtsval)



NOTE: getvar(name) is the simplest, easiest use of the variable assignment feature. For most cases, you will want to use this property-value function

to get the value of variables. The rest of the property-value functions are for extremely advanced users. 



-----------------------------------------------------------------



getinheritedvar(name) 



returns the value of name as set in the set-var property for this element or for the first containing element in which this value is defined. 



-----------------------------------------------------------------



getnearestvar(name, tag, [n]) 



returns the value of name computed for the set-var property on either this element or the nth containing element of the specified tag. 



-----------------------------------------------------------------



rescale(expression, factor): 



takes an arbitrary expression and replaces every number with itself multiplied by the scale factor. The rest of the expression remains unchanged. This

facilitates optimization of tables whose table information depends on the width of the display screen. 



For example: 



rescale('table-part column-widths="250 400 100 250"', 

mult(.001,var(hsize)))



for var(hsize)=500 results in: 



table-part column-widths="125 200 50 125"



NOTE: The result of a rescale may not be an integer and may cause problems for some properties. Use of the int() property-value function may be

helpful. 



=================================================================



When Is Variable Assignment Most Appropriate? 



You should experiment with different ways to take advantage of variable assignment in your stylesheets. However, some guidelines and cautions

exist. Variable assignments are likely to be useful in the following circumstances: 



     Variable Assignments and Links 

     Variable Assignments and Mapping Functions 

     Variable Assignments and Text-Before/After Properties 

     Variable Assignments and File-Opening Functions 

     Variable Assignments and Tables 



Reference: Also see the following section, "Cautions". 



================================================================= 



Cautions 



Generally, you can extract an expression for assignment on the set-var property and directly reference it on a variable-assignment function such as

getvar(). However, in some cases, assigning variables is inappropriate. This section discusses circumstances in which variable assignments are usually

inappropriate or where caution is necessary. 



The successful use of -cachevars is dependent on it being performed in the context of the final configuration. This is particularly critical for the caching

of variables that depend on information external to the current book; for example, in scripts for external links. 



The use of -cachevars to cache information about another book ties those two books together. If the element address for an element in another book

has been cached, any change to that other book requires the re-caching of the original book. 



Any attempt to reference information from another book during -cachevars requires that that book be available in the same relative location as where

it will be in the delivered location. 



For example, if you develop your books in three collections, COMMON, UNIX, WINDOWS, but only deliver a single combined collection:

COMMON and UNIX or COMMON and WINDOWS, you must perform your -cachevars on the combined collection if there are dependencies

in the set-var properties on books from the other collection. Note also that this implies the books from the COMMON collection will be different in

the two combined collections due to the caching of information which comes from the UNIX or WINDOWS collection. 



Reference: Also see the preceding section, "When is Variable Assignment Most Appropriate?". 



-----------------------------------------------------------------



Maximum property-value length 



The maximum length of a property value is 1K. Therefore, be careful not to overload your property-value functions. 



-----------------------------------------------------------------



Environmentally Dependent Variables 



Several property-value functions contain variables that are dependent on the environment. These are called environmentally dependent variables.

On encountering an environmentally dependent variable, the optimization phase of mkbook issues a warning that it cannot use environmentally

dependent variables. 



Examples: 



     readfile() 

     dir() 

     var(hsize) 



A script property containing portions that require evaluation in the context of a target book when doing an ebt-link is demonstrated below: 



For example, the script: 



Original property setting(s) 



script          ebt-link window="new" book=attr(book) root=idmatch(id,

                attr(rid))



Is optimized as follows: 



Variable-assignment property setting(s) 



set-var         rootval=evalinbook(join('idmatch(id,'attr(rid),')'),

Adi3xDocument,join(dir(coll),'/book/',attr(book)))



script          ebt-link window="new" book=attr(book) root=getvar(rootval)



=================================================================



Examples of Variable Assignment 



Introduction 



This section contains the following before-and-after examples: 



     Example: Cross Reference Style 

     Example: Figure-Caption Style Using Text Before 



-----------------------------------------------------------------



Example: Figure-Caption Style Using Text Before 



Here is an example of how to make this stylesheet change (ARTCAP is the figure element): 



Old fulltext.v Stylesheet 



Property settings for style ARTCAP: 



font-family     &title.font

font-weight     bold

font-size       12

foreground      &art.color

text-before     Figure if(gt(cnum(ancestor(CHAPTER)),1),

                   join(sub(cnum(ancestor(CHAPTER)),1),

                   -gcnum():),gcnum():) attr(TITLE)



Variable-Assignment fulltext.v Stylesheet (Optimized) 



Property settings for style ARTCAP: 



font-family     &title.font

font-weight     bold

font-size       12

foreground      &art.color

set-var         Art1="if(gt(cnum(ancestor(CHAPTER)),1),

                    join(sub(cnum(ancestor(CHAPTER)),1),

                          - gcnum():),gcnum():)"

text-before     Figure getvar(Art1) attr(TITLE)



Example: Cross Reference Style 



Old fulltext.v Style 



Property settings for style XREF (group=HOTTEXT): 



font-family     &hottext.fontfam

font-slant      &hottext.slant

script          ebt-link root="idmatch(ID,attr(rid))"

                   window=revelatory



Variable-Assignment fulltext.v Stylesheet 



Property settings for style XREF (group=HOTTEXT): 



font-family     &hottext.fontfam

font-slant      &hottext.slant



set-var         xRefVal="idmatch(ID,attr(rid))"

script          ebt-link root=getvar(xRefVal) window=revelatory



================================================



6.0 Problems Resolved in Release 4.1 



====================================================================== 



This section lists problems that have been resolved in this release of DynaText. 



     EPSqa22397 EPSqa21912, EPSqa21451 "Fixed Locked Headers in Tables" The table header now scrolls with the table. 

     EPSqa21260-- Line breaks incorrectly on rsquo entity 

     EPSqa21733-- RAM XML books crash DynaText unless DTD is specified externally 

     EPSqa21695-- Mkbook 4.0 generates incorrect message:tdir element %ld 

     EPSqa20660-- DynaText doesn't handle display math mode in TeX 



7.0 System Limitations and Known Problems 



7.1 System Limitations 



Limitation: 



There is a 25 KB limit for Export to Clipboard. 



Workaround: 



For selections larger than 25 KB, use Export to File. 



Limitation: 



Proximity searches of the type "within 1 word of" do not return hits for the portions of hyphenated words that follow the hyphen. Words separated by

hyphens are treated as different words. 



Limitation: 



DynaText 4.1 for Windows no longer supports the OLE plugin module that provides object linking and embedding. 



Limitation: 



When using the Automap Styles for DynaWeb feature of InStEd and mapping styles to a dynaweb.wv stylesheet, be sure to make all group names

uppercase in InStEd. 



Limitation: 



Installation 



IMPORTANT for Windows Users: If you install a new version of a Windows operating system in a new directory and try to run DynaText under the

new operating system, you will encounter the following problems: 



     The search edit field remains grey, even when you select a searchable collection. 

     Attempting to open any books results in the following error:  Error Cannot Open Book 



These problems can occur because DynaText is not registered with the new operating system. Simply re-register ADI by double-clicking on the

DynaText "ADI Registration" icon. 



------------------------------------------------------------------------- 



7.2 Known Problems 



EPSqa21202 Select property doesn't work on groups 



Problem: 



     Select property doesn't work on groups.





Example: 



     Given element A which belongs to group B, and a third element C which

     specifies a foreground color of red, if the <select> property of A is set

     to "C", the text appears in red.  However, if the <select> property of B

     is set to "C", the text does not turn red (in InStEd or in DynaText), even

     though all the properties of both A and B say "UNKNOWN due to select" and

     the <select> property of A explicitly says "C".







Workaround: 



     This is a limitation of DynaText. Select may not be used on groups.





EPSqa17612 Simple searches fail with memory allocation problems 



Problem: 



     DynaText runs out of memory on certain types of searches.  On the 

     Macintosh operating system, the application can crash.





Symptoms: 



     This problem occurs with regular expression searches that produce a

     lot of hits and element searches.  Usually the search result is large

     because there are too many hits that match the search criteria.





Workaround: 



     One way to alleviate this problem on the Macintosh is to increase the

     size of the memory partition.  Allowing the application to allocate

     more memory will solve the problem for most searches.



     If the memory partition cannot be increased to a size that will accommodate

     the search, DynaText can be configured to fail on searches that produce

     hit lists that are too large to process.  This is done by adding a new

     section to the dynatext configuration file (dynatext.cfg on the mac) 

     called [search] and add the entry DEFAULT_QUERY_HIT_LIMIT.   Note the 

     following example:



        [SEARCH]

        DEFAULT_QUERY_HIT_LIMIT    ###



     where ### is a positive number.  A good value for this number would 

     be 10000.   This value is high enough to process most queries on most

     documents and low enough to accommodate a moderate partition size.



     There are two reasons not to use this setting if queries are not taking

     up too much memory.  The first is that there is a slight performance

     penalty to do the check.  The second is that if the limit is too low,

     the search will fail.



     For the 3.1.1 release on the Macintosh, this limit is only applied to 

     regular expression searches and tag searches.  E.g:



        te*t



     and



        text in <element>





EPSqa20686 nd.sys is always empty unless the system identifier is given physically 



Problem: 



     nd.sys is always empty unless the system identifier is given physically

     in the entity declaration.



     When the system identifier appears not in the entity declaration but in the catalog or 

     system file, it is not stored as an attribute during mkbook.



EPSqa21714 Short-cut keys in search history dialog box do not work 



Problem: 



     Short-cut keys in search history dialog box do not work.





Workaround: 



     Note that quick keys work only the first time when you open the

     "Search History" dialog box. After the first time, the focus

     automatically changes to the main window and the quick keys fail to work.

     To make the quick keys work again, just click on "Search History" dialog

     box to change the focus.





EPSqa20547 Graphics print at different sizes 



Problem: 



     Some inline graphics of a group which has common sizes/dpi print at

     different sizes; some print larger than others. This occurs

     only when you use DynaText 3.1, or later releases of DynaText. 

     With DynaText 2.3 browser the inline graphics print at the same size.





Workaround: 



     Edit the stylesheet widths manually so that all graphics print at the

     same width.







EPSqa21330 Text is black when changing system to black background and white text 



Problem: 



     In Windows 95 (or Windows 3.11) if you change the system colors

     to white on black (e.g. High Contrast Black) then all the text in

     DynaText fulltext view disappears because black text on a black

     background will not show. This applies to DynaText 3.1.1 release 

     and later releases of DynaText



     DynaText 2.3 uses the default system colors for the

     foreground and background. Later versions use the

     default system colors for the background. The foreground color

     is always black unless it is changed in the stylesheet.

     This applies to DynaText 3.1.1 release and later releases of DynaText





Symptoms: 



     Book Text blends in with the black background and cannot be seen.







EPSqa22603 Property area is not rendered properly (Japanese InStEd) 



Problem: 



     The property control area is not rendered

     properly. This issue is seen in Japanese InStEd.





Symptoms: 



     Only one or two properties are displayed in the

     property control area. The rest of the area is blank.



       

        



Workaround: 



     When you see this happen, click the blank part in the

     property control area. The hidden property will

     appear. 





EPSqa22538  Context of DynaText help (reader guide book) is not shown correctly (Japanese) 



Problem: 



     The context of Japanese DynaText help (Reader Guide) is not

     shown properly in Japanese DynaText 4.1 for Windows.







Symptoms: 



     When DynaText help (Reader Guide book) is opened, all of the 

     Japanese characters are not seen in the content view.



      



Workaround: 



     Select alternate stylesheet to refresh the DynaText help

     view. 





EPSqa22546  Uninstalled Query Enhancement options are seen in DynaText preference dialog (Japanese) 



Problem: 



     Uninstalled Query Enhancement options are seen in DynaText preference dialog 

     box.(Windows platform)







Symptoms: 



     When installing Query Enhancement with only Japanese language stemming 

     features, the DynaText advanced search dialog enables the user to 

     check on/off the following Query Enhancement options which are not provided 

     for Japanese language in this release:



        Customized Thesaurus

        Compounding/De-compounding

        Normalization





Workaround: 



     When you install only Japanese QE, ignore those check boxes.





EPSqa21250  vrule is not printed when indent=0 



Problem: 



     Vertical ruled line is not printed when indent=0 is used.





Example: 



      

     Modify fulltext.pv of Reader Guide. Add vrule=surround of any element

     Change all indent(first, left, right) =0.





Workaround: 



     Avoid using "indent=0".







EPSqa22239 Print dialog doesn't highlight selected items properly 



Problem: 



     The print dialog doesn't highlight selected items properly in Dynatext

     4.1.



Symptoms: 



     All selected TOC entries are not being highlighted.





EPSqa22591 Japanese Query Enhancement limitation is not described 



Problem: 



     There are some limitations to Japanese Query Enhancements.



     Japanese Query Enhancement is only applied for Stemming in this version.

     Other Query Enhancements for Thesaurus, Compounding/De-compounding,

     and Normalization are not available for this Japanese DynaText release.



EPSqa20868 Icons are extremely small on printed page 



Problem: 



     In printed versions of books, icons appear extremely small.

     Icons appear as tiny black boxes, tiny in relation to nearby text 

     compared with online viewing.





Workaround: 



     The suggested workaround is to convert each icon's bitmap into

     a raster object, then change the stylesheet from using <icon-position>

     and <icon-type> properties to just using a regular <inline> property.

     This also allows direct control of the dimensions for display and

     printing. Use the width= parameter on the <inline> raster script. 





EPSqa08084 "not " searches do not work outside a container 



Problem: 



     Inside queries involving booleans and "nots" yields inconsistent results.





Example: 



     The following query does not work as expected:



     (stylesheet and not print) not in <chapter>



     Presumably, this should find "stylesheet" not near "print"

     and not within a <chapter>.  In fact, in this case, "stylesheet"

     is found when it is not inside of a <chapter> but NEAR "print" instead

     of NOT NEAR print.





EPSqa14941 Search keywords should not be recognized in GIs 



Problem: 



     Searching for an unquoted element name that contains any query keyword 

     (for example:  sugar inside <recipe-or-ingredient>) produces a 

     syntax error.





Workaround: 



     To search such an element name, embed it within quotation marks; 

     for example:



        sugar inside <"recipe-or-ingredient">







EPSqa13758 Katakana book titles are not sorted properly in collection window 



Problem: 



     Katakana book titles are incorrectly sorted in the collection window.





Workaround: 



     Set the SORTED=FALSE in the booklist.txt file. Then manually arrange 

     the items in the order that you want.





EPSqa13329 Space after close parenthesis in equation 



Problem: 



     A superscript that follows a close parenthesis

     may be horizontally offset more than it should be.





EPSqa22688 TeX errors seen during execution of mkbook (SGI) 



Problem: 



     Building equations using mkbook on the SGI platform is no longer supported. 

     The public-domain TeX executables shipped with DynaText are incompatible 

     with SGI IRIX 6.2. You will see TeX errors during execution of mkbook.

     Customers wishing to build equations may obtain the public domain TeX code 

     from the American Mathematical Society (see http://www.ams.org/index/tex/)

     and attempt to recompile it for this platform. The rendering of previously 

     created equations is supported.







EPSqa14190 Views without TOCs can't export entire range 



Problem: 



     The option "Export the full contents" from the Export Dialog does not

     work if the destination is the clipboard and the source window does not

     have a TOC associated with it.





Symptoms: 



     With a book view open without a TOC, exporting "full contents" to the 

     clipboard results in either an empty clipboard or inaccurate data.





Workaround: 



     Export the "full contents" to file and copy the file to the clipboard

     using a text editor.





EPSqa21398 A DTLnewfakeQuery():Query does not highlight TOC property 



Problem: 



          When a query created with the function DTLnewFakeQuery() is

          applied to a TOC view, the correct number hit is not displayed in

          the TOC view.  Currently the function only accepts the element ids; it 

          does not accept valid query data:



          start element id

          char offset inside start element

          end element

          char offset inside end element





Workaround: 



          None



EPSqa22784 Using INDEX tags without "under" attributes causes mkcolidx bus error 



Problem: 



     In DynaText 4.0 and 4.1 "mkcolidx" doesn't react to configuration 

     files containing <INDEX> tags in the same manner as previous versions.





Symptoms: 



     On UNIX systems (Solaris 2.4,2.51,2.6) mkcolidx aborts with a 

     "Bus error" when a configuration file contains <INDEX> tags with 

     no "under" attributes. On Windows 95 mkcolidx aborts and the 

     following Windows message is displayed:



     MKCOLIDX caused an ivalid page fault in module DTEXT.DLL

     at 014f:01951ddf





Workaround: 



     Add "under" attributes to all <INDEX> tags.

      



EPSqa22599 Cancel search does not work correctly and can crash DynaText 



Problem: 



     DynaText crashes if you close the book immediately after cancelling 

     the search.This is because DynaText does not immediately stop the 

     search after you press the "clear search" button.





Workaround: 



     You can prevent DynaText from crashing by not closing the book until 

     DynaText shows the partial search results.



EPSqa21169 Limitations of hotspots number 



Problem: 



     Hotspot does not work when you make more than 10 hotspots in one screen.





Workaround: 



     None



EPSqa11996 map.txt doesn't respect case of text in public identifiers 



Problem: 



     The map.txt does not consider case when resolving public identifiers. For example,

     if a map.txt were to contain the following: 

     -//EBT//TEXT IMPORTANT ENTITY//EN foo.sgm 

     -//EBT//TEXT Important Entity//EN bar.sgm 

     Then, given ... <!ENTITY impent PUBLIC "-//EBT//TEXT Important Entity//EN"> ... 

     &impent; 



     mkbook will find and incorporate foo.sgm instead of bar.sgm.



================================================ 



[End of Release Notes] 

