How do I create a "vanilla .tnt file without keymapping"? I set the original one up so long ago that I forgot how I did it.
'File->New Connection File'
Then, only set your hostname and basic options to get the connection going. Don't do any keymapping (yet).
However, I suspect that your problem with the arrow keys is related to the 7/8 bit output option. On linux, you should really have the terminal set to send 7-bit control sequences. Is this how it's set?
Brian
I don't know how it's set on my Linux shell account. I never bothered with it and am not really a Linux whiz. However, after setting the output option to 7-bit, the arrow keys seems to be working again. As I mentioned in email, that is OK provided I can get 8-bit text characters. I really need ISO-8859-x character sets. Not all the world speaks English.
I just remembered something from a few minutes after I made my earlier reply. I mentioned early in the thread that I had had to adjust some of my keymappings from (no quotes) "some_text\\x0d0a" to "some_text\\x0d\\x0a". Actually I had to make one further adjustment. Sending both the MS-style CrLf pair to Linux, as I did with A.T.3.50. worked. Suddenly Linux was interpreting an extra newline, so I changed the mappings to just "some_text\\x0d". I don't remember (it's been a long day) whether I had to make the additional adjustment after going to 7-bit output.
Paul,
AbsoluteTelnet can definitely interpret the 8859-x character sets, but *only* one at a time. On the Options->Properties->Appearance menu, there is an option for 'Translation' where this is set.
The trick is that in programs like Pine, you never know what character set data may be coming across. Different messages can be in different character sets. Since Absolute can only interpret one, data sent in any other format will display incorrectly.
There *is* a UTF8 patch to pine that will allow pine to operate in UTF8 mode. AbsoluteTelnet 'translation' setting can then be set to UTF8 and Pine will convert any non-UTF8 data to UTF8 on the fly.
[url= http://www.suse.de/~bk/pine/iconv/FAQ.html ]http://www.suse.de/~bk/pine/iconv/FAQ.html[/url]
You *have* to give it a try.
Well, as I mentioned in email, the Pine I use is provided by and under the control of my ISP. They do not even have the latest version. So I'm kind of stuck. I am seeing the ISO-8859-x characters OK, but UTF-8 usually comes out as a jumble. I can suggest to the ISP that they upgrade Pine, but I won't hold my breath. (And what vefrsion of Pine does th patch apply to?)
If you have Options->Properties->Appearance->Translation set to 8859-1, then the UTF8 data has no choice put to look like crap. By switching the translation setting in Absolute to UTF8, the UTF8 mails will look good, but then your 8859-1 encoded mails will look like crap.
That's the purpose of the patch... to put the work of doing the conversion on pine and not the client. As long as the client and interpret UTF8 (a superset of all other encodings), any encoding can be converted (by pine) and displayed (by Absolute) properly.
I'm running pine 4.58 with the patch. I think they have since modified the patch to be compatible with Pine 4.61 as well. You might ask your ISP if they've already applied it. You *may* just have to enable it. I can't remember right off if there's an option to look for that would tell you that it's there.
Brian
