Date:	Tue, 30 Mar 1999 15:35:43 +0200 (IST)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender:	eliz AT is
To:	"Salvador Eduardo Tropea (SET)" <salvador AT inti DOT gov DOT ar>
cc:	djgpp AT delorie DOT com, The Ginsburgs <kartiv AT netvision DOT net DOT il>
Subject:	Re: bugs report - RHIDE
In-Reply-To:	<m10RyDv-000S7CC@inti.gov.ar>
Message-ID:	<Pine.SUN.3.91.990330153002.2067C-100000@is>
MIME-Version:	1.0
Reply-To:	djgpp AT delorie DOT com
X-Mailing-List:	djgpp AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

On Tue, 30 Mar 1999, Salvador Eduardo Tropea (SET) wrote:

> I don't recommend people to use the editor in a DOS Window. The emulation is 
> limited and is pretty buggy. Some video drivers fails to emulate a lot of 
> things and sometimes becomes unstable when the program inside the window 
> makes use of the VGA registers.

I understand.  But since Emacs doesn't use any of these tricks, and hence 
is not limited by bugs in video drivers, it made sense to me not to get 
into such problems only for the fonts.  (Of course, the fact that Emacs 
doesn't use such tricks also means that it has less features when they 
*are* supported by the hardware.)

> 1) The to upper/lower commands are sensitive to the code page (I can convert 
> russian strings to upper case ;-)

Emacs already does that for every supported charset, so this is 
something I didn't need to bother about at all.  Since the codepage 
support simply translates DOS codes into ISO codes, the characters in the 
buffer are in ISO encoding, and thus the upper/lower-case conversion 
works as if Emacs were running on Unix.

> 2) The "HTML accents convertion" command is sensitive to the code page too.

Ditto.  All text conversions in the DJGPP port of Emacs know about the 
current codepage.

- Raw text -