@DATABASE "Wordworth PD Guide"
@AUTHOR Ryan Morse
@(c) Copyright © 1995 Ryan Morse
@$VER: WordworthPD.Guide 1.1 (2/2/96)
@MASTER "WordworthPD.Guide"
@INDEX "Index"
@FONT topaz 8
@WORDWRAP
@REMARK "Created in Wordworth by WordworthPD"

@NODE MAIN "Table of Contents"
@{fg highlight}@{u}Wordworth PD@{uu}@{fg text}

                         @{u}Wordworth PD Guide@{uu}

                  @{fg highlight}Volume 1.1 © Ryan Morse 1995/96@{fg text}

Table of Contents:

@{" The Author               " Link Author} About the author
@{" Copyright & Legal Issues " Link Legal_Issues} Copyright issues
@{" System Requirements      " Link Sys_Req} What Amiga do I need?
@{" Installation             " Link Installation} How to install these files
@{" Other Products           " Link Other_Products} Related products
@{" Your Support             " Link Support} How you can help
@{" History                  " Link History} History of Wordworth PD
@{" Index                    " Link Index} INDEX 

@{" Templates                " Link Template_List} Wordworth templates
@{" ARexx macros             " Link ARexx_List} Wordworth macros
@{" Tips & Tricks            " Link Tips_List} Wordworth work-arounds

I can exclusively reveal that I am writing a book on Wordworth. The book is called Making the Most of Wordworth, and will be published by Bookmark Publishing. It will be available in the summer. You can contact Bookmark Publishing on 01525 713671. We can not release any details yet, but if you would like to receive an information leaflet, then please contact Bookmark Publishing. They will include your details on their database, and you will receive the leaflet when it is ready.
@ENDNODE
@NODE INDEX "Index"
@{fg highlight}@{u}Wordworth PD@{uu}@{fg text}

	@{u}Wordworth PD Index@{uu}

@{b}Introduction@{ub}
 @{" The Author               " Link Author} About the author
 @{" Copyright & Legal Issues " Link Legal_Issues} Copyright issues
 @{" System Requirements      " Link Sys_Req} What Amiga do I need?
 @{" Installation             " Link Installation} How to install these files
 @{" Other Products           " Link Other_Products} Related products
 @{" Your Support             " Link Support} How you can help
 @{" History                  " Link History} History of Wordworth PD

@{b}Templates@{ub}
    @{" Template Notes           " Link TNotes} Important notes on templates
 1.0@{" Address Labels           " Link T1.0}
 1.1@{" Assignment               " Link T1.1}
 1.2@{" Curriculum Vitae         " Link T1.2}
 1.3@{" Disk Labels              " Link T1.3}
 1.4@{" Labels                   " Link T1.4}
 1.5@{" Letter                   " Link T1.5}
 1.6@{" News Letter Funny Bonez  " Link T1.6}
 1.7@{" News Letter Monitor      " Link T1.7}
 1.8@{" Normal                   " Link T1.8}
 1.9@{" NUS ID                   " Link T1.9}
 2.0@{" Picture Frame            " Link T2.0} Ideal for Wordworth 5 (and up)
 2.1@{" Amiga Guide              " Link T2.1}
 2.2@{" Fax                      " Link T2.2}
 2.3@{" Cassette Sleeve          " Link T2.3}
 2.4@{" Curriculum Vitae Display " Link T2.4}

@{b}ARexx macros@{ub}
 1.0@{" Quick Convert            " Link A1.0} Convert files to the new Ww format
 1.1@{" Text 2 Frame Cut         " Link A1.1} Place text in a frame @{b}(Ww 5)@{ub} 
 1.2@{" Proper Grammar Export    " Link A1.2} Export documents for Proper Grammar
 1.3@{" Proper Grammar Import    " Link A1.3} Import documents back to Wordworth
 2.2@{" PC Convert               " Link A2.2} Covert files for PC/Word Perfect @{b}(Ww 5)@{ub}
 2.3@{" NEW Example              " Link A2.3} Example script
 2.8@{" Proper Grammar Export 2  " Link A2.8} Export documents for Proper Grammar
 2.9@{" Proper Grammar Import 2  " Link A2.9} Import documents back to Wordworth
 3.0@{" Text 2 Frame Get         " Link A3.0} Place text in a frame @{b}(Ww 5)@{ub} 
 @{fg highlight}Wordworth Amiga Guide macros@{fg text}
 1.4@{" AG Tutorial              " Link A1.4} Not included yet!
 1.5@{" AG Create Nodes          " Link A1.5} Create nodes easily
 1.6@{" AG Link Node             " Link A1.6} Create textual links to nodes
 1.7@{" AG Link External Data    " Link A1.7} Launch files from text buttons
 1.8@{" AG Highlight             " Link A1.8} Apply a highlight to text
 1.9@{" AG Bold                  " Link A1.9} Apply a bold style to text
 2.0@{" AG Italic                " Link A2.0} Apply an italic style to text
 2.1@{" AG Underline             " Link A2.1} Apply an underline style to text
 2.4@{" AG Link External Prog    " Link A2.4} Launch programmes from text buttons
 2.5@{" AG Save Documents        " Link A2.5} Save appropriate files @{b}(Ww 5)@{ub}
 2.6@{" AG Convert WB2           " Link A2.6} Convert WB3 guides for WB2 @{b}(Ww 5)@{ub}
 2.7@{" AG Strip                 " Link A2.7} Strip Amiga Guide files to text

@{b}Tips & Tricks@{ub}
 @{" Ww Compatibility         " Link Ww_Comp} Compatibility with/between Wordworth
 @{" Sections                 " Link Sections} Create different sections
 @{" Graphics 1               " Link Graphics_1} Combine vector and bitmap images
 @{" Text Effects 1           " Link Text_FX1} Create glowing text
 @{" Text Flow 1              " Link Text_Flow1} Flow text around both sides of an object
 @{" Measurements             " Link Measurements} Use different measurements at once!
 @{" Insert                   " Link Insert} How to use Insert with text frames
 @{" Auto-correct             " Link AutoC} Important note on Auto-correct
@ENDNODE
@NODE Template_List "Template List"
@{fg highlight}@{u}Wordworth PD@{uu}@{fg text}

	@{u}Wordworth PD Templates@{uu}

Wordworth has a powerful feature known as a Template, which allows the user to create a document layout that can be used again and again. This avoids the hassle of copying old documents, or saving separate preferences files. Please refer to the Wordworth manual for a more detailed description.

    @{" Template Notes           " Link TNotes} Important notes on templates
 1.0@{" Address Labels           " Link T1.0}
 1.1@{" Assignment               " Link T1.1}
 1.2@{" Curriculum Vitae         " Link T1.2}
 1.3@{" Disk Labels              " Link T1.3}
 1.4@{" Labels                   " Link T1.4}
 1.5@{" Letter                   " Link T1.5}
 1.6@{" News Letter Funny Bonez  " Link T1.6}
 1.7@{" News Letter Monitor      " Link T1.7}
 1.8@{" Normal                   " Link T1.8}
 1.9@{" NUS ID                   " Link T1.9}
 2.0@{" Picture Frame            " Link T2.0} Ideal for Wordworth 5 (and up)
 2.1@{" Amiga Guide              " Link T2.1}
 2.2@{" Fax                      " Link T2.2}
 2.3@{" Cassette Sleeve          " Link T2.3}
 2.4@{" Curriculum Vitae Display " Link T2.4}
@ENDNODE
@NODE ARexx_List "ARexx List"
@{fg highlight}@{u}Wordworth PD@{uu}@{fg text}

	@{u}Wordworth ARexx@{uu}

The ability to support ARexx macros is a new feature to Wordworth 4SE. A macro, in its basic form, is a script which contains a series of commands. These commands will be executed in turn, after each other. This allows the user to save himself, or herself, time, by executing the commands in one go. For a more detailed description of ARexx please refer to the Wordworth manual, and/or review these scripts to gain a better understanding.

 1.0@{" Quick Convert            " Link A1.0} Convert files to the new Ww format
 1.1@{" Text 2 Frame Cut         " Link A1.1} Place text in a frame @{b}(Ww 5)@{ub} 
 1.2@{" Proper Grammar Export    " Link A1.2} Export documents for Proper Grammar
 1.3@{" Proper Grammar Import    " Link A1.3} Import documents back to Wordworth
 2.2@{" PC Convert               " Link A2.2} Covert files for PC/Word Perfect @{b}(Ww 5)@{ub}
 2.3@{" NEW Example              " Link A2.3} Example script
 2.8@{" Proper Grammar Export 2  " Link A2.8} Export documents for Proper Grammar
 2.9@{" Proper Grammar Import 2  " Link A2.9} Import documents back to Wordworth
 3.0@{" Text 2 Frame Get         " Link A3.0} Place text in a frame @{b}(Ww 5)@{ub} 

 @{fg highlight}Wordworth Amiga Guide macros@{fg text}
 1.4@{" AG Tutorial              " Link A1.4} Not included yet!
 1.5@{" AG Create Nodes          " Link A1.5} Create nodes easily
 1.6@{" AG Link Node             " Link A1.6} Create textual links to nodes
 1.7@{" AG Link External Data    " Link A1.7} Launch files from text buttons
 1.8@{" AG Highlight             " Link A1.8} Apply a highlight to text
 1.9@{" AG Bold                  " Link A1.9} Apply a bold style to text
 2.0@{" AG Italic                " Link A2.0} Apply an italic style to text
 2.1@{" AG Underline             " Link A2.1} Apply an underline style to text
 2.4@{" AG Link External Prog    " Link A2.4} Launch programmes from text buttons
 2.5@{" AG Save Documents        " Link A2.5} Save appropriate files @{b}(Ww 5)@{ub}
 2.6@{" AG Convert WB2           " Link A2.6} Convert WB3 guides for WB2 @{b}(Ww 5)@{ub}
 2.7@{" AG Strip                 " Link A2.7} Strip Amiga Guide files to text

NOTE:  If anyone finds these Amiga Guide macros helpful, then please let me know. If they create enough interest I will then write scripts to support the few other commands. See the @{"support" Link Support} notice for more information and my address. I may also write scripts for HTML documents and Installer scripts (Please refer to ARexx script 3.0).
@ENDNODE
@NODE Tips_List "Tips List"
@{fg highlight}@{u}Wordworth PD@{uu}@{fg text}

	@{u}Wordworth Tips & Tricks@{uu}

The section is designed to supplement the templates, ARexx macros and your own creative ideas. The following links provides useful information on how to work to the limitations of Wordworth. Wordworth is not a desktop publisher, but a word publisher, yet still offers great power for users who wish to present high quality work of a desktop publishing standard. I hope these "work-arounds" are useful to you.

 @{" Ww Compatibility         " Link Ww_Comp} Compatibility with/between Wordworth
 @{" Sections                 " Link Sections} Create different sections
 @{" Graphics 1               " Link Graphics_1} Combine vector and bitmap images
 @{" Text Effects 1           " Link Text_FX1} Create glowing text
 @{" Text Flow 1              " Link Text_Flow1} Flow text around both sides of an object
 @{" Measurements             " Link Measurements} Use different measurements at once!
 @{" Insert                   " Link Insert} How to use Insert with text frames
 @{" Auto-correct             " Link AutoC} Important note on Auto-correct
@ENDNODE
@NODE Author "The Author"
@{fg highlight}@{u}Wordworth PD@{uu}@{fg text}

	@{b}@{u}The Author@{uu}@{ub}

Hello, my name is Ryan Morse, and I live in Milton Keynes :-)

I produced this disk because...

