Bart Oldeman wrote:
> Hi,
>
> I've put up a dosemu 1.1.5.6 for testing to fix some (but not all) of the
> problems with 1.1.5.5.
[...]
> * lots of LFN fixes
This new patch spawned an evil problem regarding LFN and international
characters: if I have a file/dir with a long name with intl chars in it,
I can't access that (ie. File not found) anymore, even though it is seen
in dir listing. The worst thing is that this is also the case with LFN
support disabled. I tested with 1.1.5.5 too, and it doesn't have that bug.
Other than that, there seem to be several problems with file names
containing international chars, which make them practically unusable. I
tested both 1.1.5.5 and 1.1.5.6 with LFN and intl chars under dos 7.10
command.com and 4dos 6.22. Nobody seems to have reported bugs on this,
so here are some:
- I can't create files with intl chars in the name.
- Intl chars show up in names incorrectly.
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.
Without LFN, dosemu just leaves out the international chars and mangles
the name ("clich~bc"), which is fine as long as the files are
accessible. I was able to live with these things in 1.1.5.5, but not
1.1.5.6.
-Eemeli
-
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
