|
|
You have to create this UTI.
If CoreTypes doesn't recognize some type you have to create the definition yourself. In fact you may modify Info.plist of _any_ Cocoa application and it will work just fine. But this is definitely not a clean way to solve the problem in general, so I've created a Cocoa bundle which has the only purpose - export my UTIs to system. You may download it and unpack to your Application folder:
You have to create this UTI.
I downloaded your bundle and modified the info.plist to include VBS scripts files I have backed up from my XP Desktop. See below for the contents of my updated info.plist file.
Once that was done, I went into the folder with my .VBS files and ran, "mdimport -d1 ." The files are still showing up as having no mdimporter. Is there something else I need to do? Any help you can give would be appreciated :)
You have to create this UTI.
I forget to mention, I also followed the steps in the first comment and updated the /System/Library/Spotlight/RichText.mdimporter/Contents/Info.plist and added a new string, com.biapo.vbs-script in the LSItemContentTypes: section.
You have to create this UTI.
Are they reported as com.biapo.vbs-script now? If so you have to use the original hint to update Info.plist in RTF mdimporter. If they still reported as dyn.** I don't know. It works for me.
You have to create this UTI.
They are still showing up as dyn.*. I logged out, moved the application out and back into the Applications folder and same thing.
Re: You have to create this UTI.
You sometimes have to move an app out of /Applications (e.g., to the Desktop) and then back into /Applications, or logout, in order for LaunchServices to pick up any user-generated changes to Info.plist. Perhaps that's the problem with mdimport and UTI types, too.
Re: You have to create this UTI.
I think this is it, but the problems is that simple moving a bundle between directories doesn't always update the internal UTIs database (or whatever it is). The only reliable way I could find is to create an archive of the bundle (right click, create archive f.e.), then remove the bundle and empty trash, then unpack the archive back. Looks like LaunchServices cares only about creation and removal of an object and ignoring it's modifications.
Re: You have to create this UTI.
You could always take the brute force method of deleting the launch services cache remembering that this will reset a lot of user remembered details with regards to opening/launching applications:
|
SearchFrom our Sponsor...Latest Mountain Lion HintsWhat's New:HintsNo new hintsComments last 2 daysNo new commentsLinks last 2 weeksNo recent new linksWhat's New in the Forums?
Hints by TopicNews from Macworld
From Our Sponsors |
|
Copyright © 2014 IDG Consumer & SMB (Privacy Policy) Contact Us All trademarks and copyrights on this page are owned by their respective owners. |
Visit other IDG sites: |
|
|
|
Created this page in 0.42 seconds |
|