Skip to content

Files and Resources do not handle UTF-8 files with BOM #345

@gissuebot

Description

@gissuebot

Original issue created by kai@google.com on 2010-04-08 at 07:59 PM


By the UTF-8 definition, UTF-8 files are allowed to have an optional leading
BOM. This BOM is stupid and pointless, but many Windows apps seem to
generate UTF-8 files with the BOM. Guava's classes Files and Resources do
not handle UTF-8 files with a BOM. I'm not sure where this fix belongs, or
whether it should even be fixed at all (since Windows is being stupid, and
people are rightly sick and tired of working around Windows issues). BTW, I
don't personally use Windows. I'm reporting this issue only because I
maintain a library that uses Guava, and there are some Windows users of my
library that are running into this issue.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions