[
https://issues.apache.org/jira/browse/DAFFODIL-1923?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16541593#comment-16541593
]
Michael Beckerle commented on DAFFODIL-1923:
--------------------------------------------
The fix to this bug wants to fix it, and also update the DFDLSchemas CSV schema
to include an example using these Excel escaping conventions. Excel is
certainly the most important source of CSV-oriented data out there.
> Excel export CSV escaping - can't be handled with standard block escape
> -----------------------------------------------------------------------
>
> Key: DAFFODIL-1923
> URL: https://issues.apache.org/jira/browse/DAFFODIL-1923
> Project: Daffodil
> Issue Type: Bug
> Components: Back End
> Affects Versions: 2.1.0
> Reporter: Michael Beckerle
> Priority: Major
> Fix For: 2.2.0
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> Excel spreadsheet looks like this:
> |1|2|This is "some fun" now|3
> When exported to CSV, this is created
> {code}
> 1,2,"This is ""some fun"" now",3
> {code}
> Notice the quotations around the string, and the doubling of the quotes
> inside the string as an escaping mechanism.
> One would think that an escape scheme with kind 'escapeBlock' with the block
> start, block end, escape and escapeEscape all defined to be '"' (doublequote)
> would work, but it does not.
> Error message is a PE indicating "delimiter not found".
> I am only 60% sure of this bug. It came up in a project using CSV data
> exported from excel, but other complexities there may have been interacting.
> Isolated test case is needed to really verify the behavior.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
