The details on the system's usage of Uniform Type Identifiers (UTI) comes from the discussion found the UTType.h file found in the MacOS SDKs.
As to known UTIs, they come from two sources. One source is those Apple ships with the system and the other is those exported to the system by installed applications through entries in their Info.plist files. For an example of an application's UTI exports look in the BBEdit application's bundle Info.plist file UTExportedTypeDeclarations keyed array of exported type identifier information. As to the creation of dynamic type identifiers, that too is handled by the system. Read the discussion for some of the function APIs in the UTType.h file for some of the details on dynamic type identifier creation and handling. As to what ends pushing/exporting "custom" types to the system accomplishes, at the simplest it is the means by which files/file types are associated with the application(s) that can read, manipulate, and/or write the file contents/types. Macs have been doing this since day one with type/creator codes - the UTI system is just a new and vastly improved version. On Saturday, March 7, 2020 at 10:06:43 AM UTC-8, Harvey Pikelberger wrote: [snip] > RE "*Since my system has no known Uniform Type Identifier associated with > the htaccess file extension, a dynamic type identifier is used (the dyn > domain)*" -- What's the story there? Is that something you imposed? I > don't see have no kMDItemContentType / kMDItemTypeTree for .htaccess files > on my system. > > Apparently you can push your own custom types into your system -- thought > I'm not yet sure to what end. > > -- This is the BBEdit Talk public discussion group. If you have a feature request or need technical support, please email "[email protected]" rather than posting here. Follow @bbedit on Twitter: <https://twitter.com/bbedit> --- You received this message because you are subscribed to the Google Groups "BBEdit Talk" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/bbedit/3fbd6e70-095b-476b-8a20-0791b426310f%40googlegroups.com.
