-------------------------------------------------------------------
DATA ENCAPSULATION
-------------------------------------------------------------------
Data is either 'naked' (without encapsulating doublequotes), or quoted.
Quoted data is used to protect imbedded carriage returns, imbedded
commas, odd characters and of course, the quote character itself.  
Quotes that are 'data' are doubled up.  

-------------------------------------------------------------------
UNQUOTED ENCAPSULATION
-------------------------------------------------------------------
Data that does NOT contain newlines, carriage returns, comma's or
quotes (or ASCII data below 0x20 or above 0x7f) stands on its
own:

  data <1234> followed by <The Big Ol' Bear>  

becomes:

  1234,The Big Ol' Bear{CR}


-------------------------------------------------------------------
QUOTED ENCAPSULATION
-------------------------------------------------------------------
Data that contains double quotes, commas, returns or other odd
characters outside the 7-bit ASCII character set is quoted.  

  data <1234 Harrington St, Northwest> followed by <Suite 17 Stop 3>

becomes:

  "1234 Harrington St, Northwest",Suite 17 Stop 3

Note that the second chunk of data does not have the protection
of the quotes: it doesn't need it, having no odd characters within.
   <1234 West "Q" St.>


-------------------------------------------------------------------
QUOTED ENCAPSULATION OF DOUBLE QUOTE
-------------------------------------------------------------------
Data that contains double quotes is a special case, and oddly 
interpreted by all nature of commercial programs.  Consider the 
data:

   <1234 West "Q" St.>

It should become:

   "1234 West ""Q"" St."	<<< RIGHT WAY

Where each internal DATA quote is doubled up.  However, some 
programs (such as Paradox) don't do so nicely.  They would represent
the data as:

   "1234 West "Q" St.",....	<<< WRONG WAY

Where they feel that a doublequote with no comma following is part of
the data. This turns out to be rather bogus, as it can be painful under
various common circumstances (e.g.:

   <1234 West "Q" St. (for "Quantum", or "Quality")>

becomes

   "1234 West "Q" St. (for "Quantum", or "Quality")",

Which of course is entirely ambiguous as to the placement of data in 
the field.
