On Tue, Sep 6, 2016, at 06:34, Martin Panter wrote: > Yes, that was basically it. Though I had only thought as far as simple > encodings like ASCII, where one byte corresponds to one character. I > wonder if you really need UTF-8 support. Are the encoding values > currently encountered for Windows consoles all single-byte encodings > or are they more complicated? Windows supports Chinese, Japanese, and Korean encodings (code pages 936, 932, 949) that are multi-byte with one or two bytes per character. I'm not sure how that affects this though or what your point about not needing UTF-8 is.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4