In article <100d4l3$13h8n$
1@dont-email.me>, sjack <
sjack@dontemail.me> wrote: >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.
I advocate another approach. A words name is a string of bytes.
It may be Chinese. TYPE ( $. ) streams a string to a terminal.
You donot transform the identification of a word. This is the
realm of the input and output devices.
If your words are Chinese and you happen to be Chinese you understand
it. If you mess around with the input or output of Forth, numerous opportunities are lost.
Compare the file names in windows. They are case insensitive! Instead
of having files identified with an array of bytes, where the content
is arbitrary. This western parochial prejudice is soon to die.
I suggest loosing the OK message while redirecting. Actually they are superfluous anyway.
Getting the error messages out on a separate channel is a good idea.
Assuming good functioning means no error messages.
--
me
Groetjes Albert
--
Temu exploits Christians: (Disclaimer, only 10 apostles)
Last Supper Acrylic Suncatcher - 15Cm Round Stained Glass- Style Wall
Art For Home, Office And Garden Decor - Perfect For Windows, Bars,
And Gifts For Friends Family And Colleagues.
--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)