不同的文件格式以不同方式存储-DifferentFileFormatsarestoreddifferently

There's a fundamental difference in the way that bytes and characters are stored. See:

字节和字符的存储方式存在根本区别。看到:

http://www.joelonsoftware.com/articles/Unicode.html

for a description of various character sets and how they differ between various operating system (plus a whole lot more).

用于描述各种字符集以及它们在各种操作系统之间的区别(加上更多)。

Java Class files are binary and always stored in Big Endian. This means that no matter what operating system they are moved between they will always be the same.

Java类文件是二进制文件,始终存储在Big Endian中。这意味着无论在哪个操作系统之间移动,它们都将始终相同。

File Storage is not OS independant, even though the contents may be the same, the way it is interpreted is different. A point in case is many years ago I had to port (Business Basic) programs and data from a Datageneral minicomputer to DOS. The files came across with 8bit encoding and had to be translated (to 7 bit) before it could be "understood" on DOS.

文件存储不是OS独立的,即使内容可能相同,它的解释方式也不同。一个案例就是多年前我不得不将(商业基础)程序和数据从Datageneral小型机移植到DOS。这些文件遇到了8位编码,必须先翻译成7位才能在DOS上“理解”。

Short answer: it depends.

简短的回答:这取决于。

Text files do not change by themselves when moved from DOS to Unix: Try moving them using a USB key for instance.

从DOS移动到Unix时,文本文件不会自行更改:例如,尝试使用USB密钥移动它们。

They may change when copied using a thrid party software: ftp has an option to handle text conversions.

使用第三方软件复制时,它们可能会发生变化:ftp可以选择处理文本转换。

Moreover, this depends not only on OS but also on filesystem. On pre OS X macs (HFS filesystem), files were stored on two forks: data and resources. When copied on a filesystem without fork concept, file could be copied as a single file containing both data and resource forks (AppleSingle) or as two files in two separate directories (AppleDouble).

而且,这不仅取决于操作系统,还取决于文件系统。在OS X之前的Mac(HFS文件系统)上,文件存储在两个分支上:数据和资源。在没有fork概念的文件系统上复制时,可以将文件复制为包含数据和资源分支(AppleSingle)的单个文件,也可以将文件复制为两个单独目录(AppleDouble)中的两个文件。

There are two differences:

有两点不同:

Newlines

• Unix: \n
• Mac OS before X: \r

X之前的Mac OS:\ r \ n

• Windows: \r\n

Little/big endianness

The edianess might be different, but this does often only matter for unicode and binary data.

edianess可能不同,但这通常只对unicode和二进制数据有用。

No, files do not change. Only the conventions for editing them.

不,文件不会改变。只有编辑它们的约定。

What can change is the filesystem structure and metadata used to catalogue and list directories etc (ie; timestamps). Also files will naturally be encrypted on an encrypted filesystem but filesystem complexities are nearly always transparent to an application reading the file through system calls (they would be relevant if you were writing a partition resizer or other low-level disk tool).

可以改变的是用于编目和列出目录等的文件系统结构和元数据(即;时间戳)。此外,文件自然会在加密文件系统上加密,但文件系统的复杂性对于通过系统调用读取文件的应用程序几乎总是透明的(如果您正在编写分区大小调整器或其他低级磁盘工具,它们将是相关的)。

To clarify, there is nothing in the linux OS that requires vim or emacs to use the unix convention. In fact many editors and applications can detect the newline encoding and adapt. It's up to the software how to treat files, not the OS.

为了澄清,linux操作系统中没有任何内容需要vim或emacs来使用unix约定。实际上,许多编辑器和应用程序可以检测换行编码并进行调整。这取决于软件如何处理文件,而不是操作系统。

In general the filesystem will store the file the way it was asked to write it. The program that reads the file will interpret the bytes from the file.

通常,文件系统将按照要求写入文件的方式存储文件。读取文件的程序将解释文件中的字节。

For example, in DOS (and Windows) the newline consists of two bytes, but on Unix it's only one byte. But this is only an standard. Programs on Unix can read files with two-byte newlines. These programs just need to know how what the newlines are.

例如,在DOS(和Windows)中,换行符包含两个字节,但在Unix上它只有一个字节。但这只是一个标准。 Unix上的程序可以读取具有双字节换行符的文件。这些程序只需知道新行是什么。