> Date: Fri, 17 Feb 2017 13:41:38 +0100 > From: "Andries E. Brouwer" <[email protected]> > Cc: [email protected], "Andries E. Brouwer" <[email protected]>, > YX Hao <[email protected]> > > So the unicode part is straightforward. Other encodings are messy. > For SJIS and similar multi-byte character sets one can have > (per character set) descriptions of which codes are single-byte > and which double-byte, and how wide the resulting symbol is. > For ISO 2022 type encoding, with embedded escape sequences, > life is more difficult.
I'm probably missing something here, because I don't understand how the encoding of what wget writes to the terminal can affect the width of the characters displayed by that terminal. That width is the property of the character itself, and doesn't depend on how you tell the terminal to display the character. Fonts indeed can affect the visual width, but if we assume that the terminal font is a fixed-pitch one, that problem is much less significant, IME.
