From mboxrd@z Thu Jan 1 00:00:00 1970 From: Eemeli Kantola Subject: Re: dosemu 1.1.5.7 (was Re: dosemu 1.1.5.6) Date: Sat, 23 Aug 2003 10:21:33 +0300 Sender: linux-msdos-owner@vger.kernel.org Message-ID: <3F4715FD.9000308@cc.hut.fi> References: Mime-Version: 1.0 Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: In-Reply-To: List-Id: Content-Type: text/plain; charset="iso-8859-1"; format="flowed" To: linux-msdos@vger.kernel.org Bart Oldeman wrote: > On Fri, 25 Jul 2003, Eemeli Kantola wrote: >=20 >=20 >>If you under win9x or unix create a text file containing intl chars, >>they appear incorrectly under dos edit, for example. This has somethi= ng >>to do with font differences between dos and windows/unix, but is anyw= ay >>the "preferred" behavior. However, windows somehow converts chars in >>file names somehow that they look the same under dos and windows. Dos= emu >>seems to know nothing about that: as an example, a file named "clich=E9= " >>is shown as "clich" (where is a single greek theta) un= der >>dosemu. >=20 >=20 > right so this problem surfaced in 1.1.5.6 since the vfat kernel drive= r > translates from codepage xxx (default=3D437) to codepage iso8859-1 an= d > 1.1.5.6 (on VFAT) doesn't mangle short filenames. >=20 > Well it turned out that this easy approach (no mangling at all on > VFAT) wasn't feasible in all cases and that with the unicode > infrastructure already there in several places it was not that hard t= o > translate filenames from the UNIX to the DOS character set now. >=20 > In my testings (and Stas' for Cyrillic) it all works so I've put up > 1.1.5.7 at http://www.dosemu.org/testing to ask for wider testing. Thanks, that seems to have fixed about every filename problem I had! - To unsubscribe from this list: send the line "unsubscribe linux-msdos" = in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html