Test: Encoding overhaul and web support

[bpasero]

Refs: #79275

• web @alexdima
• web @sandy081
• anyOS @isidorn

Complexity: 3

Create Issue

---

This milestone encoding support landed for web. This was possible by depending on iconv-lite-umd, a webpacked version of iconv-lite.

Note: Unless files.autoGuessEncoding: true, the encoding for a file will always be the value of the files.encoding setting (UTF-8 by default) unless the file has a UTF-8 or UTF-16 byte-order-mark for identification. And even when guessing is enabled, it may result in wrong guesses or no guesses at all.

Verify:

• you can use
  • web: https://vscode-web-test-playground.azurewebsites.net/?enter=true (it even includes some encoded files)
  • desktop: any OS install will work fine
• for text files you see an entry in the status bar that shows the encoding of the file
• you can reopen the file with a different encoding ("Reopen with Encoding")
• you can change the encoding of the file ("Save with Encoding")
• UTF-8 with BOM, UTF-16LE and UTF-16BE put a byte-order-mark in the beginning (use Hex Editor extension to verify)
• you can change files.encoding and from then on files will use the configured encoding when reading and writing
• you can enable files.autoGuessEncoding: true and the encoding will be guessed from the contents (you can use this file to verify CP1252)