SFM Converts Macintosh HFS Filenames to NTFS Unicode

This article was previously published under Q117258
This article has been archived. It is offered "as is" and will no longer be updated.
SUMMARY
Microsoft Windows NT Services for Macintosh (SFM) makes it possible forMacintosh clients to create filenames on SFM server volumes that appear tocontain characters that are illegal in NTFS filenames, but are legalcharacters in Macintosh HFS filenames. These include the (ANSI) characters0x01-0x1F and " * / \ < > ? | .
MORE INFORMATION
Because NTFS is Unicode-based, when a Macintosh client creates a filenameon an SFM volume, it must be converted from Macintosh ANSI to Unicode bySFM before being passed to NTFS. Because SFM does the conversion, it candefine Unicode values that invalid NTFS characters will map to. It does soby using the Private Use Area range of the Unicode standard.

The following list describes the Unicode character values that can be usedin NTFS filenames created by Windows NT applications that, when viewed byMacintosh clients, will appear as the equivalent Macintosh ANSI "invalid"NTFS filename characters:

   Macintosh ANSI  Unicode   -----------------------------   0x01-0x1F       0xF001-0xF01F   "               0xF020   *               0xF021   /               0xF022   <               0xF023   >               0xF024   ?               0xF025   \               0xF026   |               0xF027				


In addition, the following three characters are also mapped to the UnicodePrivate Use Area:

   Macintosh ANSI                                                  Unicode   -----------------------------------------------------------------------   Space (0x20)                                                     0xF028   only if occurring as the last character of the name				


   Period (0x2E)                                                    0xF029   only if occurring as the last character of the name				


   Apple's apple logo character (0xF0)                              0xF02A				


A space or a period at the end of a filename is not legal in the Win32name space, but is common in Macintosh file naming practice. Hence, theseare mapped to alternate Unicode characters by SFM so that they areaccessible by File Manager and other Win32 applications. There is noUnicode equivalent of Apple's apple logo character, therefore it too ismapped to the Private Use Area.

Note: Remember that any unicode mapping done on a filename will make thatfile inaccessible to windows 95 on other windows clients since only NTsupports unicode
prodnt
Properties

Article ID: 117258 - Last Review: 02/24/2014 08:18:29 - Revision: 2.1

  • Microsoft Windows NT Server 3.5
  • Microsoft Windows NT Server 3.51
  • Microsoft Windows NT Server 4.0 Standard Edition
  • kbnosurvey kbarchive kbinterop KB117258
Feedback