[EMAIL PROTECTED] writes:
| [EMAIL PROTECTED] (Lars Gullik Bjnes) wrote:
|
| > | No!!! Suppose you have a 0x8f in a file name, what do you expect?
| >
| > will latex handle that char? I guess not. AND the spaceless in 1.0.4
| > and 1.1.1 had a & 0x7f
|
| I meant 0xaf which will become 0x2f "/" after applying a & 0x7f
and since "/" is one of the chars that we disallow it will be
converted to "_" (ok not currently but that takes one DEL to fix).
One other thing we ofcourse can to is to just use _ for all chars that
is not in the keep list already, and drop the 0x7f completely. That
actually has some merits...
| The reason for isalnum() in 1.0.4 and 1.1.1 was precisely to avoid such
| situation.
The problem with isalnum is that is disallows a lot of chars otherwise
perfectly ok.
| LaTeX can handle 0x8f all right if the pool file is created that way.
| There are quite a few emTeX users who configured TeX compiler for CP437
| rather than for ISO8859-X (And they are happily running TeX on file
| system of CP437 character file names.)
And we now use ascii only.
Lgb
