FWIW: It is my understanding that UTIs are derived from domain names as defined
in RFC 1035 (relevant portion quoted below). Nevertheless, as already quoted in
a previous post it is best to use the “Testing for Equality and Conformance”
APIs or the NSWorkspace’s function type(String,
> On Mar 2, 2017, at 2:38 PM, Daryle Walker wrote:
>
> I’m trying out my document-based Mac app’s data-read routine, and the code it
> being skipped. I actually check the typeName (i.e. the UTI) and it doesn’t
> match. My bundle identifier for the app has capital letters. I
On Mar 2, 2017, at 13:43 , Thaddeus Cooper wrote:
>
> Specifically the section titled "Testing for Equality and Conformance."
I agree with your and Ben’s advice to use UTI-specific equality and conformance
testing, but I’d point out that this doesn’t actually resolve
The Apple documentation is pretty good about describing how to determine if two
UTIs are equal. See the documentation here:
On Mar 2, 2017, at 11:38 , Daryle Walker wrote:
>
> I’m trying out my document-based Mac app’s data-read routine, and the code it
> being skipped. I actually check the typeName (i.e. the UTI) and it doesn’t
> match. My bundle identifier for the app has capital letters. I base
> On 02 Mar 2017, at 11:38 am, Daryle Walker wrote:
>
> Turns out that the system gives me the UTI in all small letters, so my
> (Swift) “switch” fails and my no-matching-type code is executed. I know I
> could switch my bundle ID to all small letters, but I want to know
I’m trying out my document-based Mac app’s data-read routine, and the code it
being skipped. I actually check the typeName (i.e. the UTI) and it doesn’t
match. My bundle identifier for the app has capital letters. I base my
document’s main type off that identifier, so it also has capital