Adaptec 5325301656 Administration Guide - Page 140

ISO-8859-1, EUC-JP, and UTF8., The Snap Server then must

Get Adaptec 5325301656 - Snap Server 14000 NAS PDF manuals and user guides
UPC - 753253016563
View all Adaptec 5325301656 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 140 highlights

Unicode and Protocol Interaction filename; for example, you might see {!^AB in a file name. MacOSX clients can edit such files, and the names will be retained in their original form when written back to the file system. MacOS 9 and lower are not Unicode-compliant, and use the MacRoman code page to represent extended characters. AFP translates MacRoman into UTF8 when writing to Snap Servers. Any extended characters on the file system that cannot be translated to MacRoman will also be returned with an escape sequence. NFS The NFS protocol is not Unicode-compliant or -aware. Addtionally, there is no means for the Snap Server to determine what method is being used by the client to represent extended characters. Currently, the code pages most commonly used in Linux environments are: 8859-1, 8859-15, and EUC-JP. The Snap Server then must make an assumption to enable it to translate to and from UTF8 on the file system. Therefore, when in Unicode mode, you must configure the Snap Server's NFS protocol for the code page being used by NFS clients. Code page options include ISO-8859-1, ISO-8859-15, EUC-JP, and UTF8. Any extended characters on the file system that cannot be translated to the configured NFS code page will be returned to the NFS client with an escape sequence. Escape sequences begin with {!^. The following two characters are the hexidecimal value of the characters in the filename; for example, you might see {!^AB in a file name. FTP FTP only supports ASCII characters by specification. Some clients bend the specification to allow extended characters, but there is no standard means of representing them. Therefore, no translation is performed on extended characters for FTP clients - all filenames are written to and read from the file system as a "bag-of-bytes". This has two ramifications: extended characters written to the file system by other protocols will be visible to FTP clients as garbled characters; and FTP clients are able to write invalid UTF8 characters to the file system. For the latter case, when other protocols encounter invalid UTF8 characters on the file system (which normally can only be written by FTP), the characters will be returned in an escape sequence. Escape sequences begin with {!^. The following two characters are the hexidecimal value of the characters in the filename; for example, you might see {!^AB in a file name. 126 Snap Server Administrator Guide

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
Unicode and Protocol Interaction
126
Snap Server Administrator Guide
filename; for example, you might see
{!^AB
in a file name. MacOSX clients can edit
such files, and the names will be retained in their original form when written back
to the file system.
MacOS 9 and lower are not Unicode-compliant, and use the MacRoman code page
to represent extended characters. AFP translates MacRoman into UTF8 when
writing to Snap Servers. Any extended characters on the file system that cannot be
translated to MacRoman will also be returned with an escape sequence.
NFS
The NFS protocol is not Unicode-compliant or -aware. Addtionally, there is no
means for the Snap Server to determine what method is being used by the client to
represent extended characters. Currently, the code pages most commonly used in
Linux environments are: 8859-1, 8859-15, and EUC-JP.
The Snap Server then must
make an assumption to enable it to translate to and from UTF8 on the file system.
Therefore, when in Unicode mode, you must configure the Snap Server’s NFS
protocol for the code page being used by NFS clients. Code page options include
ISO-8859-1, ISO-8859-15, EUC-JP, and UTF8.
Any extended characters on the file system that cannot be translated to the
configured NFS code page will be returned to the NFS client with an escape
sequence. Escape sequences begin with
{!^.
The following two characters are the
hexidecimal value of the characters in the filename; for example, you might see
{!^AB
in a file name.
FTP
FTP only supports ASCII characters by specification. Some clients bend the
specification to allow extended characters, but there is no standard means of
representing them. Therefore, no translation is performed on extended characters
for FTP clients — all filenames are written to and read from the file system as a
“bag-of-bytes”. This has two ramifications: extended characters written to the file
system by other protocols will be visible to FTP clients as garbled characters; and
FTP clients are able to write invalid UTF8 characters to the file system. For the latter
case, when other protocols encounter invalid UTF8 characters on the file system
(which normally can only be written by FTP), the characters will be returned in an
escape sequence. Escape sequences begin with
{!^.
The following two characters are
the hexidecimal value of the characters in the filename; for example, you might see
{!^AB
in a file name.