I am currently doing a Degree in Graphic Communication, which employs the Appl* M*cintosh. I, however, commute, and am able to use my own computer to prepare and present my work. I feel that I am a power-user of Wordworth, and push the programme to its limits, especially when my peers produce work of a lesser quality using software such as Q*ark Xpr*ss, Typ* Twist*r and W*rd P*rfect. I am familiar with these products, and they are exceptionally good (with exception to the M*c's version of W*rd P*rfect), but I can honestly say that I am loyal to Wordworth, and, more specifically, the Amiga. (Q*ark Xpr*ss, and any other desktop publisher, is only necessary if you are actually going to publish something. If you can work to the limitations of your software and can combine elements between them, then do so - the tutors only see the end result).

NOTE:  I have not included hundreds of ARexx scripts to pop-up requesters or perform basic editing functions, because these are supported (more effectively) by Wordworth, by the use of icons, short-cut key combinations and menu items. Many other software producers have filled their disks with these scripts, which are often more time consuming then using the mouse!
@ENDNODE
@NODE Legal_Issues "Copyright & Legal Issues" 
@{fg highlight}@{u}Wordworth PD@{uu}@{fg text}

	@{u}Copyright & Legal Issues@{uu}

Wordworth PD is © Ryan Morse 1995.

I would like to thank Digita for their support and kind permission to produce and release this disk.

This collection is intended as Public Domain, so please copy it and give it to all of your Wordworth owning friends. *Please read the @{"support" Link Support} notice.

I do not accept any responsibility for anything that may happen to you, your disks, your machine, your cat, your friends, or anything else you own, eat, or people you know - ESPECIALLY for the NUS identity card. All the usual disclaimers apply, and no warranty is supplied with this product.

I have not included any fonts due to copyright reasons. These are available either commercially, see @{"Other Products" Link other_products}, or by PD. Some of the fonts I used were PD equivalents. I will not send out any of these fonts, you have to obtain them either by PD libraries, commercial companies or on CD.

If anyone would like to upload these files to Aminet, please do so - just write me a letter to let me know, and keep all the files together in an archive. If the files are compiled on a CD, then I would appreciate a copy from the author, publisher or who ever. If you would like to release these files on a magazine coverdisk, then please contact me concerning certain conditions.

All trademarks are acknowledged, and I do not mean any disrespect by not mentioning all of them here.

Amiga is a trade mark of Amiga Technologies GmbH and Escom.
Wordworth, Datastore, Organiser, The Reference Library, The Classic Collection and Templates are all trade marks of Digita International LTD. and Digita Holdings LTD..
@ENDNODE
@NODE Sys_Req "System Requirements"
@{fg highlight}@{u}Wordworth PD@{uu}@{fg text}

	@{u}System Requirements@{uu}

Due to the nature of Wordworth PD, it has to share similar system requirements as Wordworth; Wordworth PD therefore requires:

  An Amiga with Workbench 2 or above
  Wordworth 3.0 or above (see notes below)

@{u}Templates:@{uu}

The templates require Wordworth 3.0 or above, some templates, however, make use of new features (such as mail merging into text frames), which is only available in newer versions.

@{u}ARexx:@{uu}

The ARexx scripts require Wordworth 4SE or above. Some scripts, however, require Wordworth 5 or above, although these are clearly marked. I have designed this disk specially for the new Amiga Magic Pack, because it contains Wordworth 4SE as standard - this is the first version of Wordworth to support ARexx.

NOTE:  Some features of the templates and ARexx scripts are only available in the full (not SE) versions of Wordworth, examples include; EPS graphic support, True Type font support and Table generation. If a SE version of Wordworth encounters an element that is not supported, it will either delete it or convert it to a common denominator (EPS graphics, for example, will be deleted, and True Type fonts will be changed to the default compugraphic font). Please refer to @{"Wordworth Compatibility" Link Ww_Comp} for more information.

This compilation was created and tested on an Amiga 1200 with 6 megabytes total memory.
@ENDNODE
@NODE Installation "Installation"
@{fg highlight}@{u}Wordworth PD@{uu}@{fg text}

	@{u}Installation@{uu}

To install the templates, just copy them into your template drawer - many users tend to leave this path as Wordworth/Document/Templates.

To install the ARexx scripts, just copy them into your ARexx drawer - many users tend to leave this assigned to the S drawer.

To install this guide, just dump it any where on your hard drive @{b}OR@{ub}, for floppy disk users, leave it on this disk. A guide has been provided for both Workbench 2 and 3 users.

Any other extras provided on this disk, install at your own discretion - they may not all be connected to Wordworth - I just wanted to provide more files to fill the disk. These @{b}do not@{ub} need to be included in any distribution archives.
@ENDNODE
@NODE Other_Products "Other Products"
@{fg highlight}@{u}Wordworth PD@{uu}@{fg text}

	@{u}Other Products@{uu}

@{u}Fonts@{uu}

NOTE:  True Type fonts are not available in the SE (Special Edition) version of Wordworth, and require more memory.

@{b}The Canon @{"BJC" Link TNotes} True Type Font Pack:@{ub}
  Charter Black Italic  (TT0709M_.TTF)
  Umbra                 (TT1074M_.TTF)

NOTE:  Please contact Digita concerning the availability of the following fonts, or refer to the Wordworth on-line help ("Wordworth Extras") for more information:

@{b}The Classic Collection (or PD):@{ub}
  Times Bold - I used a PD version.

@{b}Wordworth 3/4, and/or The Reference Library:@{ub}
  AGFA Nadianne Medium
  Futura Bold II
  Futura Book II
  Garamond Antiqua
  Garamond Kursiv
  Garamond Kursiv Halbfett
  ITC Avant Garde Gothic Book
  Microstyle
  Peignot Bold
  Peignot Demi Bold
  Shannon Book

@{b}Wordworth 2:@{ub}
  CG Palacio
  Courier
  Goudy Handtooled
  Park Avenue

@{u}Binder Covers@{uu}

The GBC A4 Binder Covers are available from Office W*rld, and come in a variety of different formats and colours (linen, oversize, etc.). Other brands are available at the same size.

NOTE:  The Assignment.GBC template requires a binder cover with a window.

@{u}Labels@{uu}

The Av*ry labels are available from Office W*rld, and are available in a number of different sizes and for different products, i.e. Ink Jet printers, Postscript printers, photocopiers and dot matrix printers. The templates exclusively use the Ink Jet labels, product code J8165M. The size of these labels are 99.1 mm x 67.7 mm, and are provided eight to a sheet. The same size labels are also available for Postscript printers, although I do not know the product code.

By now you are probably sick and tired of my templates using the Av*ry labels, but it serves to show their, and the templates, versatility. The size indicated is probably the best choice for this reason. Sticking to one size will also keep down YOUR costs; they are, after all, quite expensive.

@{u}Amiga Guide@{uu}

Amiga Guide is a document file that contains certain codes to create interaction between the user and text. These files are displayed by the programme MultiView (with Workbench 3.0) or Amiga Guide (with Workbench 2). Wordworth, and other Digita products, use Amiga Guide files as their on-line help system.

@{fg highlight}Why should I use Wordworth to create my guides?@{fg text}

I have provided all the necessary templates, macros and instructions to make creating Amiga Guide files as easy as possible. These will allow you to write the guide, without having to learn the codes or use other programmes which are often confusing. Wordworth also has an extensive dictionary and thesaurus to help you find and correct any spelling mistakes easily, and wonderful search facilities.

@{b}Workbench 3.x users:@{ub}

In order to use a [Wordworth created] Amiga Guide file in MultiView, you have to save the file as ASCII. Make sure that Wordworth's ASCII options ("File Settings") are set to; "Line Breaks: LF (Amiga)" and "Save At: End of Paragraph". This will place the line breaks/carriage returns at the end of the paragraphs only, enabling the guide to take advantage of the Wordwrap facility, and thus format the text properly on any Amiga resolution.

@{b}Workbench 2.x users:@{ub}

In order to use a [Wordworth created] Amiga Guide file in MultiView, you have to save the file as ASCII. Make sure that Wordworth's ASCII options ("File Settings") are set to; "Line Breaks: LF (Amiga)" and "Save At: End of Line". This will insert line breaks/carriage returns at the end of each line, making up for the lack of the Wordwrap facility (the textwidth, however, is quite long). Alternatively, see the note for Workbench 3 users, and use a programme such as "WrapGuide" by Udo Schuermann (© 1994/1995), to change the textwidth until I can find a suitable solution to this problem.

@{fg highlight}NOTE:  A special template "Amiga_Guide_OS2" has been included for Workbench 2 users - this template does not include the WORDWRAP node, the FONT node or the INDEX node, AND a link has been provided to an Index page from the Main/Contents page.@{fg text}

NOTE:  A script has been created to convert WB 3 guides for WB 2 @{b}(Ww 5)@{ub}:

 @{" AG Convert WB2           " Link A2.6} Convert WB3 guides for WB2 @{b}(Ww 5)@{ub}

@{b}Wordworth 4SE users:@{ub}

Save two documents from Wordworth; the first file with the suffix ".Ww" to denote that it is a Wordworth file, and the second file in ASCII with the suffix ".Guide" (to denote that it is the Amiga Guide version). Make all the changes to the Wordworth file first, and then save a second copy (in ASCII) as the guide. This will allow you to load the Wordworth file in Wordworth (for updating, etc.) without any problems (it is a pain fiddling about with the ASCII settings and carriage returns on reloading an ASCII document back into Wordworth). The Wordworth file will also allow you to use page breaks, colour, etc., as your own method of separating the nodes, highlighting text that needs to be finished, etc.. These will not appear in or affect the ASCII version. Two separate documents will also allow you to test the ASCII version in MultiView, whilst making any corrections, as you find them, @{b}instantly,@{ub} to the version running in Wordworth.

@{b}Wordworth 5 users:@{ub}

A script has been provided for Wordworth 5 users:

 @{" AG Save Documents        " Link A2.5} Save appropriate files @{b}(Ww 5)@{ub}

NOTE:  You can not resave the changes to the ASCII version, if it is already running in MultiView.

@{b}I have included all the necessary scripts, and a template, to help you:@{ub}

 @{"Amiga Guide Macros        " Link ARexx_List}
 @{"Amiga Guide Template      " Link T2.1} Instructions for WB 2 & WB 3 templates

Load in this guide, or try the template and macros, to gain a better understanding of the codes.

@{fg highlight}@{b}This guide has been created exclusively in Wordworth, using these scripts.@{ub}@{fg text}
@ENDNODE
@NODE Support "Your Support"
@{fg highlight}@{u}Wordworth PD@{uu}@{fg text}

	@{u}Your Support@{uu}

NOTE: Future additions are so open, that I am not even going to attempt to include a "To Do" page.

The first volume of Wordworth PD is shareware - I have invested a lot of time and effort in producing this package, and it has extended beyond my original plans for the first volume. The shareware fee, however, is minimal:

  1. If you bought this disk from me, for £1.75 (which is the price PD Libraries usually charge for 1 disk and P&P), then you do not have to send me anything.

  2. If you received this disk from any other source, then please send me £1.00 (as if you did buy it from me).

Registered users can get free updates by sending me a blank disk and S.A.E.. Look out for reviews in magazines, inclusions on coverdisks, or notices.

@{b}Any money I receive shall not@{ub} be wasted on beer, and I will not bore you with the starving student rubbish, however, I will tell you that @{b}any money I receive will be used@{ub} to pay my shareware fees, upgrade my current software collection to new versions, buy Amiga magazines, and generally support anything Amiga.

If you would like to forward any comments, templates or other information then please contact me at the address below. Any templates or documents that I receive shall be compiled and released on the next disk. Please provide some sort of instruction file (in ASCII), along with your name for the credit. Please let me know if you wish for your address to be made public, or provide an e-mail contact number. I can not promise that I will reply to everyone, I am incredibly busy at the moment with my College work. Look forward to the next release for the inclusion of your files.

@{fg highlight}You can contact me at this address (snail mail only):@{fg text}

	Ryan Morse
	@{b}Wordworth PD@{ub}
	9 Tadmarton
	Downhead Park
	Milton Keynes
	Bucks MK15 9BE

* If anyone would like to add to my macros, then please feel free... I am particularly interested in writing a script that will take advantage of the ARexx port in MultiView (WB 3.1 only), to talk to Wordworth. This could form the basis of a whole new on-line help system, which could pop up Wordworth requesters by use of the ARexx ports. If any one knows how to do this, then please send me any examples. I will pass on any details to Digita, and hopefully they will update their current help system.
@ENDNODE
@NODE History "History"
@{fg highlight}@{u}Wordworth PD@{uu}@{fg text}

	@{u}History@{uu}

@{fg highlight}Version, Date, Comment@{fg text}

1.0 - 06/01/96

First public release, this version was only sent to all magazines and Digita.
Issued on Amiga Shopper coverdisk, April 1996.

1.1 - 2/2/96

I think that the guide is incompatible with Workbench 2, second guide created.
Digita also reported a problem with the first guide.
Changes to text.
History page added.
Added feature in all ARexx scripts to cancel script.
Minor updates to some templates.
"Amiga_Guide_OS2" template added for Workbench 2 authors.
"AG_Convert_WB2" ARexx script added.
"AG_Strip" ARexx script added.
"Proper_Grammar_EXP_2" ARexx script added.
"Proper_Grammar_IMP_2" ARexx script added.
"Text2Frame" ARexx script deleted and replaced with:
"Text2Frame_Cut" ARexx script added, and
"Text2Frame_Get" ARexx script added.
@ENDNODE
@NODE TNotes "Template Notes"
@{fg highlight}@{u}Wordworth PD@{uu}@{fg text}

	@{u}Template Notes@{uu}

@{u}Canon BJC-600 Printer@{uu}

I have provided several templates specifically for the Canon BJC-600 ink jet printer. This is because the printer reacts in a different way to that described in the manual. As an example, the printer margins in the manual are 0.5" for the head and foot margins, and 0.13" for the side margins. The paper, however, is rolled back by one centimetre when it is taken by the printer, and, as a result, the head and foot margins of the paper are thrown off-set. The templates that end in BJC, have all been altered accordingly.

NOTE:  Other Canon printers may suffer from this problem.

@{u}Other Printers@{uu}

If you find that you need to change the layout of the documents to suit your printer, then please resave the template and send me a copy for inclusion. Please add the printer name and model in the file name, as I have done, and in the comment field of the icon.

@{u}Print Borders@{uu}

The templates all use my own print borders, and you can adjust these as necessary. The print borders, however, should automatically change to suit your preferences file.

@{u}Colour sets@{uu}

The templates all use my own colour sets (Edit menu). The template for the disk labels and the NUS ID card, need these colour settings. Hopefully, a future version of Wordworth (and Datastore) will have the ability to save and load colour sets as separate files, so that they can be used and easily changed for different purposes and shared by both programmes.

@{u}Margins@{uu}

All of the templates have the margins set, these, however, may change if you have large print borders, although I doubt it. The margins are ideal for legibility - it is pointless and ineffective to try and cram too many words on to one page. It is best if you consider the possible uses of the templates before you change any of the settings.

@{u}Style Sheets@{uu}

Almost all of the templates contain styles, these should be used in conjunction with the other template data.

@{u}Fonts@{uu}

All templates have the specific fonts listed, please refer to @{"other products" Link Other_Products}.
@ENDNODE
@NODE T1.0
@{fg highlight}@{u}Wordworth PD@{uu}@{fg text}

	@{u}Template: Address_Labels.J8165M@{uu}

@{u}Introduction@{uu}

This template uses the @{"Av*ry" Link Other_Products} labels, with mail merge settings for addresses. (This template makes use of a new feature in Wordworth 3.1r2 - mail merging in text frames).

NOTE:  This template is also available in the @{"BJC" Link TNotes} format.

@{u}Usage@{uu}

Just export the contact details from your database (Datastore or Organiser) and select the Mail Merge option from the Project menu.

This template uses the address codes exported by Organiser - the labels on the left are for company addresses, and the labels on the right are for name (personal) addresses.

The labels use codes that will skip a line if the data does not exist, please refer to the NOTE below. The :IF command checks whether the record is a Company address, for the labels on the left, and checks whether the record is a Name address for the labels on the right - if either are false, Wordworth will move on to the next record. I would suggest that you change the labels as necessary, and save one template for company contacts, and another template for name contacts. I only placed both of them together as an example of the different formats.

NOTE:  I have placed the SKIP command, on the business labels, before the "Salutation" field and "LastName" field, this is because you may not know any contacts at a particular company. In this situation, Wordworth will skip on to the next field, and will not print a blank line between the "Company" field and address fields. I have also omitted the "FirstName" field, to maintain a formal approach when addressing a company.

NOTE:  If you do not use Organiser, you may have to change the field names in the template to suit your database. Organiser 2 comes complete with an address template for Datastore, and several templates for Wordworth.

To print the labels choose "Mail Merge" from the Project menu, click Select and choose the exported database file. Then click on OK, Print and Print again.

@{u}@{"Fonts" Link Other_Products}@{uu}

Shannon Book or any font; 12pt
@ENDNODE
@NODE T1.1
@{fg highlight}@{u}Wordworth PD@{uu}@{fg text}

	@{u}Template: Assignment.GBC@{uu}

@{u}Introduction@{uu}

This template is suited for anyone who is concerned about the presentation of their reports. The template uses the binder covers by @{"GBC" Link Other_Products}.

An example document has been provided.

NOTE:  This template is also available in the @{"BJC" Link TNotes} format.

@{u}Usage@{uu}

My current course has a very high demand on presentation; each assignment has to be suitable for senior management, and, as such, my College has the proper facilities for ring binding - every reprographic department, or indeed Print & Copy shop, should offer this facility, at a minimal charge.

The template uses the first page as a title cover, and offers two options; the first is a text frame, and the second uses carriage returns to pre-position the text. Please adapt the text to suit your requirements, and scroll to the second page. Remember to delete either the pre-positioned text or the text frame, depending on your preference.

The second page has a pre-positioned header, which will appear on every page hereafter. Please adapt the text to suit your requirements, and resave the template.

NOTE:  Please remember not to type in any details of a particular assignment, as this is going to be your template.

NOTE:  The Assignment.GBC template requires a binder cover with a window.

@{u}Tips@{uu}

Remember to make use of the Create List and Create Index facilities within Wordworth. I have provided an extensive list of styles for you to use; use the "Quote Source 2" to help layout the Bibliography.

@{u}@{"Fonts" Link Other_Products}@{uu}

CG Palacio; 12 point
Goudy Handtooled; 14 and 18 point
Park Avenue; 18 point
Shannon Book or Futura Book; 12 point
@ENDNODE
@NODE T1.2
@{fg highlight}@{u}Wordworth PD@{uu}@{fg text}

	@{u}Template: Curriculum_Vitae@{uu}

@{u}Introduction@{uu}

This template is a Curriculum Vitae, which is ideal for anyone.

NOTE:  I would advise that you turn on the "Show Codes" option (View menu), which will allow you to see the tabs and spaces, until you become familiar with the format. All settings are also available in the style sheets.

NOTE:  The + (plus) symbol will appear in the style sheet list because I have set the headings in bold, the data (your personal information) should be set in plain - as set in the style sheets.

@{u}Usage@{uu}

This template is ideal for the @{"GBC" Link Other_Products} binder cover, and can be used in conjunction with the @{"Assignment.GBC" Link T1.0} template (as a title page). Alternatively, you can you the special @{"Curriculum Vitae Display" Link T2.4} template to act as the title pages, for a proper display book.

The first page is designed to be sent to a future employer, and have an impact; it is simple, clear and concise (it is on one page only). The second page acts as an extension, to provide a more detailed report of your qualifications, hobbies and interests, etc.. On the first page, just present your qualifications as an outline - for example; 3 A-levels, 11 GCSE's, etc.. These can then be presented individually on the second page, and discussed at the interview. I have provided an example to help you.

The "Main Text" style is designed for text with carriage returns (i.e. address, name, etc.) and the "Extra Text" style is designed for continuous copy (i.e. hobbies and interests, etc.).

@{u}@{"Fonts" Link Other_Products}@{uu}

Shannon Book; 12 point
Goudy Handtooled; 14 point
@ENDNODE
@NODE T1.3
@{fg highlight}@{u}Wordworth PD@{uu}@{fg text}

	@{u}Template: Disk_Labels.J8165M@{uu}

@{u}Introduction@{uu}

This template is a set of eight disk labels, and is suitable for printing in either greyscale or colour. (The labels look superb on light grey disks.)

An example document has been provided.

NOTE:  These are available in the @{"BJC" Link TNotes} format.

The template uses the Ink Jet labels by @{"Av*ry" Link Other_Products}, product code J8165M. The size of each label is 99.1 mm x 67.7 mm, and there are eight to a sheet. The same labels are also available for Postscript printers.

@{u}Usage@{uu}

The colour bar at the bottom of each label is Gold, which has been set for the Canon BJC-600 printer, it should, however, produce a similar effect on a Hewlett Packard ink jet printer, or on any other non-impact printer. The settings for the Gold colour is; Red: 215, Green: 180, and Blue: 0.

Change the colour to a shade of grey for a black and white printer. If you are going to try and print the labels on a dot matrix, I would advise that you print the text frames empty and write the text by hand.

Do not use Wordworth to type in the details of the version number or the amount of disks - write these in by pencil. The reason for this is simple; if you print these fields, then when you next upgrade a programme, the version number and, possibly, the amount of disks will change, forcing you to print another set of labels. I only keep a back-up of the most recent update, and I continually change the version numbers and disk amounts by hand.

NOTE:  Do not write the version numbers in the title field by mistake, there is a separate field for this.

The disk field only contains a slash /  - write the @{b}disk number@{ub} before the slash, and the @{b}amount of disks@{ub} (that the programme is on) behind the slash. As an example, Wordworth is on four disks, so write 1/4 for disk one of four. The amount of disks will let you know how many disks the programme is on, so if, for example, you need to restore Wordworth on your hard drive, you know how many disks to find in your disk box.

The Code field refers to the code of programme, for instance; Wordworth may be coded as Word-Processor, DOpus may be coded as Workbench, and Ami-Back may be coded as Workbench.

The Type field refers to the type of the disk, for example, an Original or Back-up disk.

This disk, in my collection, would be an Original, and I would also have a Back-up. The Type would either be PD or Personal (because I am developing it).

@{u}Tips@{uu}

If you using an ink jet printer, wet your index finger and test the viscosity of the ink. If the ink smudges or runs, use hair-spray or a fixative to form a coating over the ink. This will prevent it from smudging.

Use a metal rule to cut along the trim marks.

This template can use the mail merge facility - just change the fields to that of your database (with all the relevant codes and commands « » :SKIP :ENDSKIP :NEXT), and resave the template. Please refer to the mail merging section in the Wordworth manual for more information. @{b}I have provided a template for Datastore, to record your software collection.@{ub} Please remember to move all the fields for one disk label into one text frame only, otherwise you may encounter all sorts of problems, and to use the :NEXT command for every text frame after the first.

@{u}@{"Fonts" Link Other_Products}@{uu}

AGFA Nadianne Medium; 10 point
Futura Book II; 14 point
Umbra; 14 and 18 point
@ENDNODE
@NODE T1.4
@{fg highlight}@{u}Wordworth PD@{uu}@{fg text}

	@{u}Template: Labels.J8165M@{uu}

@{u}Introduction@{uu}

This is a blank template for the @{"Av*ry" Link Other_Products} labels, product code J8165M. The size of each label is 99.1 mm x 67.7 mm, and there are eight to a sheet. The same labels are also available for Postscript printers. This template allows you to create your own label designs - please refer to the other templates in this collection for ideas.

The blank labels are also available in the @{"BJC" Link TNotes} format.
@ENDNODE
@NODE T1.5
@{fg highlight}@{u}Wordworth PD@{uu}@{fg text}

	@{u}Template: Letter@{uu}

@{u}Introduction@{uu}

This template is an example of a letter format.

@{u}Usage@{uu}

It uses three styles;

FROM: address, which is your address - this is aligned to the right, just past the right margin.

TO: address, which is the address for the letter to be sent to - this is aligned to the left, just before the left margin, and also contains an updating date and a reference number.

Main Body: this is the actual letter content.

Just change the details to your name (in the main body), and your address, and resave the template.

NOTE:  It is possible to insert fields, in the TO: address, for mail merging, but these templates are already included with Organiser 2. If you do not own Organiser just copy the fields from the @{"Address_Labels" LINK T1.0} template and refer to the Wordworth manual for information on mail merging.

@{u}Tip@{uu}

Many people combine a sans-serif font and serif in a letter; this will provide a visual difference between the addresses and body text. Sans-serif means without serifs.

@{u}@{"Fonts" Link Other_Products}@{uu}

CG Palacio; 10 point
Shannon Book; 10 point
@ENDNODE
@NODE T1.6
@{fg highlight}@{u}Wordworth PD@{uu}@{fg text}

	@{u}Template: NewsLetter_FunnyBonez@{uu}

@{u}Introduction@{uu}

This is an information sheet that can double as a newsletter. It is very simple, and I designed it to experiment with the drawing tools of Wordworth.

I do not expect you to stick to my layout, as I said - it was only as experiment, but it is still very adequate for a number of different purposes.

@{u}Usage@{uu}

The template contains all the necessary information for the layout and design of this template; text frames, graphic elements and style sheets.

I have provided an example file to give you an idea of its use.

@{u}Tips@{uu}

I have not grouped all of the elements together - so that you can easily adjust any element, such as the colour. It will also work effectively in monochrome.

If you have a colour printer, then please apply colour to the text in the style sheets - if it is to act as an information sheet, on a pin-board for instance, the colour and design will help to attract an audience.

@{u}@{"Fonts" Link Other_Products}@{uu}

Peignot Bold; 18 and 36 point
Peignot Demi Bold; 18 point
@ENDNODE
@NODE T1.7
@{fg highlight}@{u}Wordworth PD@{uu}@{fg text}

	@{u}Template: NewsLetter_Monitor@{uu}

@{u}Introduction@{uu}

This is an information sheet that can double as a newsletter. It uses a monitor for the design. Please do not adjust the text in the text frame by the monitor light - I would like some recognition.

@{u}Usage@{uu}

The template contains all the necessary information for the layout and design; style sheets, text frames and graphic elements. This template has an extensive use of internal drawings and layers, (and is ideal for testing the drawing and updating routines in Wordworth -  for Beta testers)

I have provided an example file to give you an idea of its use, this is in reference to my previous College course.

@{u}Tips@{uu}

If you need to change the red colour, for monochrome printers, be very careful of using the send to back functions - you may have to rearrange all the elements to find the lost piece.

NOTE:  If you group the text frames together, you can not type any information in them.

NOTE:  The ability to link and unlink text frames was not available at the time of compiling this disk, if it becomes available I will revise the text frames and the style sheets (the Following option). The revised template will be available in the next release.

@{u}@{"Fonts" Link Other_Products}@{uu}

Futura Bold II; 76 point
Garamond Kursiv Halbfett or Charter Black Italic; 76 point
Microstyle; 10, 12 and 14 point
Times Bold; 18 point
@ENDNODE
@NODE T1.8
@{fg highlight}@{u}Wordworth PD@{uu}@{fg text}

	@{u}Template: Normal@{uu}

@{u}Introduction@{uu}

This template is just an example of a normal template.

@{u}Usage@{uu}

The normal template is the default page set-up.
@ENDNODE
@NODE T1.9 
@{fg highlight}@{u}Wordworth PD@{uu}@{fg text}

	@{u}Template: NUS_ID@{uu}

@{u}Introduction@{uu}

This template is a National Union of Students identity card, and is designed to display the power of Wordworth.

The cards change each year and the design varies from College to College. I do not accept any responsibility for misuse of this template, and I do not condone its use as identification. The real cards have the official stamp, and any attempt of using this template may result in a criminal offence. It is for display purposes only, you may, however, change it and use it as part of a design assignment.

This design resembles the one used at Nene College in Northampton, in 1993-94, many Colleges and Universities are now using plastic cards.

@{u}Usage@{uu}

This template is only ideal for users with non-impact colour printers.

The colour set is saved in the template, although the settings I used for the "University Blue" colour is; red: 50, green: 50, and blue: 255. This is ideal for the @{"BJC" Link TNotes}, although it should suit a Hewlett Packard or any other non-impact printer - please note that outputs may vary with different printers.

I have provided styles for the main areas of change - this is to alert you if you accidentally change the point size, etc.. These include; "Main Title", "Name of Uni.", "Membership No.". These allow you to automatically apply changes to the colour, and possibly the font. The "Membership No." uses the Courier font and a grey colour to reproduce the look and feel of a typewriter.

@{u}@{"Fonts" Link Other_Products}@{uu}

Courier; 14 point
Futura Bold II; 8 and 36 point
Futura Book II; 9 point
ITC Avant Garde Gothic Book; 6, 7, 8 and 9 point
@ENDNODE
@NODE T2.0
@{fg highlight}@{u}Wordworth PD@{uu}@{fg text}

	@{u}Template: Picture Frame@{uu}

@{u}Introduction@{uu}

This is a simple template for printing pictures. If you do not own Studio print programme, or feel that you want to use the printing quality of Wordworth, then use this template. It presents a nice small picture on an A4 sheet of paper.

NOTE:  Wordworth is usually supplied with Digita Print Manager, which does impove the quality of your prints.

This template is also useful for people who wish to present text with their picture, without resorting to adding text in a paint programme (and suffering from jaggies).

NOTE:  This template is only really effective in Wordworth 5, as this new version, based on information from the advert, supports 24-Bit graphics.

@{u}Usage@{uu}

I would recommend that you use this template with high quality paper; Hewlett Packard produce some of the best paper for their, and other compatible, ink jet printers.

Personally, I print my pictures through Studio making use of the Set Aspect command (which usually sets the picture to 8" x 6.4" on an A4 sheet), and then print the title and credit through Wordworth. To use this method simply delete the picture border, picture frame and mouse pointer, and resave the template.

NOTE:  If you are the only one who is using the template, for your own creations, then type in your name and save that as the default template.

@{u}Tips@{uu}

If you would like add your name over your picture, in an exciting way without changing your picture then please refer to the @{" Text Effects " Link Text_FX1} section.

@{u}@{"Fonts" Link Other_Products}@{uu}

Garamond Antiqua; 14 point
Garamond Kursiv; 8 and 24 point
@ENDNODE
@NODE T2.1
@{fg highlight}@{u}Wordworth PD@{uu}@{fg text}

	@{u}Template: Amiga_Guide@{uu}

@{u}Introduction@{uu}

Amiga Guide is a document file that contains certain codes to create interaction between the user and text. These files are displayed by the programme MultiView (with Workbench 3.0) or Amiga Guide (with Workbench 2). Wordworth, and other Digita products, use Amiga Guide files as their on-line help system.

This template has all the necessary headings to start a new Amiga Guide document.

@{fg highlight}NOTE:  A special template "Amiga_Guide_OS2" has been included for Workbench 2 users - this template does not include the WORDWRAP node, the FONT node or the INDEX node, AND a link has been provided to an Index page from the Main/Contents page.@{fg text}

@{u}Usage@{uu}

The user only needs to change the text set in lower case.
The nodes for the contents (main) page and the index  page are already in place.

There are many ARexx scripts to help you create exciting and easy Amiga Guide documents:

 @{"Amiga Guide Scripts" Link ARexx_List}

@{u}Tips:@{uu}

@{fg highlight}Why should I use Wordworth to create my guides?@{fg text}

I have provided all the necessary templates, macros and instructions to make creating Amiga Guide files as easy as possible. These will allow you to write the guide, without having to learn the codes or use other programmes which are often confusing. Wordworth also has an extensive dictionary and thesaurus to help you find and correct any spelling mistakes easily, and wonderful search facilities.

@{b}Workbench 3.x users:@{ub}

In order to use a [Wordworth created] Amiga Guide file in MultiView, you have to save the file as ASCII. Make sure that Wordworth's ASCII options ("File Settings") are set to; "Line Breaks: LF (Amiga)" and "Save At: End of Paragraph". This will place the line breaks/carriage returns at the end of the paragraphs only, enabling the guide to take advantage of the Wordwrap facility, and thus format the text properly on any Amiga resolution.

@{b}Workbench 2.x users:@{ub}

In order to use a [Wordworth created] Amiga Guide file in MultiView, you have to save the file as ASCII. Make sure that Wordworth's ASCII options ("File Settings") are set to; "Line Breaks: LF (Amiga)" and "Save At: End of Line". This will insert line breaks/carriage returns at the end of each line, making up for the lack of the Wordwrap facility (the textwidth, however, is quite long). Alternatively, see the note for Workbench 3 users, and use a programme such as "WrapGuide" by Udo Schuermann (© 1994/1995), to change the textwidth until I can find a suitable solution to this problem.

NOTE:  A script has been created to convert WB 3 guides for WB 2 @{b}(Ww 5)@{ub}:

 @{" AG Convert WB2           " Link A2.6} Convert WB3 guides for WB2 @{b}(Ww 5)@{ub}

@{b}Wordworth 4SE users:@{ub}

Save two documents from Wordworth; the first file with the suffix ".Ww" to denote that it is a Wordworth file, and the second file in ASCII with the suffix ".Guide" (to denote that it is the Amiga Guide version). Make all the changes to the Wordworth file first, and then save a second copy (in ASCII) as the guide. This will allow you to load the Wordworth file in Wordworth (for updating, etc.) without any problems (it is a pain fiddling about with the ASCII settings and carriage returns on reloading an ASCII document back into Wordworth). The Wordworth file will also allow you to use page breaks, colour, etc., as your own method of separating the nodes, highlighting text that needs to be finished, etc.. These will not appear in or affect the ASCII version. Two separate documents will also allow you to test the ASCII version in MultiView, whilst making any corrections, as you find them, @{b}instantly,@{ub} to the version running in Wordworth.

@{b}Wordworth 5 users:@{ub}

A script has been provided for Wordworth 5 users:

 @{" AG Save Documents        " Link A2.5} Save appropriate files @{b}(Ww 5)@{ub}

NOTE:  You can not resave the changes to the ASCII version, if it is already running in MultiView.

Load in this guide, or try the template and macros, to gain a better understanding of the codes.

@{fg highlight}@{b}This guide has been created exclusively in Wordworth, using these scripts.@{ub}@{fg text}
@ENDNODE
@NODE T2.2
@{fg highlight}@{u}Wordworth PD@{uu}@{fg text}

	@{u}Template: Fax@{uu}

@{u}Introduction@{uu}

This template was passed on to me by Mark Jackson of Digita.
The template contains all the necessary details of Digita, and is an excellent example of how to design a Fax template.

@{u}Usage@{uu}

1. Draw your own logo to replace the Digita logo, or draw a text frame in its place - this should contain your company name.

2. Change the address text frame to suit that of your company address.

3. Change the name and title of the FROM: details to suit your own requirements.

4. Change the name on the main body of text to your own.

5. Resave the template.

To use this template, create a NEW document and select Fax from the list. Type in all the necessary details in regard to your fax, and save the document for reference. Then just print the document to pass through your fax machine.

NOTE:  If any one owns GP Fax, or any other Amiga fax utility with an ARexx port, then please write an ARexx script to automatically send the data. If I receive such a script, it will be included in the next release.

@{u}@{"Fonts" Link Other_Products}@{uu}

CG Palacio; 10 point
Shannon Book; 14 point
@ENDNODE
@NODE T2.3
@{fg highlight}@{u}Wordworth PD@{uu}@{fg text}

	@{u}Template: Cassette_Sleeve@{uu}

@{u}Introduction@{uu}

This template is for producing your cassette sleeves and inlays. There are two layouts on the page. (I have only placed two layouts on the first page, because you may suffer from memory problems.)

@{u}Usage@{uu}

NOTE:  All the fold marks and trim marks are provided.

The template is divided into four parts:

1. The back section, which can be left plain.
2. The spine, which contains a text effect for the title.
3. The front cover.
4, The inlay.

(4) The inlay contains facilities for mail merging. To use this feature just export the details from your database and refer to the Wordworth manual on mail-merging.

NOTE:  Make sure that the fields in the template correspond to those in your database.

There are two picture frames in the layout; the first frame covers the front page only, and the second frame covers the front page, spine and back section. Both frames are slightly larger than the text frames to allow for bleeding edges. Both frames also have "Keep proportions" turned off.

If you want to use the "Keep proportions" feature, then I would suggest that you use the picture frame of the front cover only. You can then use the drawing tools to create a frame for the picture. This will then leave you enough room to enter a title and credit (providing that you do not adjust the size of the picture frame).

If you fill the whole cover, or indeed the whole layout, with a picture, make sure you choose the text correctly. Use a bold typeface set in white, for example, with a black shadow - this will allow you to read the titles.

You can create some wonderful images in Photogenics for use with this template, such as "clouds" (a tutorial in Photogenics is provided) for an ambient tape, "plasma" for an acid tape, or you can "warp" the "plasma" to create images similar to the techno/rave tapes. You can try to emulate the type as well, and I have provided one example: @{"Glowing text" Link Text_FX1}.
@ENDNODE
@NODE T2.4
@{fg highlight}@{u}Wordworth PD@{uu}@{fg text}

	@{u}Template: CV_Display@{uu}

@{u}Introduction@{uu}

This template is a set of title pages for a @{"Curriculum Vitae" Link T1.2} and other information presented in a display book. (The display books that contain plastic sleeves to insert the sheets of information).

@{u}Usage@{uu}

The first page is a contents page, with the user's name, title of the folder, and a text-frame for the contents; just change the text as necessary, and resave the template.

I have provided small pictures (saved in the document) to act as bullet points for the contents, just copy, delete or move these as necessary.

The second page is the headings page, which is a title page for the individual contents. Examples include: references, certificates, the curriculum vitae, etc..

The border and text frame for the headings will appear on every new page. To add more pages, simply click on the page and insert page breaks from the "Insert" menu.

@{u}@{"Fonts" Link Other_Products}@{uu}

Garamond Kursiv Halbfett; 14 and 24 point
@ENDNODE
@NODE A1.0
@{fg highlight}@{u}Wordworth PD@{uu}@{fg text}

	@{u}ARexx: Quick_Convert.Rexx@{uu}

/* Quick Convert v1.0, for Wordworth v4SE by Ryan Morse.
$VER: Quick_Convert_Macro 1.0 (10/12/95)

This script will convert any old or foreign documents, via an open requester, into the new compressed Ww 3.1/4 format - this macro, however, is forward compatible, and, if used in a new version of Wordworth, will support any future enhancements to the file format.

This script should also support any Ww filetypes (Word Perfect, etc.) for loading. Please note that many filetypes are only available in the full (not SE) versions of Wordworth.

The FITWIDTH command has been added in case you have adjusted your display mode or changed the layout of the Wordworth screen. The saved file will appear in the Open Recent window. */

OPEN
FITWIDTH
SAVE
CLOSE
@ENDNODE
@NODE A1.1
@{fg highlight}@{u}Wordworth PD@{uu}@{fg text}

	@{u}ARexx: Text2Frame_Cut.Rexx@{uu}

/* Text 2 Frame Cut v1.0, for Wordworth v5 by Ryan Morse.
$VER: Text2Frame_Cut_Macro 1.0 (10/12/95)

This script converts the selected text into a text frame.

The Cut macro will cut the text from the document, and the Get macro will copy the text from the document. This just determines whether you want to copy the text or not. */

/* Return results to get object id */
Options RESULTS

/* Cut text */
CUT

/* Create text frame */
DRAWTEXTFRAME 1 1.5 1.5 3.0 3.0 0.05 0.05 0.05 0.05 TRANSPARENT 0 BLACK PLAIN NONE
Frame = Result

/* Activate text frame */
ACTIVATETEXTFRAME Frame

/* Paste text in frame */
PASTE
@ENDNODE
@NODE A1.2
@{fg highlight}@{u}Wordworth PD@{uu}@{fg text}

	@{u}ARexx: PGrammar_EXP.Rexx@{uu}

/* Proper Grammar EXPORT v1.01, for Wordworth v4SE by Ryan Morse
$VER: ProperGrammar_Export_Macro 1.0 (10/12/95)

This script will create a temporary document for use in Proper Grammar.
The temporary file is placed in the Wordworth drawer, and can either be deleted after use or left on disk - it will, however, be updated the next time you use this script.

NOTE:  I have included the QUIT command, incase any one wants to quit Wordworth straight away to load Proper Grammar.

These [Proper Grammar] scripts allow the user to keep the style sheets, graphic elements, headers and footers, statistic comments, and other elements, which would otherwise be deleted by Proper Grammar.

NOTE:  Proper Grammar changes the Front and Background Text colours to 40% grey.
All graphic elements and style sheets are lost by Proper Grammar.
All font styles and formatting are, usually, unaffected by Proper Grammar.
Proper Grammar uses the Kindwords 3 library for Wordworth documents.

NOTE:  It is easier and less confusing to copy the body text to a separate file, rather then copying out the graphic elements. This script also by-passes the headers and footers, so, on importing the document back into Wordworth, the user only needs to change the colour of the body text. Wordworth does not support colour changing of text in its command set, preventing full automation!

This script has only been tested with Proper Grammar IIb English.
Advanced users can change these scripts to send the data by the ARexx ports. */

/* Notify user */
REQUESTRESPONSE 'This script will create a temporary file for use in Proper Grammar.'
/* If user cancels requester then stop script */
IF RC>0 THEN DO
	REQUESTNOTIFY 'AREXX MACRO CANCELLED.'
	EXIT
	END

/* Copy body text from Original document */
POSITION SOF
SELECTALL
COPY
/* Save Original document */
SAVE FORCE

/* Create Temporary document */
CLEAR FORCE
PASTE
/* Save Temporary document */
REQUESTNOTIFY 'Saving TEMP.TEXT file in the Wordworth drawer - use this file in PROPER GRAMMAR'
SAVEAS NAME 'TEXT.TEMP'

/* Quit Wordworth to load Proper Grammar - OPTIONAL */
QUIT
@ENDNODE
@NODE A1.3
@{fg highlight}@{u}Wordworth PD@{uu}@{fg text}

	@{u}ARexx: PGrammar_IMP.Rexx@{uu}

/* Proper Grammar IMPORT v1.01, for Wordworth v4SE by Ryan Morse
$VER: ProperGrammar_Import_Macro 1.0 (10/12/95)

This script will convert the TEXT.TEMP Proper Grammar file back to the Wordworth format, with any original elements (graphics/objects, headers and footers). The user, however, will lose any text colour, and tags to the style sheet - this is not my fault!

These [Proper Grammar] scripts allow the user to keep the style sheets, graphic elements, headers and footers, statistic comments, and other elements, which would otherwise be deleted by Proper Grammar.

NOTE:  Proper Grammar changes the Front and Background Text colours to 40% grey.
All graphic elements and style sheets are lost by Proper Grammar.
All font styles and formatting are, usually, unaffected by Proper Grammar.
Proper Grammar uses the Kindwords 3 library for Wordworth documents.

NOTE:  It is easier and less confusing to copy the body text to a separate file, rather then copying out the graphic elements. This script also by-passes the headers and footers, so, on importing the document back into Wordworth, the user only needs to change the colour of the body text. Wordworth does not support colour changing of text in its command set, preventing full automation!

This script has only been tested with Proper Grammar IIb English.
Advanced users can change these scripts to send the data by the ARexx ports. */

/* Notify user */
REQUESTRESPONSE 'This script will convert the TEXT.TEMP Proper Grammar file, back into your 
original Wordworth document.'
/* If user cancels requester then stop script */
IF RC>0 THEN DO
	REQUESTNOTIFY 'AREXX MACRO CANCELLED.'
	EXIT
	END

/* Opening the temporary text file created by PGrammar_EXP_Ww.Rexx */
OPEN FILENAME 'TEXT.TEMP'
/* Ww does not support colour changes in its ARexx command set - change manually */
POSITION SOF
SELECTALL
REQUESTNOTIFY 'IMPORTANT: Reset the TEXT COLOUR (to BLACK and NONE)'
FONT
/* Copying the updated text */
COPY
CLEAR FORCE

/* Load the original Wordworth document */
REQUESTNOTIFY 'Load your ORIGINAL (Pre-Proper Grammar) Wordworth document'
OPEN
/* Paste (new) edited text */
POSITION SOF
SELECTALL
PASTE

/* Notify user and save */
REQUESTRESPONSE 'Your document now contains the UPDATED TEXT with its original elements... 
RESAVING DOCUMENT'
/* If user cancels requester then stop script */
IF RC>0 THEN DO
	REQUESTNOTIFY 'SAVE DENIED.'
	EXIT
	END
SAVE
@ENDNODE
@NODE A1.4
@{fg highlight}@{u}Wordworth PD@{uu}@{fg text}

	@{u}ARexx: AG_Tutorial.Rexx@{uu}

@{fg highlight}@{b}This text file has been changed to prevent MultiView from displaying the codes.@{ub}@{fg text}

@ENDNODE
@NODE A1.5
@{fg highlight}@{u}Wordworth PD@{uu}@{fg text}

	@{u}ARexx: AG_Create_Nodes.Rexx@{uu}

@{fg highlight}@{b}This text file has been changed to prevent MultiView from displaying the codes.@{ub}@{fg text}

/* Create Amiga Guide Nodes v1.01, for Wordworth v4SE by Ryan Morse.
$VER: AmigaGuide_Create_Nodes_Command 1.0 (10/12/95)

This script will create nodes for Amiga Guide documents. Write your document (see the conditions of usage below), and run this script to create the nodes.

USAGE:  For this script to work properly, begin each topic with the word STARTTOPIC, and then write the topic title. Keep these together on a line by themselves. Finish each topic by the word ENDTOPIC, which should also be on a line by itself.

This script works by finding the STARTTOPIC text, and replacing it with the node command. The script then finds the ENDTOPIC text, and replaces it with the end node command. */

/* Notify user */
REQUESTRESPONSE 'This script will change all topics into nodes.'
/* If user cancels requester then stop script */
IF RC>0 THEN DO
	REQUESTNOTIFY 'AREXX MACRO CANCELLED.'
	EXIT
	END

/* Find Start of Topic */
POSITION SOF
FINDCHANGE ALL FIND 'STARTTOPIC' CHANGE '@ NODE'
/* Find End of Topic */
POSITION SOF
FINDCHANGE ALL FIND 'ENDTOPIC' CHANGE '@ ENDNODE'

/* Notify user */
REQUESTNOTIFY 'All topics have now been changed to nodes.'
@ENDNODE
@NODE A1.6
@{fg highlight}@{u}Wordworth PD@{uu}@{fg text}

	@{u}ARexx: AG_Link_Node.Rexx@{uu}

@{fg highlight}@{b}This text file has been changed to prevent MultiView from displaying the codes.@{ub}@{fg text}

/* Create Amiga Guide Links (to Nodes) v1.01, for Wordworth v4SE by Ryan Morse.
$VER: AmigaGuide_Link_Node_Command 1.0 (10/12/95)

This script will create links for Amiga Guide documents. Write your document (see the conditions of usage below), and run this script to create the links.

USAGE:  This script uses the Find requester to create the links. Type the Node that you want to link, then type in the word that will provide the link. The Find requester will then flag each word in turn.

NOTE:  For this script to work properly, write in the full name of the node that you want to link (without the node codes), otherwise the link will not work.

ADVANTAGES:  1) You get to use your favourite word-processor, 2) It avoids repetitive and boring typing, 3) It methodically allows you to find words that need to be linked.

DOWNFALLS:  1) You have to have a clear idea of the text you want to link, 2) It only supports one link - to create more links you have to use this script again, 3) It only selects one word as the link.

NOTE:  I have not used the Find Change command, because you may not want to link every occurrence. This is the best method. */

/* Select Node for Link */
REQUESTRESPONSE PROMPT 'Use the FIND requester to select the NODE for Link. THIS MUST EXIST!'
/* If user cancels requester then stop script */
IF RC>0 THEN DO
	REQUESTNOTIFY 'AREXX MACRO CANCELLED.'
	EXIT
	END
/* Set search parameters */
POSITION SOF
FIND
/* Copy Node name */
COPY

/* Select text for Link (to Node) */
REQUESTRESPONSE PROMPT 'Use the FIND requester to select the TEXT, for Link to the Node. THIS MUST EXIST!'
/* If user cancels requester then stop script */
IF RC>0 THEN DO
	REQUESTNOTIFY 'AREXX MACRO CANCELLED.'
	EXIT
	END
/* Set search parameters */
POSITION SOF
FIND

/* Deselect text at start of word */
CURSOR LEFT
/* Insert Node start */
TEXT '@ {" '
/* Go to end of word */
POSITION EOW
/* Insert Link command */
TEXT '" Link '
/* Paste Node name */
PASTE
/* Inset Node end */
TEXT '} '

/* Notify user */
REQUESTNOTIFY 'Text Link created.'
@ENDNODE
@NODE A1.7
@{fg highlight}@{u}Wordworth PD@{uu}@{fg text}

	@{u}ARexx: AG_Link_Ext_Data.Rexx@{uu}

@{fg highlight}@{b}This text file has been changed to prevent MultiView from displaying the codes.@{ub}@{fg text}

@{b}@{"TEST BUTTON" LINK 
"Wordworth PD #1:Wordworth PD #1/Examples/Ryan.Brush/Main"} link to external picture (on Wordworth PD disk)@{ub}

/* Create Amiga Guide External Data Links v1.01, for Wordworth v4SE by Ryan Morse.
$VER: AmigaGuide_Link_External_Data_Command 1.0 (10/12/95)

This script will create links to external DATA files for Amiga Guide documents.
NOTE:  DATA files are files that MultiView can display or use internally, such as pictures, sound samples, or any other supported and installed datatype.
Select the text to link to an external file, and run this script.

NOTE:  Remember to use the Retrace button to return to MultiView.

NOTE:  If you create an Amiga Guide link to an external file, the path and filename of the link must not be broken by a carriage return. In order to use a Wordworth created Amiga Guide file in MultiView, you have to save the file as ASCII, which may break the path. If your document does suffer from this problem, either insert a carriage return after the link command and before the path, so that the path is unbroken on one line, or change the ASCII preferences (Wordworth "File Settings") to "Line Breaks: LF (Amiga)" and "Save at: End of Paragraph".

These [Amiga Guide] scripts allow you to; 1) apply multiple styles without getting confused by the abundance of codes, 2) use your favourite word-processor, rather than multiple programmes, 3) avoid boring typing and repetition, and 4) allow you to write the guide and then decide which text to link, style, etc., and, if necessary, update easily at a later date. */

/* Notify user */
REQUESTRESPONSE 'This script will link the selected text to an external DATA file.'
/* If user cancels requester then stop script */
IF RC>0 THEN DO
	REQUESTNOTIFY 'AREXX MACRO CANCELLED.'
	EXIT
	END

/* Cut selected text */
CUT
/* Insert start of code */
TEXT '@ {"'
/* Paste text */
PASTE
/* Insert middle of code */
TEXT '" LINK "'
/* Acknowledge result of request file */
Options RESULTS
/* Request file and insert result */
REQUESTFILE TITLE "Create an external DATA link to..." PATH "SYS:"
/* If user cancels requester then stop script */
IF RC>0 THEN DO
	REQUESTNOTIFY 'AREXX MACRO CANCELLED.'
	EXIT
	END
/* Paste result of request file */
TEXT RESULT
/* Insert end of code */
TEXT '/Main"}'
@ENDNODE
@NODE A1.8
@{fg highlight}@{u}Wordworth PD@{uu}@{fg text}

	@{u}ARexx: AG_Highlight.Rexx@{uu}

@{fg highlight}@{b}This text file has been changed to prevent MultiView from displaying the codes.@{ub}@{fg text}

/* Create Amiga Guide Highlight v1.01, for Wordworth v4SE by Ryan Morse.
$VER: AmigaGuide_Highlight_Command 1.0 (10/12/95)

This script will apply a highlight to the selected text for Amiga Guide documents.
Select the text to highlight, and run this script.

These [Amiga Guide] scripts allow you to; 1) apply multiple styles without getting confused by the abundance of codes, 2) use your favourite word-processor, rather than multiple programmes, 3) avoid boring typing and repetition, and 4) allow you to write the guide and then decide which text to link, style, etc., and, if necessary, update easily at a later date.

The codes to highlight text are:
fg = foreground/text colour,
bg = background colour.

The other commands, beside highlight, are:
text, back, shine, shadow, fill, filltext.

To use these codes, just copy this script and change the appropriate insert start of code and insert end of code commands. */

/* Notify user */
REQUESTRESPONSE 'This script will apply a highlight to the selected text.'
/* If user cancels requester then stop script */
IF RC>0 THEN DO
	REQUESTNOTIFY 'AREXX MACRO CANCELLED.'
	EXIT
	END

/* Cut selected text */
CUT
/* Insert code start */
TEXT '@ {fg highlight}'
/* Paste text */
PASTE
/* Insert code end */
TEXT '@ {fg text}'
@ENDNODE
@NODE A1.9
@{fg highlight}@{u}Wordworth PD@{uu}@{fg text}

	@{u}ARexx: AG_Bold.Rexx@{uu}

@{fg highlight}@{b}This text file has been changed to prevent MultiView from displaying the codes.@{ub}@{fg text}

/* Create Amiga Guide Bold Style v1.01, for Wordworth v4SE by Ryan Morse.
$VER: AmigaGuide_Bold_Command 1.0 (10/12/95)

This script will apply a bold style to the selected text for Amiga Guide documents.
Select the text to set in bold, and run this script.

These [Amiga Guide] scripts allow you to; 1) apply multiple styles without getting confused by the abundance of codes, 2) use your favourite word-processor, rather than multiple programmes, 3) avoid boring typing and repetition, and 4) allow you to write the guide and then decide which text to link, style, etc., and, if necessary, update easily at a later date. */

/* Notify user */
REQUESTRESPONSE 'This script will apply a bold style to the selected text.'
/* If user cancels requester then stop script */
IF RC>0 THEN DO
	REQUESTNOTIFY 'AREXX MACRO CANCELLED.'
	EXIT
	END

/* Cut selected text */
CUT
/* Insert start of code */
TEXT '@ {b}'
/* Paste back selected text */
PASTE
/* Insert end of code */
TEXT '@ {ub}'
@ENDNODE
@NODE A2.0
@{fg highlight}@{u}Wordworth PD@{uu}@{fg text}

	@{u}ARexx: AG_Italic.Rexx@{uu}

@{fg highlight}@{b}This text file has been changed to prevent MultiView from displaying the codes.@{ub}@{fg text}

/* Create Amiga Guide Italic Style v1.01, for Wordworth v4SE by Ryan Morse.
$VER: AmigaGuide_Italic_Command 1.0 (10/12/95)

This script will apply an italic style to the selected text for Amiga Guide documents.
Select the text to set in italic, and run this script.

These [Amiga Guide] scripts allow you to; 1) apply multiple styles without getting confused by the abundance of codes, 2) use your favourite word-processor, rather than multiple programmes, 3) avoid boring typing and repetition, and 4) allow you to write the guide and then decide which text to link, style, etc., and, if necessary, update easily at a later date. */

/* Notify user */
REQUESTRESPONSE 'This script will apply an italic style to the selected text.'
/* If user cancels requester then stop script */
IF RC>0 THEN DO
	REQUESTNOTIFY 'AREXX MACRO CANCELLED.'
	EXIT
	END

/* Cut selected text */
CUT
/* Insert start of code */
TEXT '@ {i}'
/* Paste back selected text */
PASTE
/* Insert end of code */
TEXT '@ {ui}'
@ENDNODE
@NODE A2.1
@{fg highlight}@{u}Wordworth PD@{uu}@{fg text}

	@{u}ARexx: AG_Underline.Rexx@{uu}

@{fg highlight}@{b}This text file has been changed to prevent MultiView from displaying the codes.@{ub}@{fg text}

/* Create Amiga Guide Underline Style v1.01, for Wordworth v4SE by Ryan Morse.
$VER: AmigaGuide_Underline_Command 1.0 (10/12/95)

This script will apply an underline style to the selected text for Amiga Guide documents.
Select the text to set in underline, and run this script.

These [Amiga Guide] scripts allow you to; 1) apply multiple styles without getting confused by the abundance of codes, 2) use your favourite word-processor, rather than multiple programmes, 3) avoid boring typing and repetition, and 4) allow you to write the guide and then decide which text to link, style, etc., and, if necessary, update easily at a later date. */

/* Notify user */
REQUESTRESPONSE 'This script will apply an underline style to the selected text.'
/* If user cancels requester then stop script */
IF RC>0 THEN DO
	REQUESTNOTIFY 'AREXX MACRO CANCELLED.'
	EXIT
	END

/* Cut selected text */
CUT
/* Insert start of code */
TEXT '@ {u}'
/* Paste back selected text */
PASTE
/* Insert end of code */
TEXT '@ {uu}'
@ENDNODE
@NODE A2.2
@{fg highlight}@{u}Wordworth PD@{uu}@{fg text}

	@{u}ARexx: PC_Convert.Rexx@{uu}

/* PC (Quick) Convert v1.0, for Wordworth v5 by Ryan Morse.
$VER: PC_(Quick)_Convert_Macro 1.0 (10/12/95)

This script will convert any old or new Wordworth documents, or any other foreign documents, via an open requester, into the Word Perfect file format for use in a PC.

NOTE:  The SaveAs command will pop-up a file requester, to allow you to choose a new destination and rename the file to a standard PC filename (eight characters maximum with a three character suffix).

Please note that many filetypes are only available in the full (not SE) versions of Wordworth.

The saved file will appear in the Open Recent window. */

OPEN
SAVEAS WORDPERFECT
CLOSE
@ENDNODE
@NODE A2.3
@{fg highlight}@{u}Wordworth PD@{uu}@{fg text}

	@{u}ARexx: NEW_Example.Rexx@{uu}

This script was sent to me by Mark Jackson of Digita.

I have included it because it is an excellent example of the RESULT and PORTNAME features incorporated into ARexx.

/* Example ARexx script - Mark Jackson of Digita */
/* We want results of commands returned to us */
Options RESULTS
/* Open a new Wordworth Document window */
NEW
/* Get the ARexx port name for the document */
Portname = RESULT
/* Address the appropriate ARexx port */
ADDRESS VALUE Portname
TEXT 'The ARexx Port Name for this document is ' PORTNAME
@ENDNODE
@NODE A2.4
@{fg highlight}@{u}Wordworth PD@{uu}@{fg text}

	@{u}ARexx: AG_Link_Ext_Prog.Rexx@{uu}

@{b}@{"TEST BUTTON" SYSTEM "SYS:Utilities/Clock"} link to external programme (Clock) on Hard Drive@{ub}

/* Create Amiga Guide External Programme Links v1.01, for Wordworth v4SE by Ryan Morse.
$VER: AmigaGuide_Link_External_Prog_Command 1.0 (10/12/95)

This script will create links to external PROGRAMME files for Amiga Guide documents.
NOTE:  PROGRAMME files are self sufficient programmes.
Select the text to link to an external file, and run this script.

NOTE:   If you create an Amiga Guide link to an external file, the path and filename of the link must not be broken by a carriage return. In order to use a Wordworth created Amiga Guide file in MultiView, you have to save the file as ASCII, which may break the path. If your document does suffer from this problem, either insert a carriage return after the link command and before the path, so that the path is unbroken on one line, or change the ASCII preferences (Wordworth "File Settings") to "Line Breaks: LF (Amiga)" and "Save at: End of Paragraph".

These [Amiga Guide] scripts allow you to; 1) apply multiple styles without getting confused by the abundance of codes, 2) use your favourite word-processor, rather than multiple programmes, 3) avoid boring typing and repetition, and 4) allow you to write the guide and then decide which text to link, style, etc., and, if necessary, update easily at a later date. */

/* Notify user */
REQUESTRESPONSE 'This script will link the selected text to an external PROGRAMME.'
/* If user cancels requester then stop script */
IF RC>0 THEN DO
	REQUESTNOTIFY 'AREXX MACRO CANCELLED.'
	EXIT
	END

/* Cut selected text */
CUT
/* Insert start of code */
TEXT '@ {"'
/* Paste text */
PASTE
/* Insert middle of code */
TEXT '" SYSTEM "'
/* Acknowledge result of request file */
Options RESULTS
/* Request file and insert result */
REQUESTFILE TITLE "Create an external PROGRAMME link to..." PATH "SYS:"
/* If user cancels requester then stop script */
IF RC>0 THEN DO
	REQUESTNOTIFY 'AREXX MACRO CANCELLED.'
	EXIT
	END
/* Paste result of request file */
TEXT RESULT
/* Insert end of code */
TEXT '"}'
@ENDNODE
@NODE A2.5
@{fg highlight}@{u}Wordworth PD@{uu}@{fg text}

	@{u}ARexx: AG_Save_Docs.Rexx@{uu}

/* Save Amiga Guide Documents, v1.01 for Wordworth 5 by Ryan Morse
$VER: Save_AmigaGuide_Documents_Macro 1.0 (22/12/95)

This script will save the Wordworth version and ASCII version of the Amiga Guide documents simultaneously.

NOTE:  Change the DEFAULT filenames to suit your preferences, or, alternatively, delete the file names to pop-up the file requester. The files will be saved in the Wordworth drawer, unless you specify a path or use the file requester.

NOTE:  In order to use a [Wordworth created] Amiga Guide file in MultiView, you have to save the file as ASCII. Make sure that Wordworth's ASCII options ("File Settings") are set to; "Line Breaks: LF (Amiga)" and "Save At: End of Paragraph". This will enable the guide to take advantage of the Wordwrap facility, and thus format the text properly on any Amiga resolution.

These [Amiga Guide] scripts allow you to; 1) apply multiple styles without getting confused by the abundance of codes, 2) use your favourite word-processor, rather than multiple programmes, 3) avoid boring typing and repetition, and 4) allow you to write the guide and then decide which text to link, style, etc., and, if necessary, update easily at a later date. */

/* Notify user */
REQUESTRESPONSE 'This will save the appropriate Amiga Guide documents.'
/* If user cancels requester then stop script */
IF RC>0 THEN DO
	REQUESTNOTIFY 'AREXX MACRO CANCELLED.'
	EXIT
	END

/* Save Wordworth file */
REQUESTNOTIFY 'Saving Wordworth document.'
SAVEAS NAME 'WordworthPD.Ww'

/* Save ASCII version */
REQUESTNOTIFY 'Saving Amiga Guide (ASCII) document.'
SAVEAS ASCII NAME 'WordworthPD.Guide'
@ENDNODE
@NODE A2.6
@{fg highlight}@{u}Wordworth PD@{uu}@{fg text}

	@{u}ARexx: AG_Convert_WB2.Rexx@{uu}

@{fg highlight}@{b}This text file has been changed to prevent MultiView from displaying the codes.@{ub}@{fg text}

/* Amiga Guide Convert for WB2 v1.0, for Wordworth v5 by Ryan Morse.
$VER: AmigaGuide_Convert_for_WB2 1.0 (10/1/96)

This script will convert a Workbench 3 Amiga Guide document for Workbench 2.

This script works by finding commands that are incompatible with WB 2, and removes them. This is useful for users who have used Wordworth to create a guide file (using features such as Wordwrap), and want to create another version for WB 2 users.

NOTE:  A template "Amiga_Guide_OS2" has been provided for WB 2 authors, which also provides a link to an Index page to compensate for the lack of support for the Index node.

USAGE:  Write or update the WB 3 guide, and save it using the "AG_Save_Docs" ARexx script, and then run this script to convert the guide and save a new guide for WB 2 users.

I only have a WB 3 machine and am not sure what features have to be deleted for WB 2 users. I have, however, looked at programmes which perform a similar function as this script, and these delete the following: WORDWRAP node, INDEX node, FONT node. Some of these programs also delete styles, although this is not necessary. I have included a feature to delete these styles, (except for highlight styles). I have based this script on "AGuideConv" by Michael Friedrich (v1.0 © 1994).

This script is very similar to "AGuideConv" in that it: 1) operates on the file in memory (you are working on the file in Wordworth), 2) it uses a set text width (please refer to the WB 2 Amiga Guides notes in the Wordworth PD guide), BUT 3) it allows the user to save the file under a different name. 

NOTE:  The longer your document is, the longer this script will take to work... But, unlike other programs, YOU CAN CONFIGURE THIS SCRIPT TO SUIT YOUR NEEDS. */

/* Notify user */
REQUESTRESPONSE 'This script will convert the current Amiga Guide for WB 2.'
/* If user cancels requester then stop script */
IF RC>0 THEN DO
	REQUESTNOTIFY 'AREXX MACRO CANCELLED.'
	EXIT
	END

/* DELETE ALL WB 2 INCOMPATIBLE NODES */
/* Find and delete Wordwrap node */
POSITION SOF
FINDCHANGE FIND '@ WORDWRAP' CHANGE ''
/* Select and delete whole line */
POSITION SOL
/* Select line */
SHIFTDOWN; CURSOR DOWN SHIFTDOWN
/* Notify user */
REQUESTRESPONSE 'Deleted WORDWRAP command. Delete rest of line?'
IF RC=0 THEN DO
	CUT
	END

/* Find and delete Index node */
POSITION SOF
FINDCHANGE FIND '@ INDEX' CHANGE
/* Select and delete whole line */
POSITION SOL
/* Select line */
SHIFTDOWN; CURSOR DOWN SHIFTDOWN
/* Notify user */
REQUESTRESPONSE 'Deleted INDEX command. Delete rest of line?'
IF RC=0 THEN DO
	CUT
	END

/* Find and delete Font node */
POSITION SOF
FINDCHANGE FIND '@ FONT' CHANGE ''
/* Select and delete whole line */
POSITION SOL
/* Select line */
SHIFTDOWN; CURSOR DOWN SHIFTDOWN
/* Notify user */
REQUESTRESPONSE 'Deleted FONT command. Delete rest of line?'
IF RC=0 THEN DO
	CUT
	END

/* DELETE ALL STYLES */
/* Notify user */
REQUESTRESPONSE 'All WB 2 incompatible codes have been deleted. Delete all styles?'
/* If user cancels requester then stop script */
IF RC>0 THEN DO
	REQUESTNOTIFY 'No styles deleted. SAVE the WB 2 guide.'
	/* SAVE WB 2 GUIDE */
	/* The SAVEAS command will produce a requester to rename the guide */
	SAVEAS ASCII
	EXIT
	END

/* DELETE ALL STYLES */
/* Find and delete all ITALIC style codes */
REQUESTNOTIFY 'Deleting all Italic styles.'
POSITION SOF
FINDCHANGE ALL FIND '@ {i}' CHANGE ''
/* Find and delete all END of ITALIC style codes */
POSITION SOF
FINDCHANGE ALL FIND '@ {ui}' CHANGE ''

/* Find and delete all BOLD style codes */
REQUESTNOTIFY 'Deleting all Bold styles.'
POSITION SOF
FINDCHANGE ALL FIND '@ {b}' CHANGE ''
/* Find and delete all END of BOLD style codes */
POSITION SOF
FINDCHANGE ALL FIND '@ {ub}' CHANGE ''

/* Find and delete all UNDERLINE style codes */
REQUESTNOTIFY 'Deleting all Underline styles.'
POSITION SOF
FINDCHANGE ALL FIND '@ {u}' CHANGE ''
/* Find and delete all END of UNDERLINE style codes */
POSITION SOF
FINDCHANGE ALL FIND '@ {uu}' CHANGE ''

/* Notify user of changes */
REQUESTNOTIFY 'All styles have been deleted, now SAVE the WB 2 guide.'

/* SAVE WB 2 GUIDE */
/* The SAVEAS command will produce a requester to rename the guide */
SAVEAS ASCII
@ENDNODE
@NODE A2.7
@{fg highlight}@{u}Wordworth PD@{uu}@{fg text}

	@{u}ARexx: AG_Strip.Rexx@{uu}

@{fg highlight}@{b}This text file has been changed to prevent MultiView from displaying the codes.@{ub}@{fg text}

/* Strip Amiga Guide to Text v1.0, for Wordworth v4SE by Ryan Morse.
$VER: Strip_Amiga_Guide_to_Text 1.0 (11/1/96)

This script will strip an Amiga Guide file to plain text.

NOTE: I have only included the Amiga Guide commands that I have presently written scripts for. This script can easily be changed to accommodate for more or different commands.

NOTE: There are still a few problems with this script; 1) Be careful of the find and replace command for the word SYSTEM - the find ARexx command is not case sensitive and it will delete ALL 'system' words that it finds. 2) It does not delete path links or other information in brackets {}. 3) The longer your document is, the longer you wait.

NOTE: I may update this script to convert Amiga Guide italic styles, etc., to Wordworth italic styles. */

/* Notify user */
REQUESTRESPONSE 'This script will strip the current Amiga Guide to plain text.'
/* If user cancels requester then stop script */
IF RC>0 THEN DO
	REQUESTNOTIFY 'AREXX MACRO CANCELLED.'
	EXIT
	END

/* Find and delete Database node */
POSITION SOF
FINDCHANGE FIND '@ DATABASE' CHANGE ''
/* Select and delete whole line */
POSITION SOL
/* Select line */
SHIFTDOWN; CURSOR DOWN SHIFTDOWN
/* Notify user */
REQUESTRESPONSE 'Deleted Database command. Delete rest of line?'
IF RC=0 THEN DO
	CUT
	END

/* Find and delete Author node */
POSITION SOF
FINDCHANGE FIND '@ AUTHOR' CHANGE ''
/* Select and delete whole line */
POSITION SOL
/* Select line */
SHIFTDOWN; CURSOR DOWN SHIFTDOWN
/* Notify user */
REQUESTRESPONSE 'Deleted AUTHOR command. Delete rest of line?'
IF RC=0 THEN DO
	CUT
	END

/* Find and delete Copyright node */
POSITION SOF
FINDCHANGE FIND '@ (c)' CHANGE ''
/* Select and delete whole line */
POSITION SOL
/* Select line */
SHIFTDOWN; CURSOR DOWN SHIFTDOWN
/* Notify user */
REQUESTRESPONSE 'Deleted COPYRIGHT command. Delete rest of line?'
IF RC=0 THEN DO
	CUT
	END

/* Find and delete Version node */
POSITION SOF
FINDCHANGE FIND '@ $VER:' CHANGE ''
/* Select and delete whole line */
POSITION SOL
/* Select line */
SHIFTDOWN; CURSOR DOWN SHIFTDOWN
/* Notify user */
REQUESTRESPONSE 'Deleted VERSION command. Delete rest of line?'
IF RC=0 THEN DO
	CUT
	END

/* Find and delete Master node */
POSITION SOF
FINDCHANGE FIND '@ MASTER' CHANGE ''
/* Select and delete whole line */
POSITION SOL
/* Select line */
SHIFTDOWN; CURSOR DOWN SHIFTDOWN
/* Notify user */
REQUESTRESPONSE 'Deleted MASTER command. Delete rest of line?'
IF RC=0 THEN DO
	CUT
	END

/* Find and delete Index node */
POSITION SOF
FINDCHANGE FIND '@ INDEX' CHANGE
/* Select and delete whole line */
POSITION SOL
/* Select line */
SHIFTDOWN; CURSOR DOWN SHIFTDOWN
/* Notify user */
REQUESTRESPONSE 'Deleted INDEX command. Delete rest of line?'
IF RC=0 THEN DO
	CUT
	END

/* Find and delete Font node */
POSITION SOF
FINDCHANGE FIND '@ FONT' CHANGE ''
/* Select and delete whole line */
POSITION SOL
/* Select line */
SHIFTDOWN; CURSOR DOWN SHIFTDOWN
/* Notify user */
REQUESTRESPONSE 'Deleted FONT command. Delete rest of line?'
IF RC=0 THEN DO
	CUT
	END

/* Find and delete Wordwrap node */
POSITION SOF
FINDCHANGE FIND '@ WORDWRAP' CHANGE ''
/* Select and delete whole line */
POSITION SOL
/* Select line */
SHIFTDOWN; CURSOR DOWN SHIFTDOWN
/* Notify user */
REQUESTRESPONSE 'Deleted WORDWRAP command. Delete rest of line?'
IF RC=0 THEN DO
	CUT
	END

/* Find and delete Remark node */
POSITION SOF
FINDCHANGE FIND '@ REMARK' CHANGE ''
/* Select and delete whole line */
POSITION SOL
/* Select line */
SHIFTDOWN; CURSOR DOWN SHIFTDOWN
/* Notify user */
REQUESTRESPONSE 'Deleted REMARK command. Delete rest of line?'
IF RC=0 THEN DO
	CUT
	END

/* Find and delete all of Ryan's Topic codes */
POSITION SOF
FINDCHANGE ALL FIND 'STARTTOPIC' CHANGE ''
POSITION SOF
FINDCHANGE ALL FIND 'ENDTOPIC' CHANGE ''

/* Find and delete all of node codes */
POSITION SOF
FINDCHANGE ALL FIND '@ NODE' CHANGE ''
POSITION SOF
FINDCHANGE ALL FIND '@ ENDNODE' CHANGE ''

/* Find and delete all highlight style codes */
POSITION SOF
FINDCHANGE ALL FIND '@ {fg highlight}' CHANGE ''
POSITION SOF
FINDCHANGE ALL FIND '@ {fg text}' CHANGE ''

/* Find and delete all ITALIC style codes */
POSITION SOF
FINDCHANGE ALL FIND '@ {i}' CHANGE ''
/* Find and delete all END of ITALIC style codes */
POSITION SOF
FINDCHANGE ALL FIND '@ {ui}' CHANGE ''

/* Find and delete all BOLD style codes */
POSITION SOF
FINDCHANGE ALL FIND '@ {b}' CHANGE ''
/* Find and delete all END of BOLD style codes */
POSITION SOF
FINDCHANGE ALL FIND '@ {ub}' CHANGE ''

/* Find and delete all UNDERLINE style codes */
POSITION SOF
FINDCHANGE ALL FIND '@ {u}' CHANGE ''
/* Find and delete all END of UNDERLINE style codes */
POSITION SOF
FINDCHANGE ALL FIND '@ {uu}' CHANGE ''

/* Find and delete all link codes */
POSITION SOF
FINDCHANGE ALL FIND 'Link' CHANGE ''

/* Find and delete all System link codes */
POSITION SOF
FINDCHANGE ALL FIND 'SYSTEM' CHANGE ''

/* Find and delete all other codes */
POSITION SOF
FINDCHANGE ALL FIND '@ {' CHANGE ''
FINDCHANGE ALL FIND '}' CHANGE ''

/* Notify user of changes */
REQUESTNOTIFY 'All Amiga Guide codes have been stripped.'
@ENDNODE
@NODE A2.8
@{fg highlight}@{u}Wordworth PD@{uu}@{fg text}

	@{u}ARexx: Proper_Grammer_EXP_2.Rexx@{uu}

/* Proper Grammar EXPORT v2.0, for Wordworth v4SE by Ryan Morse
$VER: ProperGrammar_Export_Macro 2.0 (28/1/96)

NOTE: Version 2 differs from version 1, in that it creates a work-area allowing the user to keep the original document open. The original script is better suited to users with low memory machines.

This script will create a temporary document for use in Proper Grammar.
The temporary file is placed in the Wordworth drawer, and can either be deleted after use or 
left on disk - it will, however, be updated the next time you use this script.

NOTE: I have included the QUIT command, incase any one wants to quit Wordworth straight away to load Proper Grammar.

These [Proper Grammar] scripts allow the user to keep the style sheets, graphic elements, headers and footers, statistic comments, and other elements, which would otherwise be deleted by Proper Grammar.

NOTE: Proper Grammar changes the Front and Background Text colours to 40% grey.
All graphic elements and tags to styles are deleted by Proper Grammar.
All font styles and formatting are, usually, unaffected by Proper Grammar.
Proper Grammar uses the Kindwords 3 library for Wordworth documents.

NOTE: It is easier and less confusing to copy the body text to a separate file, rather then copying out the graphic elements. This script also by-passes the headers and footers, so, on importing the document back into Wordworth, the user only needs to change the colour of the body text. Wordworth does not support colour changing of text in its command set, preventing full automation!

This script has only been tested with Proper Grammar IIb English. */

/* Notify user */
REQUESTRESPONSE 'This script will create a temporary file for use in Proper Grammar.'
/* If user cancels requester then stop script */
IF RC>0 THEN DO
	REQUESTNOTIFY 'AREXX MACRO CANCELLED.'
	EXIT
	END

/* Copy body text from Original document */
POSITION SOF
SELECTALL
COPY
/* Save Original document */
SAVE FORCE

/* NEW DOCUMENT */
/* Return results to obtain portname */
Options RESULTS
/* Create new document */
NEW
Portname = RESULT
/* Address new document */
ADDRESS VALUE Portname

/* Insert text in new document */
PASTE

/* Save Temporary document */
REQUESTNOTIFY 'Saving TEMP.TEXT file in the Wordworth drawer - use this file in PROPER 
GRAMMAR'
SAVEAS NAME 'TEXT.TEMP'

/* Quit Wordworth to load Proper Grammar - OPTIONAL */
QUIT
@ENDNODE
@NODE A2.9
@{fg highlight}@{u}Wordworth PD@{uu}@{fg text}

	@{u}ARexx: Proper_Grammer_IMP_2.Rexx@{uu}

/* Proper Grammar IMPORT v2.0, for Wordworth v4SE by Ryan Morse
$VER: ProperGrammar_Import_Macro 2.0 (28/1/96)

NOTE: Version 2 differs from version 1, in that it creates a new work-area rather than using the current document. This is a better method in case the user is working on a document and does not know what is happening, and will inevitably lose the document. (The old script cleared the current work area, destroying any work present in it.)

This script will convert the TEXT.TEMP Proper Grammar file back to the Wordworth format, with its original elements (graphic objects, headers and footers, etc.). The user, however, will lose any text colour, and tags to styles - this is not my fault!

These [Proper Grammar] scripts allow the user to keep the style sheets, graphic elements, headers and footers, statistic comments, and other elements, which would otherwise be deleted by Proper Grammar.

NOTE: Proper Grammar changes the Front and Background Text colours to 40% grey.
All graphic elements and tags to styles are deleted by Proper Grammar.
All font styles and formatting are, usually, unaffected by Proper Grammar.
Proper Grammar uses the Kindwords 3 library for Wordworth documents.

NOTE: It is easier and less confusing to copy the body text to a separate file, rather then copying out the graphic elements. This script also by-passes the headers and footers, so, on importing the document back into Wordworth, the user only needs to change the colour of the body text. Wordworth does not support colour changing of text in its command set, preventing full automation!

This script has only been tested with Proper Grammar IIb English. */

/* Notify user */
REQUESTRESPONSE 'This script will convert TEXT.TEMP Proper Grammar file, back for Wordworth.'
/* If user cancels requester then stop script */
IF RC>0 THEN DO
	REQUESTNOTIFY 'AREXX MACRO CANCELLED.'
	EXIT
	END

/* NEW DOCUMENT */
/* Return results to obtain portname */
Options RESULTS
/* Create new document */
NEW
Portname = RESULT
/* Address new document */
ADDRESS VALUE Portname

/* Opening the temporary text file created by PGrammar_EXP_Ww.Rexx in new document */
OPEN FILENAME 'TEXT.TEMP'
/* Ww does not support colour changes in its ARexx command set - change manually */
POSITION SOF
SELECTALL
REQUESTNOTIFY 'IMPORTANT: Reset the TEXT COLOUR (to BLACK and NONE)'
FONT
/* Copying the updated text */
COPY
CLEAR FORCE

/* Load the original Wordworth document in work-area */
REQUESTNOTIFY 'Load your ORIGINAL (Pre-Proper Grammar) Wordworth document'
OPEN
/* If user selects cancel the work-area will be used */
/* Paste (new) edited text */
POSITION SOF
SELECTALL
PASTE

/* Notify user and save */
REQUESTRESPONSE 'Your document is now updated. RESAVING DOCUMENT.'
/* If user cancels requester then stop script */
IF RC>0 THEN DO
	REQUESTNOTIFY 'SAVE DENIED.'
	EXIT
	END
/* Save doument */
SAVE
@ENDNODE
@NODE A3.0
@{fg highlight}@{u}Wordworth PD@{uu}@{fg text}

	@{u}ARexx: Text2Frame_Get.Rexx@{uu}

/* Text 2 Frame Get v1.0, for Wordworth v5 by Ryan Morse.
$VER: Text2Frame_Get_Macro 1.0 (10/12/95)

This script converts the selected text into a text frame.

The Cut macro will cut the text from the document, and the Get macro will copy the text from the document. This just determines whether you want to copy the text or not. */

/* Return results to get object id */
Options RESULTS

/* Get text */
GETTEXT
TextReturn = RESULT

/* Create text frame */
DRAWTEXTFRAME 1 1.5 1.5 3.0 3.0 0.05 0.05 0.05 0.05 TRANSPARENT 0 BLACK PLAIN NONE
Frame = Result

/* Activate text frame */
ACTIVATETEXTFRAME Frame

/* Insert text in frame */
TEXT TextReturn
@ENDNODE
@NODE Ww_Comp "Wordworth Compatibility"
@{fg highlight}@{u}Wordworth PD@{uu}@{fg text}

	@{u}Wordworth Compatibility@{uu}

The last time I checked, Wordworth 3.x/4 files (documents and templates) are still compatible with older versions of Wordworth - that is, they can be loaded. Wordworth 2 users will just need to change the text and background colours to black and none (white) respectively. This is relatively simple, due to the palette in the toolbar. Just remember to use the select all command beforehand.

Please note that older versions of Wordworth lack many of the current features, and the programme will make the necessary changes. For instance, True Type fonts should be converted to the default font. Tables and structured drawings should be deleted, and so on and so forth. I have not checked backward compatibility since version 3.1.

The following ARexx macros will automatically convert your files to different formats, please click on the buttons to obtain a full description of what they actually do:

 @{" Quick Convert            " Link A1.0} To convert files to the new Ww format.
 @{" PC Convert               " Link A2.2} To covert files for PC/Word Perfect @{b}Ww 5@{ub}.

Wordworth (all versions I know) are still compatible with Proper Grammar; Proper Grammar uses the Kindwords 3 library for Wordworth documents. Proper Grammar changes the Front and Background Text colours to 40% grey (on reloading to Wordworth), and deletes all style sheets and graphic elements. All font styles and formatting are unaffected by Proper Grammar. Two scripts have been provided to reduce these problems:

 @{" Proper Grammar Export    " Link A1.2} To export documents for Proper Grammar.
 @{" Proper Grammar Import    " Link A1.3} To import documents back to Wordworth.
 @{" Proper Grammar Export 2  " Link A2.8} To export documents for Proper Grammar.
 @{" Proper Grammar Import 2  " Link A2.9} To import documents back to Wordworth.

These scripts effectively copy out the body text for use in Proper Grammar - by doing so it means that the headers and footers are unaffected, all graphic objects remain, and, what is more important, the style sheets are not deleted (although the tags to your document are). This is the best solution and requires very little work from the user. I would, however, like to see Digita write or licence a grammar checker for a future version of Wordworth.

As a last note, owners of Proper Grammar can use this programme to convert documents to and from the Wordworth and Proper Grammar/Final Copy/Final Writer file formats. This method is far superior than using the ASCII file format to transfer information between these packages, although many elements of the layout (such as objects) will be lost. This is useful for people who have changed word-processors.
@ENDNODE
@NODE Sections "Sections"
@{fg highlight}@{u}Wordworth PD@{uu}@{fg text}

	@{u}Sections@{uu}

At the time of writing, Wordworth 4SE still lacks sections. I will give you an example of how I work around this problem.

For the final major project of my previous course, the report was marked on many of my subjects; Technical studies (estimating), Business and Management studies, German Language and Design studies. Now many people like to add title pages to their documents, but due to the lack of sections, Wordworth counts this as the first page. It is possible to exclude the headers and footers from the first page, but not the page count. Once I had decided on the layout of my design (the overall dimensions of the pages, the font styles and types, columns, etc.), I created a separate document as the title page. This allowed me to exclude all page numbers, and also offer me greater flexibility; the title page contained a heavy use of graphics, and containing these to one page, gave me a faster loading time and the memory to print the document.

Similarly, I did not want the contents pages to be included with the page count, I wanted them to have their own numbers. I created a separate document, and used the page numbering style ("Document Settings: Options") to use a different style.

For the body text I created a series of different layouts, on paper, to accommodate for text, text with graphics, lists, columns and so on. Wordworth does not support multiple columns of different widths on a page, so I made extensive use of the text frames. I used an average of eight layouts in my report, encompassing all of the different layouts outlined above. Text frames are actually objects and thus require more memory for printing, creating several documents at once allowed me to print the whole project without running out of memory (although I did come close).

The finished project filled over one hundred pages, which all had to be trimmed, and took over eight hours to print. I drew in the trim/crop marks by myself, and used the copy to all pages feature. As I mentioned in the @{"introduction" Link Author}, the teachers only see the end result.
@ENDNODE
@NODE Graphics_1 "Graphics #1"
@{fg highlight}@{u}Wordworth PD@{uu}@{fg text}

	@{u}Graphics 1@{uu}

If you examine the objects in the news letter templates, you will see a first hand method of creating and working with graphics in Wordworth. Recent versions of Wordworth allow structured drawings to be imported into documents, but many users either lack the software to create their own drawings, or lack the clip art to use in their documents. But how many people have actually tried incorporating a structured drawing and bitmap picture together... Try this example:

Convert the "Earth.iff" picture (provided free with Wordworth 3.x and up) to greyscale (grey pictures offer greater definition, and print better, etc.).

Draw a picture frame using these co-ordinates (in cm); Left 9.15, Top 14.20, Width 2.80, Height 2.80; Keep proportions; Colour 0 transparent; and load the "Earth.iff" picture.

Draw a (structured drawing of a) circle, over the Earth picture, at these co-ordinates (in cm); Left 9.12, Top 14.20, Diameter 2.75; Fill: transparent; Border: 20% grey; 2pt thickness.

The (structured drawing of a) circle will now overlap the Earth picture on screen and when it is printed. This will effectively hide the jagged edges and make the Earth picture look round. The colour and thickness of the circle will also make the Earth look as if it has a wonderful hazy atmosphere.

Now draw a text effect over the other two elements, at these co-ordinates (in cm); Left 8.10, Top 13.2, Width 4.80, Height 4.80; Type: circle; pre-sets: none; Text "The European Tour - " (with spaces, but no quotation marks).

Group all of these elements together and copy them. Create a new document using the @{"Monitor Newsletter" Link T1.7} template, and delete the middle top text frame (not the one for the reversed-out text), now select paste and the graphic elements should drop perfectly in place providing you with another design for that template.

I have many other graphic tips and not enough time or space, please rip apart the templates to gain a better understanding.

MANY M*cintosh and PC applications (Illustr*tor, P*inter, etc.) support the successful integration of bitmap and vector graphics, and this is one major feature that is lacking in Amiga graphic programmes. The Amiga also has a gap in the market for a budget structured drawing programme; the only two options available are still out of the reach of many Amiga users... Pagestream has Art Expression built in (I do not and can not verify this as my information is dependant on magazine reviews), and ProVector is too expensive for the hobbyist and student (as a comparison you can buy C*ral Dr*w, for the PC, for under £50). Design Works, however, will probably fill this gap, and is currently being updated. I have written and asked Digita to produce a budget structured drawing programme, but I am just one voice. If you want such a programme, and would buy and use it, then please let Digita know. I have to admit that I am spoiled by the HIP way of working, and I can not get to grips with the out-dated and obsolete structured drawing programmes I currently own (all from magazine coverdisks). I am also interested in Almathera creating a structured drawing programme, and how well they can implement this with Photogenics.
@ENDNODE
@NODE Text_FX1 "Text Effects #1"
@{fg highlight}@{u}Wordworth PD@{uu}@{fg text}

	@{u}Text Effects 1: Glowing Text@{uu}

This is an extension of the @{"Graphic 1" Link Graphics_1} tutorial, in that it is an example of combining vector and bitmap work. This example is only really relevant if you are using Wordworth to create a graphic oriented document (i.e. a leaflet, poster, etc.), it is also very effective with the @{"Picture Frame" Link T2.0} template.

NOTE:  This example uses Photogenics, which is supplied with Wordworth 4SE in the Amiga Magic Pack.

This effectively creates a glow around text:

1. Choose a heading font, particularly one that is bold and big.
2. Convert the font via Fountain or Intellifont for use in Workbench.
3. Load this font (at the same size as that of your doucument) in Photogenics, and type in the text of the heading (see number 1).
4. Add a guasian blur of 6 intensity to the type.
5. Save the file (as an ILBM for Ww4SE, or a 24-Bit format for Ww5) and reload Wordworth.
6. Import the type/picture and place it over the background graphic. Select the options "Keep Proportions", and "Colour 0 Transparent"

NOTE:  You may have to adjust the background colour of the text graphic file in Photogenics or Personal Paint, also included in the Amiga Magic pack, so that it becomes colour 0 for transparency in Wordworth.

7. Type the heading in a text frame and position it over the text graphic.
8. Resize the text graphic so that it is correctly sized to the heading.

The glow can also be changed, via Photogenics, to any colour you want. Try using the Futura Bold typeface, and type 'FIRE'; change the glow to red, and the font in Wordworth to yellow. There are more effective ways of creating this effect, but this method is best suited to the limitations of Photogenics and Wordworth.

This example displays how you can combine vector graphics with bitmap graphics and create effects in Wordworth that were otherwise impossible.

MANY M*cintosh and PC applications (Illustr*tor, P*inter, etc.) support the successful integration of bitmap and vector graphics, and this is one major feature that is lacking in Amiga graphic programmes. The Amiga also has a gap in the market for a budget structured drawing programme; the only two options available are still out of the reach of many Amiga users... Pagestream has Art Expression built in (I do not and can not verify this as my information is dependant on magazine reviews), and ProVector is too expensive for the hobbyist and student (as a comparison you can buy C*ral Dr*w, for the PC, for under £50). Design Works, however, will probably fill this gap, and is currently being updated. I have written and asked Digita to produce a budget structured drawing programme, but I am just one voice. If you want such a programme, and would buy and use it, then please let Digita know. I have to admit that I am spoiled by the HIP way of working, and I can not get to grips with the out-dated and obsolete structured drawing programmes I currently own (all from magazine coverdisks). I am also interested in Almathera creating a structured drawing programme, and how well they can implement this with Photogenics.
@ENDNODE
@NODE Text_Flow1 "Text Flow"
@{fg highlight}@{u}Wordworth PD@{uu}@{fg text}

	@{u}Text Flow 1: Flow text around both sides of an object@{uu}

@{fg highlight}An example document is provided on disk.@{fg text}

@{u}Single column grid@{uu}

NOTE:  This method is far from perfect, and you should check the example file before wasting your time. Print the example to see the results before you abandon this method altogether.

This method requires the most work:

Place your picture/object, and position it on the page. Draw two text frames that start at the top of the picture and end at the bottom of the picture. The first frame should start at the left margin and end at the centre of the object, and the second frame should start from the centre of the object and end at the right margin. Set the margins to none. Check to see what line of text is affected by the flow, and reposition the top of the text frame at the line of text above the affected line. You can either use co-ordinates to position the frame or; 1) copy the line of text under the text frame, and 2) paste it in the text frame, so that the line is duplicated. Now, 3) move the text frame until both sentences match up correctly (the text will be the same). Do the same for the bottom of the text frame. (Then delete that line of text from under the text frame.)

