Fossil version [d8221b9863] 2011-05-12 14:56:52 UTC on Windows 7, 64-bits.

I upgraded to the latest version (mentioned above), and did an <tt>all rebuild</tt>.  But now, fossil can no longer find any file in the current directory or below it if that directory's path contains a non-ASCII character (which it does in my main source tree).  My previous version, from about a month ago (April 2011), worked fine in that identical setup.

Here's a command line session illustrating the problem.  Notice that "Voronwë" gets mangled to "Voronw´┐¢", which looks suspiciously like converting Ansi to UTF8 once too often (topped with a CharToOem if I’m not mistaken; but hey, that's the Windows console for you).

<pre>
C:>cd
changes
SQLITE_CANTOPEN: os_win.c:33310: (3) - The system cannot find the path specified.
SQLITE_CANTOPEN: os_win.c:33310: (3) - The system cannot find the path specified.
SQLITE_CANTOPEN: cannot open file at line 33316 of [f55156c519]
unable to open database file

If you have recently updated your fossil executable, you might
need to run "fossil all rebuild" to bring the repository
schemas up to date.


changes
DELETED    src/SQL.rc
EDITED
EDITED
EDITED
EDITED


</pre>

I've set the severity to 'important' because while I can get it to work by using this workaround, this only works when using fossil from command-line.  I've integrated fossil in my IDE's tools menu, which always passes the long path.  This issue breaks this integration with my IDE.