Here are some questions I expect to get.

1. How will I know when a new version is released?

Some day google code will have RSS feeds, but until then your best bet is to subscribe to the QLColorCode RSS feed on my blog. You can do this in Mail.app, for example. You can also use the RSS FWD service to have that feed forwarded to you as e-mail if you're not hot on RSS (but really, you should be).

2. Why doesn't it highlight my Bozoscript .bozo files?

The plugin tells the system, "I can display anything of type public.source-code" but it's up to the system to figure out what extensions, mime-types, and such have that type. For extensions like .c or .py the system already knows that they're source code, but for .bozo and other "exotic" file types somebody needs to tell it. I've included a few random "interesting" file types in the Info.plist file in the plugin's bundle to take care of this, but it's probably not wise to include everything that Highlight can handle. Why not? Well, if two different entities make conflicting claims on a given file extension then only one of them can win. For the gritty details, see Apple's UTI docs and this message.

3. How can I figure out what QL plugin is being used for a file?

You can use the qlmanage tool to figure out what type the OS thinks a given file is and what generator it uses for it. Here's an example:

[n8gray@golux]% qlmanage -p Notes.txt 2>&1 | grep 'Generator used'
2008-01-07 13:50:57.476 qlmanage[56917:5f03] [QL] Previewing /Users/n8gray/src/flickr/Notes.txt. Content type UTI: public.plain-text. 
Generator used: <QLGenerator /System/Library/Frameworks/QuickLook.framework/Resources/Generators/Text.qlgenerator>

4. Can you add support for Bozoscript?

If it's supported by Highlight then the answer is probably yes. If it's not supported by highlight then the answer is also probably yes, but only if you're willing to write the highlight support. Assuming the language is supported by highlight, I'll need some info about the language in order to create a Universal Type Identifier for it:

1. The name of the language
2. The file extension(s) it uses
3. The website of the organization in charge of the language (if possible)
4. (optional but potentially very helpful) The Info.plist file from a major Mac software package that handles files of this language.

Once you've got that information, mosy on over to the Issues page and file an issue. That is the highly preferred way for you to make new language requests. If you send them as e-mail, leave them as comments on my blog, or leave them in other random places there's a much higher chance I'll overlook or forget about them.

5. I thought QLColorCode used Pygments as its highlighting engine.

Sorry, that's not a question. :-) Actually, it did use Pygments, but now it uses Highlight. Pygments is a nice project, but the Highlight engine is about 10x faster and supports more languages. One nice aspect of QLColorCode's design is that the highlighting engine can be swapped out quite easily if something better comes along.

6. This is awful! How do I uninstall QLColorCode?

Just drag the bundle from ~/Library/QuickLook or /Library/QuickLook into the trash.