If you want a straight flow:

Draw another text frame directly over the graphic element, and set the stand off to the right. Then set the stand off for the graphic element to the left.

If you want a contour flow:

Copy the object and set the original stand off to the left, and the stand off of the original to the right. If it is a picture, and duplicating the image will use too much memory, then you will have to identify the main sections of image (the straights, diagonals and curves) and draw in the equivalents (by the structured drawing tools) to provide the text flow on the other side. Remember to select the fill as transparent, and send the hairlines to the back - behind the image so that they will not appear in the print out, and also try to minimise the amount of drawings.

NOTE:  You can not achieve a contour flow using drawings if you group them together, Wordworth will find the furthest points and create an invisible box around the grouped objects, causing a straight flow.

Now select the text from under the text frames and drag and drop it into the first text frame. This should cause the other text on the page to move up under the text frames, so use carriage returns to position it back past the text frames. This now leads on to the hard bit... You have to see where the text flows, and drag and drop the flowed part of the sentence into the right text frame. If you drag too much and cause a flow in the right text frame, then move some text back until it fills only one line in the frame. Repeat this until the text reads properly from left to right.

NOTE:  For this to work properly, you may to change the formatting of your text, use carriage returns for each line, and insert extra spaces before or after the line of text.

NOTE:  The quickest way of working out which text to move, is to drop it all in the first text frame. Now select @{b}all@{ub} the text starting from the flow and drop it all in the second text frame, and repeat this stage over and over again until it is complete.

