commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Emmanuel Bourg (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CSV-107) CSVFormat.EXCEL.parse should handle byte order marks
Date Sun, 16 Mar 2014 23:12:42 GMT

    [ https://issues.apache.org/jira/browse/CSV-107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13937369#comment-13937369
] 

Emmanuel Bourg commented on CSV-107:
------------------------------------

Handling the BOMs is outside the scope of commons-csv IMHO. The BOMs should be checked ahead
of the CSVParser to build a proper input Reader (using {{BOMInputStream}} for example. We
should probably add a BOM aware InputStreamReader in common-io btw).

> CSVFormat.EXCEL.parse should handle byte order marks
> ----------------------------------------------------
>
>                 Key: CSV-107
>                 URL: https://issues.apache.org/jira/browse/CSV-107
>             Project: Commons CSV
>          Issue Type: Bug
>          Components: Parser
>    Affects Versions: 1.0
>            Reporter: Kenzley Alphonse
>            Priority: Critical
>         Attachments: vod.csv
>
>   Original Estimate: 3h
>  Remaining Estimate: 3h
>
> The CSVFormat.EXCEL.parse should consider the byte order marks when reading the input
stream. Files with a byte order mark fail to properly parse.
> In my example, I have a starting byte order mark before my headers in a CVS file. The
parse fails when trying to get the header via the CSVRecord.get call.
> I marked this as critical because many users will interact with Windows user which will
most likely have BOM files.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message