Grant Taylor  wrote:
> On 2/11/21 9:44 PM, Flavio Bessa wrote:
> > Hello folks,
>
> Hi,
>
> > I was trying to run Mystic, but it seems that the LXTerm is not very
> > much friendly to ANSI character codes. Is there a way to tweak it?
>
> I know for a fact that XTerm, which it seems is the root of LXTerm, has
> supported ANSI control codes for at least 20 years as I've been using
> them in it for at least that long.
>
> Please provide more details about the problems that you're seeing.
>
> Also, can you reproduce the problems in standard XTerm?
>
The ancestor of ANSI codes is surely the DEC VT100 from way back
before PCs even existed, so pre-Windows certainly and probably pre-DOS.

I agree though, just about every modern terminal emulator for Linux
supports ANSI codes.

Support of 'extended characters', those in the 128 to 255 range, i.e.
not ASCII isn't really to do with ANSI codes. The ANSI codes are
mostly ways to change character colours, bold, underline, etc.

The 128 (well, strictly 144) to 255 'characters' are defined by what
codepage/character encoding you are using.  Codepages are beginning to
disappear now but you can use them by setting your locale to things
such as en_GB ISO-8859-1 (there's a whole series of ISO-8859 encodings
from 1 to at least 15) ISO-8859-1 is the 'latin' set with standard
West European langauages characters like accented e, a, c with a
cedilla, etc. Other code pages have graphical characters etc.
Read the manual pages about locale to configure these.

The 'modern' way to handle extended/extra characters is UTF, I have
all my systems set to the en_GB.UTF-8 locale now and everything 'just
works' to the extent of displaying arabic, chinese and all sorts of
other characters sets in my terminal windows.

--
Chris Green
·

--- SoupGate-Win32 v1.05