[
https://issues.apache.org/jira/browse/SANDBOX-206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12556053#action_12556053
]
Yonik Seeley commented on SANDBOX-206:
--------------------------------------
I've done some more investigation of what common CSV producers use:
Excel does not do backslash escaping.
MySQL does backslash escaping to escape separators and or to escape
encapsulators if they are used. The escape is used to escape itself.
This is the behavior I think we should mimic (no backslash escaping, but escape
consistently if enabled) I haven't been able to find any basis for the current
behavior... so if you understand why the current code purposely does what it
does, speak up!
> backslash before quote character gives an error
> -----------------------------------------------
>
> Key: SANDBOX-206
> URL: https://issues.apache.org/jira/browse/SANDBOX-206
> Project: Commons Sandbox
> Issue Type: Bug
> Components: CSV
> Environment: Windows, SOLR 1.2
> Reporter: Michael Lackhoff
>
> A CSV-field with the contents "This is text with a \""quoted"" string" gives
> the error
> "invalid char between encapsualted token end delimiter". If the backslash is
> not immediately before the double quote, everything is fine.
> The same error occurs when the backslash is the last character in the field
> (directly before the delimiter), like:
> "This is a text with a backslash \".
> Here the reason might be that the backslash also works as an escape character
> like in
> "This is a field with a \"quoted\" text" (no error, just the quotes in the
> resulting field)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