@{u}Multiple column grids@{uu}

Not very many people know this, but Wordworth can flow text around both sides of an object. The only official way to do this, however, is to use multiple columns on a page. Place a picture (this does not seem to work on CGM files), in the gutter, so that the graphic image enters both the left and right columns, and set the stand off (it does not matter whether you choose left or right for the flow). The text should flow perfectly around the image. To see the text flow at its best, use a contour flow with a 5 point stand off, and set the text to full justified.

NOTE:  You may have to reformat the document to make the text flow properly after loading, just Select All and click on Paragraph (Format menu) or Document (Format menu) and then on OK.

NOTE:  The only CGM files I own were included with Wordworth, and, as such, I am unable to fully test them. I am also unable to test EPS files, because they are not supported by Wordworth 4SE.

@{u}Double page spreads@{uu}

NOTE:  If you are using multiple columns then please refer to the "Multiple column grid".

NOTE:  If you are using a single column grid, and the object is placed on one page only, then please refer to the "Single column grid".

If you are using a single column grid, and want to flow text around an object in the centre of the spread, use these methods:

If you want a straight flow:

Draw a text frame to the same size as the object, and position it precisely over the object. Next, set the stand off of the object to the left, and the stand off of the text frame to the right.

If you want a contour flow:

The easiest method is to copy the object and position them precisely over each other. Set the stand off of the original to the right, and set the stand off of the copy to the left. If it is a picture, and duplicating the image will use too much memory, then you will have to identify the main sections of image (the straights, diagonals and curves) and draw in the equivalents (by the structured drawing tools) to provide the text flow on the other side. Remember to select the fill as transparent, and send the hairlines to the back - behind the image so that they will not appear in the print out, and also try to minimise the amount of drawings.

