commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sebb (JIRA)" <>
Subject [jira] [Commented] (CSV-58) Unescape handling needs rethinking
Date Thu, 01 Aug 2013 13:03:49 GMT


Sebb commented on CSV-58:

If the behaviour is symmetric, I think we can leave it as it is for now.

By symmetric, I mean that if the format escapes TAB FF and BACKSPACE it should unescape them
as well.
Also if the format does not escape them, then they should not be unescaped either.
> Unescape handling needs rethinking
> ----------------------------------
>                 Key: CSV-58
>                 URL:
>             Project: Commons CSV
>          Issue Type: Bug
>          Components: Parser
>            Reporter: Sebb
>             Fix For: 1.0
>         Attachments: commons-csv.diff
> The current escape parsing converts <esc><char> to plain <char> if
the <char> is not one of the special characters to be escaped.
> This can affect unicode escapes if the <esc> character is backslash.
> One way round this is to specifically check for <char> == 'u', but it seems wrong
to only do this for 'u'.
> Another solution would be to leave <esc><char> as is unless the <char>
is one of the special characters.
> There are several possible ways to treat unrecognised escapes:
> - treat it as if the escape char had not been present (current behaviour)
> - leave the escape char as is
> - throw an exception

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message