I agree. It is really stressfull.

When changing the encoding in the Document Panel Textastic should always ask the the user if he want to save (or save as..) the file in the new encoding (always alerting the user that the current text displayed will be encoded 'as is' in the new encoding), or if he wants to reload the current file using the selected encoding to open it (always alerting the user that doing so will discard all unsaved changes and reload the file). Also when opening the file it should autodetect the encoding (now it doesn't detect chinese GB18030 and open the file as garbage).

Two suggestions:

- If an non standard UTF-8 encoding is detected when opening a file, Textastic should show the detected encoding (for example chinese (GB18030) and ask if the user wants to use a different encoding to decode the text, (clarify that internally Textastic works in UTF-8 ) or if the user wants to preserve the original encoding when loading or saving this file (always converting internally to and from UTF-8). Textastic should be able to detect and display the characters of any encoding (this does not happens now.. chinese encoded in GB18030 is not detected and shown as garbage).

- If you switch the encoding from the Document Properties the app should ask if we want to encode the current visible document in the selected encoding (so that it will be saved as it is shown but in the new encoding) or if we want to reload the original file using the selected encoding (with a warning that doing that will discard any unsaved changes to the file). 

I agree.

Two suggestions:

- If an non standard UTF-8 encoding is detected when opening a file, Textastic should show the detected encoding (for example chinese (GB18030) and ask if the user wants to use a different encoding to decode the text, (clarify that internally Textastic works in UTF-8 ) or if the user wants to preserve the original encoding when loading or saving this file (always converting internally to and from UTF-8). Textastic should be able to detect and display the characters of any encoding (this does not happens now.. chinese encoded in GB18030 is shown as garbage).

- If you switch the encoding from the Document Properties the app should ask if we want to encode the current visible document in the selected encoding (so that it will be saved as it is shown but in the new encoding), or if we want to reload the original file using the selected encoding (with a warning that doing that will discard any unsaved changes to the file).