<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=windows-1255"
http-equiv="Content-Type">
</head>
<body dir="ltr" bgcolor="#ffffff" text="#000000">
Diego Iastrubni wrote:
<blockquote cite="mid:201006192236.29794.elcuco@kde.org" type="cite">
<pre wrap="">Shachar,
On שבת 19 יוני 2010 00:08:26 Shachar Shemesh wrote:
</pre>
<blockquote type="cite">
<pre wrap="">There is no such thing "non-unicode vfat". FAT file systems comes in two
flavors. One is the classic, pre-Windows 95, version, which only
supported ASCII (no Hebrew at all). The other is the LFN extension to
FAT, which is encoded in UTF-16 (i.e. - unicode). In other words, if the
DoK has Hebrew names, they are in Unicode.
</pre>
</blockquote>
<pre wrap=""><!---->I am pretty sure I used to write in Hebrew filenames under DOS and Win3.11 (and
saw "reversed Hebrew" in my app... I had to reverse it...). When I say "pretty
sure", I tell you I wrote code myself.
Can you prove me wrong? What is missing here ? (except me being senile, that
might be true)
</pre>
</blockquote>
I may have mis-spoke. Not even all ASCII was supported. There was no
support for lower case file names, for example. All file names without
LFS were upper case. When programs not written by you (say, the
"Einstein" word processor) wanted to write Hebrew, they did all sorts
of crazy mappings on the file name to map it to something that FAT
could save.<br>
<br>
As for what you did - I have no idea what that is, so I cannot comment.
Did you ever run scandisk on your drives? Did it pass?<br>
<br>
As for references: <a class="moz-txt-link-freetext" href="http://en.wikipedia.org/wiki/8.3_filename">http://en.wikipedia.org/wiki/8.3_filename</a><br>
<br>
Shachar<br>
<br>
<pre class="moz-signature" cols="72">--
Shachar Shemesh
Lingnu Open Source Consulting Ltd.
<a class="moz-txt-link-freetext" href="http://www.lingnu.com">http://www.lingnu.com</a>
</pre>
</body>
</html>