
****************************************************************************
Oracle Book Release Notes                                September 12, 1994

Version 2.0.4.6.0 Production
****************************************************************************

=== Note: Oracle Book V2.0.4.6.0 replaces and is fully compatible with 
Oracle Book V2.0.4.5.0 and the CDE1 Production3 products. ===

These release notes include updated information and known restrictions for 
Oracle Book V2.0.4.  The information included in these release notes is 
organized according to the following topics:

*  Oracle Book Runtime: Known Restrictions

*  Oracle Book Designer: Known Restrictions

*  Documentation Updates

The known restrictions documented apply to all platforms, unless specifically 
noted otherwise.  Numbers corresponding to the particular report in the bug 
database are listed where applicable.  These release notes will be updated 
on an ongoing basis.  If you receive a patch or subsequent release of Oracle 
Book, be sure to check the latest version of these notes.

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Oracle Book Runtime: Known Restrictions
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
______________________
All Platforms
----------------------
* If you have Book 1.0 Designer installed and install Book 2.0, Book 1.0 
Desinger will no longer function.  This problem is related to the shared 
components used by Book and other Oracle products. The error you get trying 
to run Book 1.0 Designer is: 'Builder caused a stack fault in module 
corewin.dll at 0003:1ed0'.  It is recommended that you upgrade the Designer
to version 2.0. 
   
*  Oracle Book V2.0 can use the bookshelves information stored in a 
PREFS.ORA file that was created using Oracle Book V1.0.  Once you use a 
V1.0 PREFS.ORA file with Oracle Book V2.0, the bookshelves definitions 
contained in that file is updated to reflect the new format.  Once you 
have used a V1.0 PREFS.ORA file with Oracle Book V2.0, do NOT modify 
the contents of a bookshelf using Oracle Book V1.0.  If you need to 
change the contents of a bookshelf, do so with Oracle Book V2.0.

Because Oracle Book V2.0 must update the Oracle Book V1.0 bookshelves 
information, the first time Oracle Book V2.0 reads the bookshelves 
information in a V1.0 PREFS.ORA file, response time may be slow.  Once the 
bookshelves information has been updated, however, performance time should 
return to normal.

* Oracle Book V2.0 has not yet been tested with multi-byte languages, so 
V2.0.4 does not support running with multi-byte character sets.  

