On 2013-09-28 13:07, Brian Schenkenberger, VAXman- wrote:
Sampsa Laine <sampsa at mac.com> writes:
I am playing around with iTerm as well at the moment though.
What do you use as a terminal client on OS X?
Pros and cons of the various terminal emulations can be debated ad nauseum
and ad infinitum.
I have iTerm and iTerm2, and Terminal.app on OS X. Both of the iTerm pass
the preliminary VTTEST suites but they both fail miserably when asked to do
the DECSWL and DECDHL tests. Terminal.app renders both DECSWL and DECDHL
rather well.
Neither of them will do DECELR and DECSLE. However, in their defense, none
of the unix/linux default xterm appear to do them either. I've built xterm
from source and there are switches which will enable these. I've not found
the ideal combination yet of all of the build switches to make xterm do all
of the things I can now accomplish with a real VT terminal or DECterminal.
vttest is worse at testing than I thought if it don't pick up that Terminal.app do not even clear the screen when changing to 80 column mode (it should clear the screen, even if you are already in 80 column mode).
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
On 2013-09-28 12:45, Brian Schenkenberger, VAXman- wrote:
Johnny Billquist <bqt at softjar.se> writes:
On 2013-09-28 11:30, Sampsa Laine wrote:
Yeah I was thinking of typing up some Arabic documents in say EDIT and using TYPE to view them - but Terminal.app doesn't seem to pass the Arabic letters across correctly.
I think you are a little confused.
"Arabic letters" as such don't pass through anywhere. We're talking
computers here. Everything is ones and zeroes.
It's just a case of how you choose to interpret those ones and zeroes at
each end. 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.
That might end up with the terminal sending UTF-8 encoded Unicode, which
VMS might have some opinions about. VMS do not handle UTF-8, and some of
the values you get from the UTF-8 encoding might cause VMS to do
specific things.
The MAC will think of several bytes as one character encoded in UTF-8,
but VMS will think of that as several characters in Latin-1, unless you
are running some special program in VMS which grabs all incoming data,
in which case you can (or course) do anything you want.
How are these files being exposed to the Terminal.app? If by "$ TYPE",
then VMS doesn't know anything about the file contents other then its
record structure. The information in it will be transmitted as bytes
of some value. There is no interpretation of that data upon output.
"$ TYPE" just pumps the file data into the terminal driver.
If the file contains the appropriate UTF for some Arabic letter, that
would be output to the Terminal.app. THere may be some need for codes
that tell the Terminal.app to use the Arabic fonts; however, I believe
even that is handled by the accepted UTF encoding.
FWIW, VMS does handle arabic numerals. :)
Right, except for the fact that VMS *might* insert newlines into the output when it thinks you are hitting the terminal width...
I can't think of any other output modification done by VMS offhand. It might strip the 8th bit if you set some parameter, but that would have been very obvious in this case.
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
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.
The same might also be true for input.
As for why I like Terminal.app? I dunno, got used to it I guess in the last 8 years, not really come across too many bugs that bothered me..
I am playing around with iTerm as well at the moment though.
Tried it. It also have bugs.
What do you use as a terminal client on OS X?
xterm
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
I'm just a chemist so help me: what is an X capacitor???
Van: Dave McGuire
Verzonden: zaterdag 28 september 2013 14:56
Aan: hecnet at Update.UU.SE
Beantwoorden: hecnet at Update.UU.SE
Onderwerp: Re: [HECnet] Alpha Server 1200 p/s schematics
On 09/28/2013 08:24 AM, Rok Vidmar wrote:
>> I' m thinking of repairing the damaged unit but need schematics for that.
>
> In fact, you don't. Open it up, replace the electrolytes. Near them you
> may find a blown small element which is not needed really.
The 'X' capacitor? Actually I'd not want to run a big power supply without
that. They're usually not difficult to find, or to replace.
-Dave
--
Dave McGuire, AK4HZ
New Kensington, PA
Brian, I'm in the Netherlands so shipping will be too expensive (I think)
Hans
Van: Brian Schenkenberger, VAXman-
Verzonden: zaterdag 28 september 2013 14:30
Aan: hecnet at Update.UU.SE
Beantwoorden: hecnet at Update.UU.SE
Onderwerp: Re: [HECnet] Alpha Server 1200 p/s schematics
I can't help with the schematics but I do have 2 AS1200 (aka, d|i|g|i|t|a|l
Ultimate Workstation) here in state of disrepair due to CPU/CPU fan failures.
If you want one of the P/S, make me an offer. ;)
--
VAXman- A Bored Certified VMS Kernel Mode Hacker VAXman(at)TMESIS(dot)ORG
Well I speak to machines with the voice of humanity.
On 2013-09-28 11:45, Sampsa Laine wrote:
On 28 Sep 2013, at 11:39, Johnny Billquist <bqt at softjar.se
<mailto:bqt at softjar.se>> wrote:
On 2013-09-28 11:33, Sampsa Laine wrote:
If I type the document locally and upload it via Kermit, it sort of
works.
Unfortunately it doesn't keep the ligatures which makes it more or
less useless for Arabic :)
How do you verify that it "works"? What does the document look like on
the Mac? I mean, if you really look at all the bytes. What did you use
to create it?
The letters are all there, but they're not correctly connected
(ligatures) - again, probably a Terminal.app problem, VMS is storing
them just fine.
That could be a question of fixed font width. Would they look ok if you types the same file in Terminal.app but running locally on the Mac?
I've attached two PNGs - what the correctly formatted Arabic should look
like and how Terminal.app displays it. But yeah, I don't think this is a
VMS issue, it seems to happily accept any script thrown at it :)
Even though do (to my eyes) look more like a problem with fixed width fonts, I would be very careful about what to expect when you are dealing with something coded in UTF-8 on VMS, as VMS do not really know about UTF-8, and might in fact interpret and handle your output in ways you might not want.
It would work for Hebrew though
You will most likely have similar issues with any document using any
characters beyond ASCII, since I bet you have a UTF-8 encoded Unicode
text on the Mac.
In Hebrew there are no ligatures so as long as the letters made it,
Terminal.app can't mess it up :)
No, but VMS still can.
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
What would that small element be Rok?
Van: Rok Vidmar
Verzonden: zaterdag 28 september 2013 14:24
Aan: HecNet
Beantwoorden: hecnet at Update.UU.SE
Onderwerp: Re: [HECnet] Alpha Server 1200 p/s schematics
> I' m thinking of repairing the damaged unit but need schematics for that.
In fact, you don't. Open it up, replace the electrolytes. Near them you
may find a blown small element which is not needed really.
--
Regards, Rok
On Sep 28, 2013, at 12:43 PM, Brian Hechinger <wonko at 4amlunch.net> wrote:
On Sep 28, 2013, at 8:58, Dave McGuire <mcguire at neurotica.com> wrote:
On 09/28/2013 08:42 AM, Sampsa Laine wrote:
Cool. At the moment the innd sort of distributes the uuhec.* hierarchy,
but I hate dealing with inn, the config files make me cry.
I can help with INN stuff. INN and I have...an understanding.
You and INN have a bit of a..... history. :)
That we do. ;)
-Dave
--
Dave McGuire, AK4HZ
New Kensington, PA
On Sep 28, 2013, at 8:58, Dave McGuire <mcguire at neurotica.com> wrote:
On 09/28/2013 08:42 AM, Sampsa Laine wrote:
Cool. At the moment the innd sort of distributes the uuhec.* hierarchy,
but I hate dealing with inn, the config files make me cry.
I can help with INN stuff. INN and I have...an understanding.
You and INN have a bit of a..... history. :)
Hello!
Search me. It certainly is an interesting gadget. I'd bid on it, if
those clowns, (not the seller) didn't run such an annoying site.
-----
Gregg C Levine gregg.drwho8 at gmail.com
"This signature fought the Time Wars, time and again."
On Sat, Sep 28, 2013 at 7:25 AM, Sampsa Laine <sampsa at mac.com> wrote:
Saw this whilst looking through the Vintage section on ebay:
http://www.ebay.co.uk/itm/Vintage-CHAT-Telex-Plus-Communications-Mod-3090-0…
