Hi Fabrice, I decided to change the default behavior of the BaseX CSV parser: backslashes will now always be treated as esape characters. \r, \n and \t will be encoded as CR, NL, and TAB, and other characters will be returned literally. A new snapshot is online.
Everyone: please report if this new default causes surprises in your setting. Best, Christian On Thu, Nov 13, 2014 at 10:34 AM, Fabrice Etanchaud <[email protected]> wrote: > Dear all, > > I did not find a way to specify how to escape quotes when importing a csv > file with quotes=yes. > > Here is an example : > > "12345"|"TOTO LE HERO"|"Toto le héro 3 \"A'' > LP"|"67"|"8051"|"4000"|"XX"|""|"LU"|""|""|"ITE"|""||"GB"|""|"20.10" > > where quotes are escaped with a leading \ > (the '' after the A are two single quotes). > > But it seems BaseX detects quote quote (“”) as escaped quote. > > Could it be possible to have in the future an option to override the default > behavior ? > > Best regards, > Fabrice Etanchaud > Questel/Orbit
