[
https://issues.apache.org/jira/browse/DAFFODIL-1923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Josh Adams resolved DAFFODIL-1923.
----------------------------------
Resolution: Fixed
Assignee: Dave Thompson (was: Josh Adams)
The issue of having the escapeEscapeCharacter and the escapeBlockEnd using the
same character has been resolved in commit
59654346802a1a16c3c1461f48a8d19397287044
There are still some issues where for example the EEC is "+" and the
escapeBlockEnd is "++", but that is an extreme edge case and does not prevent
Excel's CSV export from working. This issue has been documented in
DAFFODIL-1972
> 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
> Assignee: Dave Thompson
> 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)
