X-Authentication-Warning: delorie.com: mailnull set sender to djgpp-bounces using -f From: "Thomas Mueller" Newsgroups: comp.os.msdos.djgpp Subject: Re: GNU Emacs DOS (DJGPP) port converts upper-ASCII characters to ASCII 127 Date: 13 Feb 2002 10:21:46 GMT Lines: 45 Message-ID: References: <3791-Sat09Feb2002145347+0200-eliz AT is DOT elta DOT co DOT il> NNTP-Posting-Host: dial3-100.bluegrass.net (208.147.34.100) Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Trace: fu-berlin.de 1013595706 47473174 208.147.34.100 (16 [49635]) X-Mailer: NOS-BOX 2.05 To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com from Eli Zaretskii > and my previous post >> : >> I thought the newest DOS version available for download was 20.5 >Emacs 21.1 was released several months ago. I didn't release its >DJGPP port because I wasn't sure it was stable enough (the N.0 >version problem). However, anyone can download the official GNU >distribution from ftp.gnu.org and build it with DJGPP. The DJGPP >build is supported right out of the box, just read the file INSTALL >for instructions. I guess I could, when ready, download Emacs source and build for DOS, Linux and NetBSD from the same source? I am also interested in vim updates to see if the updates fix bugs in the DOS port. Maybe Lynx too. >> If you read all your email in DOS Emacs, what do you use to send and receive >> email? >Emacs, of course ;-) I was wondering how Emacs Internet capabilities would work with DOS packet drivers such as DOSPPPD (EPPPD) and LSPPP. Besides feedmail and Blat, there is GNUS, and I notice some others in message header lines. >> Next time I find a Korean spam, or maybe there's one I missed in prescreening, >> I'll take a look, just for curiosity, to see what it looks like in DOS Emacs. >Don't hold your breath: Korean characters can only be seen on Korean >DOS/Windows systems. I tried viewing the Korean spams in Emacs with --unibyte switch, just to see what would show. Naturally I didn't expect to see actual Korean characters. I also viewed the HELLO file in Emacs with and without --unibyte, and also in Tiny Editor (DOS-based and also a 16-bit OS/2 version). Emacs with --unibyte showed ^[ in some places, where Tiny Editor showed left-arrow, indicating ASCII 27, suggesting an ANSI escape sequence. DOS and OS/2 support ANSI, but such support is a small shadow of what Linux supports. Korean spams didn't contain any left-arrow (ASCII 27) characters, as I saw viewing with Tiny Editor. Since I might want to view the same file in another environment or configuration, I don't want Emacs to permanently convert characters in strange character sets to ASCII 127 and save that way if I edit the file.