Path: ...!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!eternal-september.org!.POSTED!not-for-mail
From: sjack@dontemail.me (sjack)
Newsgroups: comp.lang.forth
Subject: Unicode Codepage STDIN STDOUT ERROUT
Date: Sun, 18 May 2025 17:16:19 -0000 (UTC)
Organization: A noiseless patient Spider
Lines: 19
Message-ID: <100d4l3$13h8n$1@dont-email.me>
Injection-Date: Sun, 18 May 2025 19:16:20 +0200 (CEST)
Injection-Info: dont-email.me; posting-host="ac434886f5dacb302967b2d782c1becd";
	logging-data="1164567"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX1/kyGzE1JZHMZh3/aK0uTZQ"
User-Agent: tin/2.6.4-20240224 ("Banff") (Linux/6.8.0-60-generic (x86_64))
Cancel-Lock: sha1:qNYQOKi9iN1Z6HrJPKt0/pAhkHk=
Bytes: 1730

I operate with a Unicode terminal but have it set up for codepage.
Any Unicode output other than ASCII values is directed to another
Unicode terminal (window) using handle HUNI .  
Sometimes along with Unicode output I also direct STDOUT, normal
Forth output, to the same Unicode window but using handle HOUT . The
low register codepage characters of normal Forth output will display
properly in a Unicode terminal.  Straight forward, nothing
complicated, and flexible.

Toad extensions also supports ERROUT.  Error messages and the OK
command status are set to use ERROUT. Typical use of this arrangement
is to direct STDOUT to another window on Forth startup.  The window
from which Forth was launched is left with STDIN, and ERROUT. This
launch window then provides terminal input and displays the OK
command status and error messages. All "clean" output goes to the
other window.

-- 
me