Skip to content

invalid_encoding for no apparent reason #248

Description

@evokateur

I installed the gem on two Ubuntu machines and a mac.

I tested with a very simple CSV file

$ cat foo.csv
field1,field2,field3
"hello","hello","hello"

The result on the mac:

$ csvlint foo.csv
..
foo.csv is VALID

The result on both Ubuntu machines:

$ csvlint foo.csv

foo.csv is INVALID
1. invalid_encoding. Row: 1. 1

The encoding of the file:

$ file foo.csv
foo.csv: ASCII text

environments:

  • macOS Big Sur, zsh
  • Ubuntu 18.04.4 LTS running in Homestead
  • Ubuntu 18.04.2 LTS EC2 instance

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions