Importing/exporting data with carriage returns (I Think)

[Fairlight]

XML has its own set of issues.  Suddenly you go from \r or \n being an
issue, or " and , being an issue, to < and > being issues.  Or with JSON, "
and , and [ and ] and { and } and : becoming issues.

XML has CDATA, but that has issues, because ]]> becomes your enemy, no
matter how unlikely it is you'd hit that.

If you want maximum portability without pain or risk, Base64 encode
everything.

m->

On Fri, Aug 25, 2017 at 08:22:35PM +0000, Walter Vaughan Jr via Filepro-list thus spoke:
> Sort of what <XML> was invented to solve. With XML you can have as many soft and hard carriage returns as you want per field in a row of data. Would tools in filePro 5.7 and newer be helpful?
> 
> -----Original Message-----
> From: Filepro-list [mailto:filepro-list-bounces+wvaughan=steelerubber.com at lists.celestial.com] On Behalf Of Richard D. Williams via Filepro-list
> Sent: Friday, August 25, 2017 3:55 PM
> To: filepro-list at lists.celestial.com
> Subject: Re: Importing/exporting data with carriage returns (I Think)
> 
> You have a real problem here.  Typically we need some unique character to indicate the end of a row. 
> _______________________________________________
> Filepro-list mailing list
> Filepro-list at lists.celestial.com
> Subscribe/Unsubscribe/Subscription Changes
> http://mailman.celestial.com/mailman/listinfo/filepro-list
> 

-- 
Audio panton, cogito singularis.