In moving from swish-e version 2.1 to 2.4.0-pr4, I noticed a slight change 
in how -x behaves.  In this example:

-x 
\'<swishrank>\"<swishdocpath>\"<swishtitle>\"<swishdocsize>\"<swishlastmodified 
fmt=\"%m/%d/%Y\">\n\'

double quote chars are serving as field separators.  This was a good choice 
with swish-e version 2.1, because if any of the actual data contained 
double quote chars, they got swapped to single quote chars.  It looks like 
2.4 doesn't do this anymore; is that right?  If so, is there another good 
solution out there to the timeless problem of "pick a field separator that 
won't show up in your data"?

Thanks,

David





*********************************************************************
Due to deletion of content types excluded from this list by policy,
this multipart message was reduced to a single part, and from there
to a plain text message.
*********************************************************************