[
https://issues.apache.org/jira/browse/CSV-54?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13227699#comment-13227699
]
Emmanuel Bourg commented on CSV-54:
-----------------------------------
The reason for enclosing the values into quotes is to put a delimiter or a line
separator in the value. Spaces are always part of the value, quoted or not. At
least that's how it's specified in RFC 4180.
> Confusing semantic of the ignore leading/trailing spaces parameters
> -------------------------------------------------------------------
>
> Key: CSV-54
> URL: https://issues.apache.org/jira/browse/CSV-54
> Project: Commons CSV
> Issue Type: Bug
> Components: Parser
> Reporter: Emmanuel Bourg
> Fix For: 1.0
>
>
> {{CSVFormat}} has two parameters to control how the leading and trailing
> spaces around values are handled, but the actual behavior depends on the
> value being enclosed in quotes or not.
> If the value is not enclosed in quotes, setting
> {{leading/trailingSpacesIgnored}} to {{true}} will left or right trim the
> value. For example with this input (using the default format):
> {code}a, b ,c{code}
> the second value will be equal to {{'b'}}.
> But if the value is enclosed into quotes, the value is no longer trimmed:
> {code}a," b ",c{code}
> this will give {{' b '}}.
> With quoted values the parser actually ignores the spaces between the
> delimiter and the quote. Thus with this input:
> {code}a, " b " ,c{code}
> The value returned is {{' b '}}.
> If {{leading/trailingSpacesIgnored}} is set to {{false}}, we get instead {{'
> " b " '}} which is consistent with RFC 4180.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
