From af3c8348a096b80a22d9463c516a932689a4836c Mon Sep 17 00:00:00 2001 From: bptato Date: Wed, 12 Jul 2023 00:05:14 +0200 Subject: Improve encoding support * Use the output charset in lineedit (as w3m does) * encoder: fix broken UTF-8 encoding, use openArray instead of var seq for input queue * Add RuneStream as an in-memory interface to EncoderStream * Document display-charset config option --- doc/config.md | 24 +++++++++++++----------- 1 file changed, 13 insertions(+), 11 deletions(-) (limited to 'doc/config.md') diff --git a/doc/config.md b/doc/config.md index 6662d1be..443d7003 100644 --- a/doc/config.md +++ b/doc/config.md @@ -111,21 +111,23 @@ Following is a list of encoding options: -fallback-charset +document-charset string/array -Default character set for loading documents.
-For text -documents, all listed character sets are enumerated until the document has been -decoded without errors. +List of character sets for loading documents.
+All listed character sets are enumerated until the document has been decoded +without errors. In HTML, meta tags and the BOM may override this with a +different charset, so long as the specified charset can decode the document +correctly. + -document-charset -string/array -List of forced character sets for loading documents.
-All listed character sets are enumerated until the document has been decoded -without errors.
-Overrides fallback-charset. +display-charset +string +Character set for keyboard input and displaying documents.
+Used in dump mode as well.
+(This means that e.g. `cha -I EUC-JP -O UTF-8 a > b` is equivalent to `iconv +-f EUC-JP -t UTF-8.) -- cgit 1.4.1-2-gfad0