NOTE:  You can not achieve a contour flow using drawings if you group them together, Wordworth will find the furthest points and create an invisible box around the grouped objects, causing a straight flow.

@{fg highlight}NOTE:  It is always best if you just copy a picture to achieve a contour flow, rather than using drawings to create the other flow. Creating drawings is very time consuming and 90 per cent of the time will get flawed results. If you do suffer from memory problems, separate this page from the others be using my @{"sections" Link Sections} tip.@{fg text}
@ENDNODE
@NODE Measurements "Measurements"
@{fg highlight}@{u}Wordworth PD@{uu}@{fg text}

	@{u}Measurements@{uu}

The measurement settings in Wordworth 3.0 and above, are found in "View Settings" and can be changed to inches, centimetres, millimetres, points or picas. You can place the icon for "View Settings" in your toolbar, so you can easily change the measurement unit whilst working in Wordworth.

If, however, you need to position an object (a picture, text frame, or drawing, etc.) at a specific location, and need to use a different measurement unit (i.e. you are working in inches but need to position an object precise to centimetres), rather than changing the measurement unit of the document, open up the "Information" requester of the object. Type in the new position, followed (without any spaces) by the abbreviation of the measurement unit you need.

NOTE:  Make sure that there are no spaces between the position and abbreviation.

