[CSV-58] Unescape handling needs rethinking

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Fix Version/s: Patch Needed, 1.x
• Component/s: Parser
• Assignee: Unassigned
• Reporter: Sebb
• Created: 14/Mar/12 15:37
• Updated: 10/Jul/14 19:43

Description

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

Issue Links

• is related to: CSV-56 Do not use exotic escape characters for sequences like \r or \n