I'm running a terminal emulator that has char(182) bound to the alt-F1 key,
which with my "linux console" terminal emulation chosen here at my end,
and term type d3-mon chosen at the server end, should produce a nice
little "paragraph" symbol. And at a bash prompt it does -- either before I
start my d3 session or during a ! subshell of d3. But d3 seems to filter
that down to a "6" character.

I can crt char(182) and see it ok, so the linux stty settings of that d3
session
aren't mutating it to 6 upon output. The linux stty setting is -istrip8 {I
got
another login to cooperate and check this for me}, same as back in bash.
Linux unicode_stop or unicode_start before I began my d3 session don't
make any difference.

Just pasting it from my windows clipboard doesn't work any better, btw.

So what am I doing wrong, here?

And I undestand that char(182) won't look like a nice paragraph symbol to
other users on other emulations, but I just want to use it locally and
briefly during an edit session, as a substitute for @VM or maybe @SVM
and all the control chars that produce odd symbols are in-use by the
update editor commands {a pity that -- ^Z is an overbar, for me}

Have you tried experimenting with the xcs (xcs-on, xcs-off), or
control-chars commands?

/Scott Ballinger
Pareto Corporation
Edmonds WA USA
206 713 6006

"Scott Ballinger" wrote
Yay! You fixed it!
Doing just xcs verb returned

off

Doing xcs-on verb
made my session start accepting high ascii input from keyboard
{affects both typed commands like
DISPLAY ABChigh ascii hereDEF
and basic INPUT commands}
Change was local to this pick port,
survives across logoffs and
exit then d3 -30
{this is pick port 30 I was testing on all day}
System default seems to be
xcs-off.

On a side note, both Accuterm 2k2 and Accuterm 97 terminal
emulators store high ascii in their key bindings menus in an odd
notation; the so-called paragraph symbol is {for me} char(182)
and when I stuff that in the keybinding slot in the menu page,
say by holding down left alt key while typing 0182
or just 182 on
the numeric
keypad, well, it looks like a paragraph symbol onscreen right then,
but later shows as \6 in that same menu. Works fine, just looks odd.

And no, the control-chars verb didn't help this a bit.
Neither did
unicode_stop or unicode_start done in bash before I issued
the d3 command to get a d3 USERID: prompt. And linux
stty -a was showing -istrip8 just like at a bash prompt,
where
I was easily able to do echo {high ascii here} so that wasn't it.

I see that in the dm,bp, xcs source it prints "Warning: not supported!"
if system(100) bears the substring -DOS
I hope that refers to crufty old AP/DOS and not to D3/NT...

Thanks heaps! I've never messed with high ascii in d3 before, didn't know
the xcs verb.

On Apr 29, 6:58*am, "Frank Winans" <fwin... (AT) sbcglobal (DOT) net> wrote:
XCS Works perfectly in D3 7.5.4
For those that may not have messed around with extended ASCII there is
the excellent character map in Windows typically found under All
Programs>Accessories>System Tools this shows the characters plus the
appropriate numeric keypad entries
¦ is <ALT>0166 with my current settings
For even more fun use Notepad make an entry then save it as Unicode,
Unicode BigEndian, UTF-8 and the default ANSI then read it back in
Pick - I use COPY DOS: quite useful for getting an understanding of
different encodings
Peter McMurray

"Excalibur21" <pgmcmurray (AT) gmail (DOT) com> wrote
On Apr 29, 6:58 am, "Frank Winans" <fwin... (AT) sbcglobal (DOT) net> wrote:
Hi
XCS Works perfectly in D3 7.5.4
For those that may not have messed around with extended ASCII there is
the excellent character map in Windows typically found under All
Programs>Accessories>System Tools this shows the characters plus the
appropriate numeric keypad entries
¦ is <ALT>0166 with my current settings
For even more fun use Notepad make an entry then save it as Unicode,
Unicode BigEndian, UTF-8 and the default ANSI then read it back in
Pick - I use COPY DOS: quite useful for getting an understanding of
different encodings
Peter McMurray


I {fwinans here} refreshed this posting because I wanted the
keyword glyph or glyphs to get in the google database -- I couldn't
find this thread at first attempt.
Thanks again to Scott Ballinger for the tip about d3 XCS-ON verb,
and to Peter McMurray for the above reply!

My original post of this thread was

I'm running a terminal emulator that has char(182) bound to the alt-F1 key,
which with my "linux console" terminal emulation chosen here at my end,
and term type d3-mon chosen at the server end, should produce a nice
little "paragraph" symbol. And at a bash prompt it does -- either before I
start my d3 session or during a ! subshell of d3. But d3 seems to filter
that down to a "6" character.