ios 捆绑创建者操作系统类型代码？？？在 Xcode 4
声明：本页面是StackOverFlow热门问题的中英对照翻译，遵循CC BY-SA 4.0协议，如果您需要使用它，必须同样遵循CC BY-SA许可，注明原文地址和作者信息，同时你必须将它归于原作者（不是我）：StackOverFlow
原文地址: http://stackoverflow.com/questions/5401208/
Warning: these are provided under cc-by-sa 4.0 license. You are free to use/share it, But you must attribute it to the original authors (not me):
StackOverFlow
Bundle creator OS Type code ??? in Xcode 4
提问by moon
I just realized that Bundle Creator OS Type codein my iOS app's Info.plistvalue is ?????in Xcode 4. What is the value supposed to be?
我刚刚意识到我的 iOS 应用程序值中的Bundle Creator OS Type 代码在 Xcode 4 中。该值应该是多少？Info.plist?????
采纳答案by Nevin
It's used to identify your application. You don't have to change it for an iPhone application.
它用于识别您的应用程序。您不必为 iPhone 应用程序更改它。
Take a look at these links:
看看这些链接：
回答by uchuugaka
It's not really used anymore. It's a holdover from the Classic Mac OS days when it was a datapoint used mainly to determine what apps could create or edit or read file types. Back then you had to register them with Apple. I don't think they even provide that service any more. OS X and some apps might still use it in rare cases under the hood but its very legacy. As you can imagine, the severely limited possible permutations made it untenable long term.
它不再真正使用了。它是经典 Mac OS 时代的延续，当时它是一个数据点，主要用于确定哪些应用程序可以创建、编辑或读取文件类型。那时你必须在 Apple 注册它们。我认为他们甚至不再提供这种服务。在极少数情况下，OS X 和一些应用程序可能仍会在幕后使用它，但它是非常传统的。可以想象，极其有限的可能排列使其长期站不住脚。
UTIs are the preferred approach now. The system then uses a combination of these and file extensions and magic numbers. Though on ios that may not be true as much as OSX.
UTI 是现在的首选方法。系统然后使用这些和文件扩展名和幻数的组合。虽然在 ios 上可能不像 OSX 那样真实。
回答by Chandan Shetty SP
It is just the four letter code to identify the bunder creator... for example for apple it is APPL... It can be ???? or if your app name is "myApp" you can give "MYAP"... If you have many apps you can give first 2 characters with your app name and next 2 characters with company name...
它只是识别绑定创建者的四个字母代码......例如对于苹果来说它是APPL......它可以是???? 或者如果您的应用程序名称是“myApp”，您可以提供“MYAP”...如果您有很多应用程序，您可以提供应用程序名称的前 2 个字符和公司名称的后 2 个字符...
For example apple uses CF for core foundation, AV etc
例如苹果使用CF作为核心基础，AV等
回答by Eric
Just to give the historical perspective on extensions and file type and creator codes.
只是为了提供有关扩展名、文件类型和创建者代码的历史观点。
File extensions were part of the file system in CP/M and were intended to function something like what file types and creator codes actually did in MacOS. At the time, it was expected that each application would use a unique extension and only the one application would ever edit its own files. In the file system, the file name and extension were stored in two different areas, so the extension was not part of the name. Remember, at that time most systems had only a few applications, and file contents were specific to an application. They were never intended to be visible to end users, but due to an error in the directory command in CP/M, they were shown displayed as if they were part of the file name. MS-DOS picked up the convention, and the rest, unfortunately is history.
文件扩展名是 CP/M 中文件系统的一部分，其功能类似于 MacOS 中的文件类型和创建者代码。当时，预计每个应用程序都将使用唯一的扩展名，并且只有一个应用程序会编辑自己的文件。在文件系统中，文件名和扩展名存储在两个不同的区域，因此扩展名不是名称的一部分。请记住，当时大多数系统只有几个应用程序，并且文件内容是特定于应用程序的。它们从未打算对最终用户可见，但由于 CP/M 中的目录命令中的错误，它们被显示为好像它们是文件名的一部分。MS-DOS 接受了这个惯例，其余的不幸成为历史。
Apple's initial file system design saw the shortcomings of the extension concept, the primary one being that some file types were likely to be used by more than one application and with standardization of file formats, having more than one application that could operate on a file would be common. Therefore Apple split the file creator - the app that created the file - from the file type. By default if a file was double clicked, the originally creating application would open it. However, if a user did a file open from within an application, then all compatible files were supposed to be listed, even if that app was not the creator. Also, it would be possible to list all the applications that could open a file. Semantically, as intended in CP/M, the type and creator codes were separate from the file name itself.
Apple 最初的文件系统设计看到了扩展概念的缺点，主要的缺点是某些文件类型可能被多个应用程序使用，并且随着文件格式的标准化，有多个应用程序可以对文件进行操作常见。因此，Apple 将文件创建者——创建文件的应用——从文件类型中分离出来。默认情况下，如果双击文件，最初创建的应用程序将打开它。但是，如果用户从应用程序中打开文件，则应该列出所有兼容的文件，即使该应用程序不是创建者。此外，还可以列出所有可以打开文件的应用程序。在语义上，正如 CP/M 中所预期的那样，类型和创建者代码与文件名本身是分开的。
Developers that properly registered their applications with Apple got their own creator codes. The problems with this concept came about from two sources: 1. Developers that hiHymaned other's or Apples own creator codes. 2. Unix systems, which never had a formal filename extension (all file names were a single string) began adopting the convention to end the file name with a dot and some additional letters to indicate file type. In the Unix convention, the extension is part of the file name itself, unlike CP/M and MS-DOS.
向 Apple 正确注册其应用程序的开发人员获得了自己的创建者代码。这个概念的问题来自两个来源： 1. 劫持他人或苹果自己的创建者代码的开发人员。2. Unix 系统，从来没有正式的文件扩展名（所有文件名都是一个字符串）开始采用约定以点结束文件名和一些额外的字母来表示文件类型。在 Unix 约定中，扩展名是文件名本身的一部分，与 CP/M 和 MS-DOS 不同。
