As discussed in this thread:
The public File APIs in brackets use the incorrect strings for specifying encoding types (currently only "utf8" is supported).
To summarize, the HTML5 File System draft
says that encodings should be specified by their IANA names:
So, for example, to open a file with UTF 8 encoding, the encoding
should be specified as:
Currently brackets uses the "utf8" string, which is counter to the
However, internally, we need to specify the strings in the "utf8" format, in order to maintain compatibility with the NodeJS API.
It appears that this will require changes in:
It will also require that a number of tests are updated to use the appropriate string.
So, the work required is:
If there are no objections, then I will take care of this.
Assigning to Mike @mikechambers .
Fixed But Not Closed. @mikechambers please confirm that this is fixed and close it.
Fixed in pull request #874