On Fri, 25 Jul 2003, Eemeli Kantola wrote: > If you under win9x or unix create a text file containing intl chars, > they appear incorrectly under dos edit, for example. This has something > to do with font differences between dos and windows/unix, but is anyway > the "preferred" behavior. However, windows somehow converts chars in > file names somehow that they look the same under dos and windows. Dosemu > seems to know nothing about that: as an example, a file named "cliché" > is shown as "clich<theta>" (where <theta> is a single greek theta) under > dosemu.
right so this problem surfaced in 1.1.5.6 since the vfat kernel driver translates from codepage xxx (default=437) to codepage iso8859-1 and 1.1.5.6 (on VFAT) doesn't mangle short filenames. 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 to translate filenames from the UNIX to the DOS character set now. 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. We'll try to fix the LD_ASSUME_KERNEL and RH 9 issues for 1.1.5.8. Also in 1.1.5.7: * should fix the attribute (color) problems reported by Bernhard Bialas * DPMI was improved at several places; now it runs Windows 3.1 with os2win31.zip again. * some smaller fixes Bart - To unsubscribe from this list: send the line "unsubscribe linux-msdos" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
