Return to Answer

P.S. Another shortcoming of the CSV importer which may be considered as a bug both in "TextDelimiters" and "LineSeparators":

• Importing CSV with multiline text fields

Diagnosis

A workaround

According to the Documentation, the "TextDelimiters" option determines "string or list of strings used to delimit non-numeric fields." Based on this I would consider the following behavior as a bug:

Tracing the evaluation shows that Import removes the "TextDelimiters" before converting fields which match (a kind of) NumberString into numbers. The correct behavior would be to remove the delimiters after converting numeric fields into numbers.

Double-quote characters delimiting text fields are not imported by default.

According to the Documentation, the "Table" format (as well as "CSV" and "TSV")

• Stores numerical and textual information, formatted as a table.

and for separating textual information from numerical in these data formats we have

• Import and Export option:
  "TextDelimiters" Automatic string or list of strings used to delimit non-numeric fields

Based on this I consider the following behavior as a bug:

Tracing the evaluation shows that Import removes the substrings specified via "TextDelimiters" before converting the fields which match (an analog of) NumberString into numbers. The correct implementation would be to remove the delimiters after converting numeric fields into numbers.

• Double-quote characters delimiting text fields are not imported by default.