[
https://issues.apache.org/jira/browse/CSV-107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14035927#comment-14035927
]
Gary Gregory commented on CSV-107:
----------------------------------
BOM processing seems pretty important since Excel is an important data source.
So we need consider:
- Should a Charset passed in the API override the BOM?
- Should we simply depend on Commons IO for BOM processing since 3 classes are
needed.
> 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: csv-bom.diff, 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)
