Base filetypes

The base Perforce file types are:

Keyword	Description	Comments	Stored as
`text`	Text file	Synced as text in the workspace. Line-ending translations are performed automatically.	deltas in RCS format
`binary`	Non-text file	Synced as binary files in the workspace. Stored compressed within the depot.	full file, compressed
`symlink`	Symbolic link	Helix Server applications on UNIX, OS X, recent versions of Windows treat these files as symbolic links. On other platforms, these files appear as (small) text files. On Windows, you require `admin` privileges or an appropriate group policy must be set, otherwise, you get text files.	deltas in RCS format
`unicode`	Unicode file	Services operating in unicode mode support the `unicode` file type. These files are translated into the local character set specified by `P4CHARSET`. Line-ending translations are performed automatically. Services not in unicode mode do not support the `unicode` file type. For details, see the Internationalization Notes.	RCS deltas in UTF-8 format
`utf8`	Unicode file	Synced in the client workspace with the UTF-8 BOM (byte order mark). Whether the service is in unicode mode or not, files are transferred as UTF-8 in the client workspace. Line-ending translations are performed automatically. For details, see the Internationalization Notes.	RCS deltas in UTF-8 format without the UTF-8 BOM (byte order mark).
`utf16`	Unicode file	Whether the service is in unicode mode or not, files are transferred as UTF-8, and translated to UTF-16 (with byte order mark, in the byte order appropriate for the user’s machine) in the client workspace. Line-ending translations are performed automatically. For details, see the Internationalization Notes.	RCS deltas in UTF-8 format