add properties for charset and byte order mark about editorconfig HOT 9 CLOSED

I agree with the two.

from editorconfig.

I also like these ideas.

I think we should try to tackle a charset property first.

We may need to create a list of supported character sets so plugins can support charsets individually if charset names are not always represented consistently among different text editors. If this is the case, which character sets should we attempt to support initially?

from editorconfig.

I have made a Wiki page we can use for reference when fleshing out charset details.

from editorconfig.

As a start, I think we should support Unicode charsets and latin1. They are widely supported by editors. Then let's add more.

from editorconfig.

I believe this could be done in v0.9, since it requires no modification to the EditorConfig Core: it's about the standard and the implementation of the plugins.

from editorconfig.

I think we should aim to release the indent_size = tab feature in a final/stable before implementing this feature. There are multiple tab-indented projects that could benefit from specifying a non-fixed indentation size and size indent_style = tab.

Maybe we should declare v0.9 of EditorConfig C core stable, upload new versions of core, and upgrade the C-based plugins first. We could then work on adding charset to v0.9.1 or v1.0 (if we're ready for the big 1.0 release).

from editorconfig.

We could also release non-c based plugins. Then we work on v0.9.1, to include the python core. This feature maybe could included in v0.10, avoiding the release of v1.0

from editorconfig.

These options will be implemented in v0.10.0 as a single property: charset.

from editorconfig.

Where is charset documented?

from editorconfig.