Starting with Fetch 5.6, and with help of our friends at BareBones, we have a better way of handling text encodings when editing remote files.
Versions of Fetch prior to 5.6 behaved in one of two different ways when editing remote files:
- Ignore the user-specified preferred encoding — which annoyed many of our users
- Ignore the file-specified encoding — which annoyed many of our users
- If a remote file contains encoding information (such as am HTML META content-type tag), and you use Fetch to edit the file, the encoding information will be honored.
- If a remote file doesn’t specify its own encoding, then the preferred encoding from Fetch preferences will be used when you edit the file.
If you are using a different text editor, your results will vary; many editors ignore preferred encoding from Fetch preferences, and some ignore the encoding provided by the file itself. Feel free to contact the authors of your favorite text editor and request that they improve their cooperation with Fetch.
If you are a developer of a text editor, and you want to improve your integration with Fetch, please read the external editor protocol specification, and contact us with any questions.