ageoPub6` !PRG formatted GEOS file V1.0D4$eps24testgcP Շ ԇ%P&GEOPUB3&BLASTER'S CONVERTER V2.5GP(GEOPUB5:P*GEOPUB6AWrite Image V2.1geoWrite V2.1  ...݅ ( >1 59 ..  9 < <` " . r " `(@1ʎsAڢ9 V&iR=pppppppppp "GeoWrite sucks." I've heard the preceding comment before from quite a few people. Once upon a time I felt that way as well and settled on Busy Bee Software's The Write Stuff (aka BB Writer or TWS) as my Word Processor of choice. All of the things that geoWrite sucks at TWS makes easy. GeoWrite is a Graphical-based program so text entry is painfully slow (especially on a stock C-64 and you really notice it if you try to insert some text at the start of a long article). TWS is a text-based program so text entry is fast. You have to load GeoSpell to check your typing and get a word count. TWS has integrated word counting ability and a lightning fast Spell Checker. GeoWrite does not have macro ability. TWS has user customizable macros and comes with existing macros to make typing easier. Of course, the shortcomings of geoWrite are overcome with some smart use of the program and some hardware and software products. By setting your margins in to one screen width you could avoid the side to side screen scrolling and type fairly quickly. If you use the default BSW font you are not hampered by a lot of graphical activity redrawing fonts. There are numerous Word Count utilities including some Desk Accessory versions that let you check your word count as you type (my favorite is the DA WordCount 2.0 by Michael Myers). Once I got a 4 MHz Schnedler Turbo- Master Accelerator I had a hard time typing faster than what geoWrite could keep up with. With the 20 MHz SCPU I rarely bother moving my margins in and always use the font I want rather than having to change it later. ppppppppp@@Unbeatable Format ppppppppp@ But, the one thing that geoWrite has going for it that no other Word Processor can touch is a format ready-made for importing into geoPublish. To ensure that geoPublish could satisfy the needs of as many {II OG`olee oIΣI OG`,0D J aU 8 8pppppppppusers as possible Berkeley Softworks planned ahead and created the Text Grabber to make it easy to import text from numerous Word Processor programs. Not only did this mean that people could use their favorite program but it meant that publishers could accept contributions from non-GEOS users and easily include these articles in their geoPublish projects. The reason this subject has come up this time is that I have been using geoWrite to write some of the articles in this series. Since I want to use geoPublish on my 128D with the 20 MHz SCPU to make it easier to document procedures I have been relegated to using geoWrite on my 64-C at 1 MHz. Uggghh! Due to the very slow performance at 1 MHz (I have been spoiled for the last 11 years with different accelerators) I have again resorted to using other Word Processors to write some of these articles. It occurred to me that many of you will do the same when it comes time to create your own gP Masterpieces. ppppppppp@@Sprechen Sie Deutsches? ppppppppp@ No. I don't speak German either but at one time I had a need to translate some German (geoDOS Dox) into English. I needed a way to handle the translation. Since all files imported into geoPublish have to be in geoWrite format how do we go about translating one format to the other? As mentioned, the BSW Text Grabber program allows easy import of files created by EasyScript, PaperClip, SpeedScript and WordWriter plus it has 3 Generic Import Forms. To import files created by BB Writer you would use the "Generic 1 Form". To make this easier to remember I renamed a copy of Generic 1 to "TWS Form". In addition to the Text Grabber a number of people created other programs to import files into geoWrite format. Red Storm (aka Joe Buckley) created numerous versions of WrongIsWrite (WIW) which isfy the needs of as many {II OG`olee oIΣI OG`,0D J aU 8 8ppppppppp@will import ASCII files as well as converting between versions of geoWrite. Markus Kanet wrote geoDOS and it excels at file conversions. You can convert C= and PC text (ASCII) files into geoWrite format and set the font, margins and tabs at the same time. Maurice Randall warns that geoDOS affects certain areas that geoWrite uses and suggests rebooting Wheels after using geoDOS. 888888888@One other program that is very handy to have when you are working with multiple geoWrite files and converting between different formats is Toolkit (or Toolkit.80 for GEOS 128 users) by Rick Krantz. This little gem lets you change fonts and margin settings on entire documents very easily. I keep Text Scraps of regular margin settings I use in an Album to make it even easier to get just what I want. c3 a>q oBL  ZZZujZZLZBLs sU; q; iD ~ B` .644L78888888880 If you don't have geoWrite 2.1 (you should pick up a copy of GEOS V2.0 right away) you also need to be careful to use copies of your geoWrite files when working on a geoPublish project. GeoPublish converts all geoWrite files into geoWrite V2.1 format so you won't be able to read them with previous versions of geoWrite. This will mean using a program like WrongIsWrite to convert the geoWrite file back if you want to edit it outside of geoPublish. ppppppppp@ 888888888@There are plenty of other top-notch geoWrite utilities but we have seen enough so far to help us in creating the best geoPublish projects we can. Next time we will import more of our articles and look at other ways to fit our files into geoPublish. Until then, enGEOy your Commodore!et just what I want. c3 a>q oBL  ZZZujZZLZBLs sU; q; iD ~ B` .644L7jj