2016-02-17 14:02 GMT+01:00 Oliver Tonnhofer <[email protected]>:
> RFC4180 allows newlines as long as they are inside of double quotes. This is 
> at least supported by the Python and Go standard libraries, not sure how 
> other software handles this.

Thanks, Oliver. That's correct.
I have to be more specific:
The ABNF of RFC4180 says:

escaped = DQUOTE *(TEXTDATA / COMMA / CR / LF / 2DQUOTE) DQUOTE

:Stefan

2016-02-17 14:02 GMT+01:00 Oliver Tonnhofer <[email protected]>:
> Hi Stefan,
>
>
>> On 17.02.2016, at 13:53, Stefan Keller <[email protected]> wrote:
>>
>> 2016-02-17 11:48 GMT+01:00 Jeremy Palmer <[email protected]>:
>>>> Allowing non-printable control-characters in strings makes it very
>>>> complicated and disables mainly all existing CSV software.
>>>
>>> Yes but Excel handles it. So does OGR and QGIS Delimited Text Provider.
>>> From memory the Microsoft ODBC CSV driver doesn’t - but that’s got lots of 
>>> issues.
>>
>> No, it does'nt handle linebreaks as one record - nor is this allowed
>> in any of the CSV standardization approaches I know.
>
> RFC4180 allows newlines as long as they are inside of double quotes. This is 
> at least supported by the Python and Go standard libraries, not sure how 
> other software handles this.
>
>
>
> Regards,
> Oliver
_______________________________________________
gdal-dev mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/gdal-dev

Reply via email to