Skip to content

.INI compatibility is a worthy goal #411

@hgolden

Description

@hgolden

I believe that it is a worthy goal to make TOML upward compatible with a large class of existing .INI files (despite the fact that the format isn't fully specified). If necessary, this could be an alternative syntax. The idea behind this is to immediately acquire a large set of valid TOML so adoption of the parser will be encouraged.

I don't know enough about .INI in non-ASCII uses, but it would be preferable to read data from existing .INI files encoded in existing non-Unicode encodings. The reason is that there are so many of them. To enable this, it should be possible to specify a default non-Unicode encoding when calling a TOML parser. I assume that ICU would provide all the necessary code conversion.

While UTF-8 is a lingua franca, IMO there is no reason that it has to be the only encoding accepted.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions