Guess I'm content using ASCII - simply wondered
what happened to the non-ASCII graphical
characters, can't understand why they've
disappeared (I've liked them as console output looks less cluttered ...).
-M
At 2021-11-20 09:31, you wrote:
utf8 support in windows terminal is buggy. A robust solution would be using
windows unicode io but that is low priority. Can you use ascii box
characters instead?
On Fri, Nov 19, 2021 at 8:45 PM Martin Kreuzer <[email protected]> wrote:
> Hi all -
> Presently I'm using v8.07 and v9.0x in parallel.
> Using JConsole, I get different *layout* results depending on J version:
> a: NB. v9.0x no proper box-drawing chars showing
> U¿
> 33
> AU
> 9!:6'' NB. because none present
> UA¿AÃ
'AAU3Ã
> JVERSION
> Engine: j903/j64avx2/windows
> Beta-v: commercial/2021-11-16T21:47:12
> Library: 9.03.07
> Platform: Win 64
> Installer: J903 install
> InstallPath: d:/program files (non-sys)/j903
> Contact: www.jsoftware.com
> JConsole v8.07 has no problem switching from
> text- to graph-based chars (probably being based on cp 437).
> Same machine (running Win 10 Pro 64), same TT
> font (Consolas, Lucida Console, ...),
> tried CPs 437, 850, 1252 and 65001 (on the
> underlying command window) with no avail.
> (I've read this thread:
> http://www.jsoftware.com/pipermail/general/2010-October/033925.html )
> Anyone any suggestion?
> Thanks.
> -M
> ----------------------------------------------------------------------
> For information about J forums see http://www.jsoftware.com/forums.htm
----------------------------------------------------------------------
For information about J forums see http://www.jsoftware.com/forums.htm
----------------------------------------------------------------------
For information about J forums see http://www.jsoftware.com/forums.htm
