[HECnet] Non ASCII fonts on VMS?

Johnny Billquist bqt at softjar.se
Sat Sep 28 20:28:33 PDT 2013


On 2013-09-28 21:18, Johnny Billquist wrote:
On 2013-09-28 21:10, Brian Schenkenberger, VAXman- wrote:
Johnny Billquist <bqt at softjar.se> writes:

On 2013-09-28 11:51, Sampsa Laine wrote:
    Are you saying that Terminal.app (a program I avoid by the way,
since the VT100 emulation is buggy) do not pass all values? How are
you using it, by the way?
Selected some arabic language on your MAC, running the terminal,
typing in there, and in the terminal you have telnetted to some VMS
box.

Yes, essentially, Terminal.app will not accept Arabic letter input
but displays Arabic text (incorrectly, without ligatures).

I've tried this both locally, over SSH and Telnet.

Again, I don't think this is a VMS issue.

In this case, I think it is not. But I think you can pretty much expect
there to be situations where it will break for you because VMS do not
really work correctly with UTF-8. Your best chance, if you really want
to do UTF-8 would be to write your own program to output the file.

That's not true.   VMS is only transmitting bytes of data to his
terminal.app.
VMS does not have any knowledge of the usage of that transmitted data
by the
autonomous application that is digesting it at the end of the
connection; in
this case, Terminal.app.

VMS can wrap output, and for that VMS keeps track of printing characters
output, so it can know when it hits column 80... And at that point, it
inserts extra CR+LF in the stream.

Checking at terminal settings in VMS:
LFFILL and CRFILL will also mess you up.

Thinking a bit more, these two might actually not be a problem. I think a plain CR or LF will not occur in the middle of a multibyte sequence.

Broadcast will mess you up.

This one is because broadcast text can just as well pop up in the middle of a multibyte character. However, since I think the broadcast will only happen between complete I/O requests, chances might be low, unless you do multibyte characters in multiple I/O requests.

TTSYNC can output XOFF and XON characters to you at any time.

Correction, it was HOSTSYNC I was thinking of here.

Lowercase alters output.
Tab can replace the tab character with a number of spaces.

And of course, the WRAP issue mentioned previously.

	Johnny

-- 
Johnny Billquist                                   || "I'm on a bus
                                                                  ||   on a psychedelic trip
email: bqt at softjar.se                         ||   Reading murder books
pdp is alive!                                         ||   tryin' to stay hip" - B. Idol



More information about the Hecnet-list mailing list