#1313 [file] fails on some files with non-ASCII characters in thei

obsolete: 8.2
closed-invalid
Jeffrey Hobbs
5
2001-08-22
2000-10-26
Anonymous
No

OriginalBugID: 4801 Bug
Version: 8.2
SubmitDate: '2000-04-03'
LastModified: '2000-04-17'
Severity: CRIT
Status: UnAssn
Submitter: techsupp
ChangedBy: hershey
OS: Windows 98
FixedDate: '2000-10-25'
ClosedDate: '2000-10-25'

Name:
Chris Nelson

ReproducibleScript:
On an NT system, do

set fname "file\u008a"
set fid [open $fname w]
close $fid

On a Spanish W98 system, in the same directory, do:

set fname "file\u008a"
file exists $fname

It returns 0 but [glob file*] shows the file.

ObservedBehavior:
fileexists can't find the file.

DesiredBehavior:
file exists finds the file

Discussion

  • Jeffrey Hobbs
    Jeffrey Hobbs
    2001-08-07

    • assigned_to: nobody --> hobbs
     
  • Vince Darley
    Vince Darley
    2001-08-16

    Logged In: YES
    user_id=32170

    This needs debugging by someone with access to Win98 and a
    debugger. Purely on WinNT there is no problem.

    To the reporter of this bug: on Win98 what does 'file
    exists [lindex [glob file*] 0]' return? if 'fname' is
    file\u008a, what exactly is [lindex [glob file*] 0]?

     
  • Logged In: YES
    user_id=107514

    I just tried this again to answer Vincent's question.

    1) The Spanish is a red herring; I was able to reproduce the problem on a normal, English W98 system.

    2) From

    file exists [lindex [glob file*] 0]

    I get 1. glob reports something like:

    file~D8

    but fname is puts'd as:

    file?

     
  • Jeffrey Hobbs
    Jeffrey Hobbs
    2001-08-22

    • status: open --> closed-invalid
     
  • Jeffrey Hobbs
    Jeffrey Hobbs
    2001-08-22

    Logged In: YES
    user_id=72656

    Hmmm, well Win9*/ME doesn't handle i18n in the same way
    (I'm not even sure what capabilities they really have at
    the fs level). I tried this on Win98, and I wasn't even
    able to create a file called file\u008a. However, I am
    able to create other weird files. Going further, Win9*
    doesn't seem to be able to operate on \u008a being in the
    file at all (try it with Explorer or Notepad). This seems
    to be a file system limitation, not a bug in Tcl.