![](/s/cache/cb/a7/cba7831faa68ec585148280bb53e0296.png)
+2
Fixed
UTF-16 files cannot be opened / are greyed out
Textastic doesn't correctly detect UTF-16 text files and instead treats them as being binary files. In consequence, such files are greyed out and cannot be opened.
Answer
![](/s/cache/cb/a7/cba7831faa68ec585148280bb53e0296.png)
Answer
Fixed
This bug is fixed for the next version.
Textastic now correctly detects UTF-16 and UTF-32 files with a BOM (http://unicode.org/faq/utf_bom.html#BOM) and also lets you open files it detects as being binary (greyed out in the file list).
Textastic now correctly detects UTF-16 and UTF-32 files with a BOM (http://unicode.org/faq/utf_bom.html#BOM) and also lets you open files it detects as being binary (greyed out in the file list).
Customer support service by UserEcho
Textastic now correctly detects UTF-16 and UTF-32 files with a BOM (http://unicode.org/faq/utf_bom.html#BOM) and also lets you open files it detects as being binary (greyed out in the file list).