*  If two documents with the same document identifiers are placed in a 
bookshelf together, Oracle Book may experience problems when trying to locate 
the targets of hypertext links or word searches.  You can view your PREFS.ORA 
file at the file system level to determine if two documents in a bookshelf 
have the same document identifier. (Bug#214947)

*  Oracle Book automatically adds the OBN file extension to any notes files 
you create (unless you specify a different file extension when you save the 
notes file).  If you save another notes file using the same name as an 
existing notes file, and do not specify a file extension, Oracle Book 
overwrites the existing notes file without a warning.  You will only receive 
a warning if you specify the existing file name and extension. (Bug#214078)

For example, you save a notes file using the Save As menu item in the File 
menu and supply the file name MYNOTES.  Oracle Book saves this file as 
MYNOTES.OBN.  Later, you save a new notes file using the Save As menu item 
in the File menu and again supply the file name MYNOTES.  Oracle Book 
overwrites the existing MYNOTES.OBN file without displaying a warning.  If, 
however, you had supplied the file name MYNOTES.OBN, Oracle Book would have 
displayed a warning asking if you wanted to overwrite the existing 
MYNOTES.OBN file.

*  The size of user notes files will vary according to the number and types 
of notes contained in that file.  Typically, image and sound annotations 
require the most space.  Because the notes file must be loaded into memory, 
Oracle Book may have trouble opening very large notes files.  You may not 
experience this problem if you have plenty of system memory available. 
(Bug#213897)

*  Deleting user links within a table must be performed from outside the 
table.  Place the cursor outside the table, then select Delete Link from the 
Edit menu.  Select the link you wish to remove from the list of user links 
that appears. (Bug#212289)

*  The Undo command in the Edit menu does not currently function when 
editing text or image annotations.  If you paste a range of text or 
image in an annotation dialog and wish to remove it, use the Cut or 
Clear menu items. (Bug#212635)

*  In the Style Properties dialog box, the Apply button is always the active 
default.  If you press [RETURN] while in this dialog, the Apply button is 
activated. (Bug#212620)

*  Word searches containing the `_' (underbar) character are not supported.  
Oracle Book interprets this character as a space. (Bug#214627)

*  Page numbers are only printed if you print the entire document. 
(Bug#214939)
 
* Book draws with the wrong color if you change the Windows color scheme. 
(Bug#228830)
 
* If running Book Runtime, you swap CD's in your CDROM drive, Book will not
notice until you open a file explicitly from the File dialog box. 
(Bug#223282)
 
* Book may be unable to import some EPS graphics files within word processor 
documents. (Bug#230353)

* Book cannot print to the HP Laserjet 4/4M driver. (Bug#225847)
______________________
Windows Restrictions
----------------------

*  If you resize the document window to a size narrower than the button bar, 
the document text, horizontal scroll bar, and button bar are cropped.  The 
vertical scroll bar is not visible at all.  This limitation will be fixed 
with release 2.0.10 of the Oracle Toolkit.  Contact your Oracle Support 
representative for availability.

* Oracle Book will not run under Windows NT.  A workaround is available; 
please contact Oracle Support if you need to run this version. (Bug 227792)

_________________________
UNIX Motif Restrictions
-------------------------

*  Using [TAB] to navigate within dialogs in Oracle Book runtime (namely 
those dealing with user notes in the Edit menu like Add note and Delete 
note) does not function. (Bug#212627)

*  Resizing the Style Properties dialog box can cause a display error with 
radical shifts in size. (Bug#211596)


+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Oracle Book Designer: Known Restrictions
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

*  Due to the default average character width, tab settings may appear larger 
than expected.  You may want to reduce the size of your tab settings by as 
much as half for your generated Oracle Book document.

*  Generating searchable documents to a database is not currently supported.  
If you wish to generate searchable documents, you must generate them to the 
file system. (Bug#214438)

*  When mapping word processor styles to Oracle Book tags, we do not 
recommend mapping styles that are used within tables in your word processor 
files.  Some word processors do not end styles within the same table cell 
they are started in.  

* Generating a document from a text file 1 megabyte or larger can cause 
Oracle Book Designer to crash.  To avoid this problem, separate your files 
into multiple files of smaller size. (Bug#222105)

* Images included in a word processor document may appear in a different
size after generating the Oracle Book document.  (Bug#223769,Bug#215909)

* Some image formats, notably 4-bit bitmaps, do not get imported from word 
processor documents.  To avoid this problem, convert the image to a 
different format (e.g., 8-bit bitmap), then paste or include the new image
file in your word processor document.

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Documentation Updates
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

*  If you are using Oracle Book Designer and wish to store documents in 
the database, please note that you will need to install the product named 
"CDE Database Tables" in order to get the SQL scripts necessary for
preparing your database.  The SQL scripts will be installed to your
ORACLE_HOME\SQL directory, and several of them will need to be run in 
addition to the SQL scripts in ORACLE_HOME\BDES20.  (See the Oracle Book
Designer's Guide p. 6-22 for more details.)

	Note:  If you have installed earlier versions of Oracle Book Designer,
	please note that the "CDE Database Tables" product replaces the "Tools 
	Utilities Database Tables" product included with earlier versions of 
	Oracle Book.

*  Note that each instance of the <tabs> tag resets the previous instance of 
a <tabs> tag, regardless of whether the tag includes the left tab (lt) 
attribute, the left indent attribute (li) or both.  For example, if you set a 
left tab with the tag <tabs lt=3>, and later want to add a left indent to the 
existing tab setting, you must enter the tag <tabs lt=3 li=3>.  If you 
inserted only the <tabs li=3>, the previous left tab setting would be cleared.

*  When you use the <caution>, <note>, and <warning> tags, make sure to add 
spaces and hard returns as necessary to format the text within the frame.  
Text included within one of these tags does not automatically wrap to fit the 
frame.