Press return or the tab key, and Wordworth will reposition the object and automatically convert the position, of the measurement unit you typed in, to the measurement unit of the document.

Example:  If you are working in inches, and type in (in the object's "Information" requester) "From Left: 1.0cm" (no spaces between the position and abbreviation), Wordworth will position the object one centimetre from the left of the page, and convert the centimetre figure into the inch equivalent (which is 0.39 inches).

@{b}The abbreviations are:@{ub}

  Inches = in
  Centimetres = cm
  Millimetres = mm
  Points = pt
  Picas = pc
@ENDNODE
@NODE Insert "Insert"
@{fg highlight}@{u}Wordworth PD@{uu}@{fg text}

	@{u}Insert@{uu}

Wordworth 3.0 and above has the ability to Insert certain codes straight into a document, such as; updating times, page numbers, and, amongst others, page count. Many of these can not be inserted straight into a text frame, although many operate correctly if you drag and drop text edit them into a text frame - the template; @{"Assignment.GBC" Link T1.1} is one such example of this ability. This is a very useful tip, especially if, for example, you want to add a page number in a margin, over graphic elements, and so on.

Some Insert commands, however, will not work correctly in text frames, such as Index and List tags. These can be inserted into a text frame by the above method, but will not work. The best method to add words to an Index or List is finish the document and layout completely (along with the text frames), and move the words you want to tag out of the text frames and on to the page. Once the Index and List are created, the words can be moved back. I doubt that anyone will notice if you forget to move out a word, from a text frame, that should be included in the Index.
@ENDNODE
@NODE AutoC "Auto-correct"
@{fg highlight}@{u}Wordworth PD@{uu}@{fg text}

	@{u}Auto-correct@{uu}

Auto-correct is a wonderful feature of Wordworth, which can automatically correct words, change abbreviations and capitalise names.

The auto-correct requester allows you to automatically correct day and month names, but unfortunately the word/month "May" is used in everyday language... i.e. "I like Wordworth, where @{b}may@{ub} I buy a copy". If you enable the auto-capitalisation of the day and month names, then you have to beware of your text - a mistake is a mistake and could cost you marks in an assignment, a job in a business report or estimate, etc. - it will all reflect on you. If you use a grammar checker, then this should flag any mistake. Personally, I have entered all of the day and month names (except the month of May) into the requester by hand.

If you are using Wordworth to write business or College reports (these are usually formal and do not allow abbreviations), you may want to consider entering abbreviations in the list. Wordworth will then auto-correct these for you, allowing you to write your document without checking every word. Examples include:

aren't = are not
can't = can not
don't = do not
shan't = shall not
shouldn't = should not
won't = would not
@ENDNODE
