EDOBE XDOM TAKE 6 IR - PRODUCTSHEET Especificações descarregar pdf (Página 43)

CHAPTER 3: File System Access Using File and Folder objects 43

As an example, suppose you use the UNIX machine myServer for data storage. If you set up an alias share

in the root directory of

myServer, and if you set up a Windows-accessible share at share pointing to the

same data location, the path name

//myServer/share/file would work for all three platforms.

Unicode I/O

When doing file I/O, Adobe applications convert 8-bit character encoding to Unicode. By default, this

conversion process assumes that the system encoding is used (code page 1252 on Windows or Mac

Roman on Mac OS). The

encoding property of a File object returns the current encoding. You can set the

encoding property to the name of the desired encoding. The File object looks for the corresponding

encoder in the operating system to use for subsequent I/O. The name is one of the standard Internet

names that are used to describe the encoding of HTML files, such as

ASCII, X-SJIS, or ISO-8859-1. For a

complete list, see File- and Folder-supported encoding names

A special encoder,

BINARY, is provided for binary I/O. This encoder simply extends every 8-bit character it

finds to a Unicode character between 0 and 255. When using this encoder to write binary files, the encoder

writes the lower 8 bits of the Unicode character. For example, to write the Unicode character

1000, which is

0x3E8, the encoder actually writes the character 232 (0xE8).

The data of some of the common file formats (UCS-2, UCS-4, UTF-8, UTF-16) starts with a special byte order

mark (BOM) character (

\uFEFF). The File.open method reads a few bytes of a file looking for this

character. If it is found, the corresponding encoding is set automatically and the character is skipped. If

there is no BOM character at the beginning of the file,

open() reads the first 2 KB of the file and checks

whether the data might be valid UTF-8 encoded data, and if so, sets the encoding to UTF-8.

To write 16-bit Unicode files in UTF-16 format, use the encoding UCS-2. This encoding uses whatever

byte-order format the host platform supports.

When using UTF-8 encoding or 16-bit Unicode, always write the BOM character "

\uFEFF" as the first

character of the file.

File error handling

Each object has an error property. If accessing a property or calling a method causes an error, this

property contains a message describing the type of the error. On success, the property contains the empty

string. You can set the property, but setting it only causes the error message to be cleared. If a file is open,

assigning an arbitrary value to the property also resets its error flag.

For a complete list of supported error messages, see “

File access error messages” on page 44.

1 2 ... 38 39 40 41 42 43 44 45 46 47 48 ... 303 304

Sem comentários

EDOBE XDOM TAKE 6 IR - PRODUCTSHEET Especificações Página 43