Mailing-List: contact issues-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: issues@commons.apache.org
Date: Mon, 11 Dec 2017 13:35:00 +0000 (UTC)
From: "Zhang Hongda (JIRA)" <jira@apache.org>
To: issues@commons.apache.org
Message-ID: <JIRA.13123992.1512913784000.429717.1512999300144@Atlassian.JIRA>
In-Reply-To: <JIRA.13123992.1512913784000@Atlassian.JIRA>
References: <JIRA.13123992.1512913784000@Atlassian.JIRA> <JIRA.13123992.1512913784724@jira-lw-us.apache.org>
Subject: [jira] [Comment Edited] (CSV-219) The behavior of quote char using
 is not similar as Excel does when the first string contains CJK char(s)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
archived-at: Mon, 11 Dec 2017 13:35:05 -0000


    [ https://issues.apache.org/jira/browse/CSV-219?page=3Dcom.atlassian.ji=
ra.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D1628587=
6#comment-16285876 ]=20

Zhang Hongda edited comment on CSV-219 at 12/11/17 1:34 PM:
------------------------------------------------------------

Thanks Gary. By the way, I even deleted the "if (c <=3D COMMENT) {" branch =
to meet what the Microsoft Excel does in my job. But when I have read the c=
omment under it, I am not sure if it is a bug or a feature. I think this so=
urcecode is only affect to the printing of a CSV file, but has no no effect=
 on the parser. When I tried to parse a CSV file with a char which ASCII co=
de less than '#' but more or equal than 0x20 without quoting it, I didn't f=
ind any problem which the comment says. I still wondered in which case the =
parser will fail in common cases. So for the time being, I am not reporting=
 that as a bug.


was (Author: hongda):
Thanks Gary. By the way, I even deleted the "if (c <=3D COMMENT) {" branch =
to meet what the Microsoft Excel does in my job. But when I have read the c=
omment under it, I am not sure if it is a bug or a feature. I think this so=
urcecode is only affect to the printing of a CSV file, but has no no effect=
 on the parser. When I tried to parse a CSV file with a char which ASCII co=
de less than '#' but more or equal than 0x20, I didn't find any problem whi=
ch the comment says. I still wondered in which case the parser will fail in=
 common cases. So for the time being, I am not reporting that as a bug.

> The behavior of quote char using is not similar as Excel does when the fi=
rst string contains CJK char(s)
> -------------------------------------------------------------------------=
-------------------------------
>
>                 Key: CSV-219
>                 URL: https://issues.apache.org/jira/browse/CSV-219
>             Project: Commons CSV
>          Issue Type: Bug
>          Components: Printer
>    Affects Versions: 1.5
>            Reporter: Zhang Hongda
>         Attachments: diff.patch
>
>
> When using CSVFormat.EXCEL to print a CSV file, the behavior of quote cha=
r using is not similar as Microsoft Excel does when the first string contai=
ns Chinese, Japanese or Korean (CJK) char(s).
> e.g.
> There are 3 data members in a record, with Japanese chars: "=E3=81=82", "=
=E3=81=84", "=E3=81=86":
>   Microsoft Excel outputs:
>   =E3=81=82,=E3=81=84,=E3=81=86
>   Apache Common CSV outputs:
>   "=E3=81=82",=E3=81=84,=E3=81=86


--
This message was sent by Atlassian JIRA
(v6.4.14#64029)