[author], [title], [publisher] ([date]).

John Steinbeck, The Grapes of Wrath, Random House (1946).

Author:[author]
Title: [title]
Publisher: [publisher]
Date:  [date]

Author:John Steinbeck
Title: The Grapes of Wrath
Publisher: Random House
Date:  1946

  [author/17]  [title/25]  [date]

  John Steinbeck   The Grapes of Wrath  1946

[author], [title], [publisher] ([date]).
----------------------------------------------
Synopsis:

{note/wrap 2 74}

John Steinbeck, The Grapes of Wrath, Random House (1946).
----------------------------------------------
Synopsis:

  The narrative begins just after Tom Joad is paroled  from 
  McAlester prison for homicide. On his journey to  his home 
  near Sallisaw, Oklahoma, Tom meets former  preacher Jim Casy, 
  whom he remembers from his childhood, and the two travel 
  together. When they arrive at Tom's childhood farm home, 
  they find it deserted. Disconcerted and confused, Tom and 
  Casy meet their old neighbor, Muley Graves, who tells them 
  the family has gone to stay at Uncle John Joad's home  
  nearby. Graves goes on to tell them that the banks have 
  evicted all the farmers off their land, but he refuses to 
  leave the area.(Wikipedia)

• The Markup Editor The markup editor occupies the left side of the pane. At the top is the title of the markup being edited and a "save changes" button. Below this is the text window that holds the markup. You may enter or cut and paste text here just as you would in any text editor. Note that when you press the "save changes" button, Plato checks the markup text for errors. If errors are discovered, the error pane opens up below the text pane and displays a list of the errors along with their locations in the markup. Until the errors are corrected you won't be allowed to save the markup. Note that most errors can be avoided by using the markup code builder to generate markup codes and labels.
• The Markup Code Builder This is the set of controls to the right of the text window. Using these controls, you can automatically generate markup labels and codes, as well as macros and interal variables for insertion in the text. Figure 2 shows how codes and labels are inserted intop the markup.

• [[head]] Markup under this section will be placed at the beginning of the output file.
• [[tail]] Markup under this section will be placed at the end of the output file.
• [[object object class name: object class ID]] Markup under this section will be added to each object of the type specified. Note that each object section must be associated with a particular object class:

  Label syntax:
  [[object object class name: object class id]]  
  Example:
  [[object note:8]]

  
  The class name and ID must both be present for validation. Since the class ID is usually a hidden attribute, don't try to find and remember it; select the object classes from the code builder control and Plato will supply the correct codes and insert the label into the markup.
  
  NOTE: If you preface the markup brackets with a capital "R", the script will use the raw data from the field instead of the formatted data. Example: R[author]. This feature is mostly of use when delivering Plato numeric attributes to a numerical application like a spreadsheet. Since all Plato object attributes are subject to formatting rules, these rules may conflict with an application like Microsoft Excel, which will impose its own formatting rules on numbers. For these occasions using the "R" option will ensure the Plato numeric attribute is not formatted when processed by the script.
• [[bookmarks]] Markup under this section will be added to bookmarks.
• [[post_processing]] This section defines post-processing instructions.
• swap lists Swap list sections allow you to build swap lists and apply them to various elements of markup and object data. See xxx for more information about swap lists. There are six ways swap lists can be applied; each variation performs its substitutions on a different portion of the script. Although this variety of types may initially seem like unneeded complexity, you will eventually see that for certain types of problems that may arise with markup logistics, each type performs a necessary function. The six ways are:
  1. [[swap_list_markup]] Acts only on the markup before any object data is attached.
  2. [[swap_list_metadata_only]] Acts only on object field data (metadata) before it is attached to markup.
  3. [[swap_list_notes_before/without_formatting]] Acts on notes without formatting, or (for notes with formatting instructions attached) before they are formatted.
  4. [[swap_list_notes_after_formatting]] For notes with formatting instructions, acts on the note after it has been formatted. For notes without formatting instructions, this has the same effect as 'swap list (notes before/without formatting).' Be careful--if you apply both swap list types to an unformatted note the results may be unpredictable.
  5. [[swap_list_markup_metadata_notes]] Acts on both object field data and notes after markup has been applied to them. This is the swap list type you will probably most often use.
  6. [[swap_list_bookmark_notes_only]] Acts only on the note field for bookmark objects (this allows footnotes or endnotes to have different formatting markup).
     

