[
https://issues.apache.org/jira/browse/CSV-107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14035792#comment-14035792
]
Thomas Neidhart edited comment on CSV-107 at 6/18/14 3:00 PM:
--------------------------------------------------------------
Sure, the UnicodeReader solution is just a little bit smaller, but I do not
have a preference.
I agree with the OP that this could be a serious problem for potential users
processing certain files and if there is a simple way to avoid these problems,
then we should do it imho.
was (Author: tn):
Sure, the UnicodeReader solution is just a little bit smaller, but I do not
have a preference.
I agree with the OP that this could be a serious problem for potential users
processing certain files and if there is a simple way we should do it.
> 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
> Reporter: Kenzley Alphonse
> Priority: Minor
> Fix For: 1.x
>
> 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)
