NewDeal Hot Tip 1529General Use
When we paste a graphic into Bindery, the height of the line on which we paste it expands to accommodate the height of the graphic. This problem is easily overcome by using Manual Line Spacing (called "leading" by desktop publishers, because early typesetters used little strips of lead between the rows of type to create the extra space they desired). Select (highlight) the text, then click on the Paragraph menu, select Paragraph Spacing, Custom Spacing, and in the dialog box click on Manual for the Line Spacing setting.
Now comes a tricky part. We must make room for the graphic. This may involve a bit of trial and error.
As an example, let's say our text is in 12 point size and our graphic is one inch high. The graphic is six lines high (there are 72 points to an inch) so the graphic needs to be pasted on the sixth line of text. Don't worry about the math, this process can be done visually, it just might mean pasting in the graphic a couple times before getting it right--the bit of trial and error I mentioned.
Back to our example. On each of the first five lines of text, we need to make space for the width of the graphic. Personally, I use non-breaking space characters (ALT+SPACEBAR) to do this. If we use regular space characters, then we must insert a carriage return at the end of each line of text, which messes up the formatting of fully justified text.
Now that we've made space on the first five lines of text, we Paste the graphic as the first character of the sixth line. This process can also be used to create large initial drop caps: instead of pasting a graphic, simply insert the initial cap in a large point size.
At this point if we go back and edit the first five lines of text in our example, portions of the graphic may disappear. That's okay! It is just that the screen display has not been updated yet, a feature that lets you continue to see the text you're editing even when a graphic might otherwise be in the way. Simply press F5 or choose Redraw in menus to restore the screen.
A Book Reader file consists of one launcher that goes in the \DOCUMENT directory and one or more source files that go somewhere in \USERDATA. Let's say your launcher file is named MYBOOK.000. The path in Shipper would be:
\GEOWORKS\DOCUMENT\MYBOOK.000Let's say you have two source files named MYSOURC.001 and MYSOURC.002 and you've put them in the \BOOKS directory within \USERDATA. Then the paths in Shipper need to be
\GEOWORKS\USERDATA\BOOKS\MYSOURC.001 \GEOWORKS\USERDATA\BOOKS\MYSOURC.002Keep in mind that Shipper can't handle the GEOS 32-character directory names, so do NOT create a directory in \USERDATA with lower case letters, spaces, or more than 8 characters. Make sure that the directory containing your source files does not contain an "@dirname.000" file. Look from the DOS prompt or from the Windows File Manager.
If you did create a directory that contains an "@dirname.000" file, you'll need to go back into Bindery and recompile the book using a directory name that is 8 or fewer upper case characters only.
In Preferences, Fonts, drag at least one font into the Toolbar or Menu area. Then exit Bindery and edit your GEOS.INI file. In this example, I dragged only URW Roman into the Toolbar and Menu areas. URW Roman has the font ID# 1000. You'll see keys in your [system] section like this:
fonttool = 1000All you need to do is add the font ID numbers for the bitmap fonts, like this:
fontmenu = 1000
fonttool = 100002020a0002010600Here are the font ID numbers for the four bitmap fonts:
fontmenu = 100002020a0002010600
Only if they are located on the B: drive of the Reader's Zoomer, which is unlikely. The common work around for using extra fonts in a book is to convert text to a bitmap. Since the Zoomer has a limited number of fonts pre-installed, using bitmaps provides the author with a wider range of design possibilities, without having to distribute additional fonts along with one's book.
Assuming that books will primarily be read on screen, not printed out--especially on a Zoomer--the bitmap fonts are also a good choice, since they are always very legible on screen and they draw quickly. However, they do suffer from the limitations mentioned above.
If you are installing Bindery version 1.0 into NewDeal or Ensemble, back up your GEOS.INI file. The DOS installer for Bindery 1.0 overwrites the GEOS.INI file. This is an unfortunate situation involving the installer that was corrected in Bindery 2.0. After installing Bindery, restore your INI from the backup, or copy a fresh INI from the first installation diskette for NewDeal or Ensemble 2.01, or edit the INI file as noted below. If you have Windows on your system, use the Windows installer. It doesn't overwrite the GEOS.INI.
If you've installed Bindery into Ensemble, you may want to look at the following entries in your GEOS.INI:
defaultLauncher = Bindery
defaultLauncher = GeoManagerand
productName = Geoworks Bindery
productName = (whatever your product is named)Both the DOS and the Windows installer make a new Token Database and back up the old one to TOKEN_DA.01 (or .02, or .03, etc... depending on how many already exist). Look in \PRIVDATA for a file like TOKEN_DA.01 (check file sizes to figure out which one you want) and then rename it from the DOS prompt to TOKEN_DA.000 and all your icons should be restored. This way you won't have to rescan all your old icons and the Bindery icon will be added next time you start the software.
A NewDeal guru replies:
No, it's not possible to run Book Reader solely from a CD ROM. NewDeal must run on a read/write device, because as NewDeal loads and runs, it writes new files and modifies old ones. Therefore, NewDeal cannot run solely from a CD. Examples of files that NewDeal creates or writes to while it's running are the GEOS_ACT.IVE file, the state files for all the applications that use them, the printer spool files, and the GEOS.INI file, among others.
Unfortunately, NAV does not flag the failure with a virus warning message, either, or it would be easier to track down the conflict.
There's no work around so far. If you experience this conflict, NAV must be uninstalled in order to run Bindery. Disabling NAV by removing the line that loads it in the autoexec.bat file is not adequate.
Last Modified 8 Mar 1999