• Plato attribute codes and formatting instructions Applies to sections labeled "object" and "bookmarks"
• Code Building Window Displays the code built using the code generator controls. Press the 'insert code' button to insert the code into the text editor.
• Select Object class Selects the object class for the label. The object class selected here will determine which attributes are displayed in the attribute drop down list.
• Select Object class attribute The attribute selected here will be displayed in the code building window.
• Select formatting mode This selection will determine what formatting, if any, will be applied to the attribute. This formatting is intended for plain text markup, and may have unpredictable effects if applied to markup for HTML, RTF, or other output.
1. No formatting No formatting will be applied.
2. Fixed length, no formatting The attribute will be displayed within a fixed-legnth area. The length of the area will be as specified in the 'length' drop down list. Fixed length formatting is intended to produce plain text column displays in which the columns are padded with spaces. Example:
   

   [field name/20] = insert field contents in a fixed space of 20 characters

3. Use formatting Allows the attribute to be word wrapped and stripped of extra spaces and line ends. This is intended for large attributes such as notes but may be applied to any attribute. The formatting instructions produce the following codes:
   • [note] insert contents of note
   • [note/wrap 3 74] insert contents of note; word wrap into block starting at column 3 and ending at column 74
   • [note/wrap 3 74 ni] same as word wrap command except the first line will start at column 0 (no indent)
   • [note/strip space] insert contents of note and remove all extra spaces
   • [note/strip returns] insert contents of note and remove all single CR/LF characters
   These instructions may be combined:

     [note/wrap 2 74/strip space/strip returns]

• Macros and internal variables Applies to sections labeled "head," "tail," "post processing," and all swap list sections
• Macros Allows you to select a macro from the drop down list and insert it into the markup text. For more about macros, see below.
• Internal Variables Allows you to select an internal variable from the drop down list and insert it into the markup text. For more about internal variables, see below.

   &end_of_line&quote   =   &end_of_line``
   " \&quote"=   " ``"
   "\&quote "=   "'' "
   \&quote&end_of_line   =   ''&end_of_line 

 &end_of_para =  \par}{\Pard 

1. [[swap_list_markup]] Acts only on the markup before any object data is attached. This use is rather specialized and exists to allow you to swap in Plato reserved characters. For instance, if you markup has the text [balloon] in it, Plato will interpret it as an object attribute, and if it does not find a matching arrtribute in the selected object class it will flag the text as an error. Some entries in the SWAP-LIST-MARKUP section will fix this: in the markup type !balloon? and under the [[swap_list_markup]] section include the following two entries:
   

    ! = <
    ? = >

2. [[swap_list_metadata_only]] Acts only on object field data (metadata) before it is attached to markup.
3. [[swap_list_notes_before/without_formatting]] Acts on notes without formatting, or (for notes with formatting instructions attached) before they are formatted.
4. [[swap_list_notes_after_formatting]] For notes with formatting instructions, acts on the note after it has been formatted. For notes without formatting instructions, this has the same effect as 'swap list (notes before/without formatting).' Be careful--if you apply both swap list types to an unformatted note the results may be unpredictable.
5. [[swap_list_markup_metadata_notes]] Acts on both object field data and notes after markup has been applied to them. This is the swap list type you will probably most often use.
6. [[swap_list_bookmark_notes_only]] Acts only on the note field for bookmark objects (this allows footnotes or endnotes to have different formatting markup).