[jira] Resolved: (IO-178) BOMExclusionInputStream - an InputStream for UTF-8 data that ignores an initial Byte Order mark

["Niall Pemberton (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/IO-178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Niall Pemberton resolved IO-178.
--------------------------------

       Resolution: Fixed
    Fix Version/s:     (was: 1.5)
                   2.0
         Assignee: Niall Pemberton

Thanks Keith, I have added this with superficial changes, mostly formatting

http://svn.apache.org/viewvc?view=rev&revision=721749

> BOMExclusionInputStream - an InputStream for UTF-8 data that ignores an initial Byte Order mark
> -----------------------------------------------------------------------------------------------
>
>                 Key: IO-178
>                 URL: https://issues.apache.org/jira/browse/IO-178
>             Project: Commons IO
>          Issue Type: New Feature
>          Components: Streams/Writers
>    Affects Versions: 1.4
>            Reporter: Keith D Gregory
>            Assignee: Niall Pemberton
>            Priority: Minor
>             Fix For: 2.0
>
>         Attachments: BOMExclusionInputStream.java, BOMExclusionInputStream.patch, TestBOMExclusionInputStream.java
>
>
> Microsoft tools have the unpleasant habit of writing a byte order mark (the three-byte sequence 0xEF 0xBB 0xBF) at the start of a UTF-8 encoded file.
> The CharsetDecoder supplied with the JDK does not simply discard these bytes, but instead returns the BOM character (0xFEFF); see http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6378911 for discussion on this.
> This makes life unpleasant for anyone who is processing text data, as the program must look for this character and ignore it.
> The BOMExclusionInputStream class is a work-around: it recognizes the BOM at the start of the stream, and skips over it.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.