A while back I switched to GeSHi for source code highlighting in my posts, and recently I started writing PowerShell scripts in my posts, and calmly sticking it in <code lang=“posh”> tags, half expecting it to just work, like all the other languages … but of course it didn’t. So after a few searches on Google and Ask, I concluded that a PowerShell syntax file doesn’t yet exist. So, I made one, feel free to grab it (it’s GPL, and I’ve even left intact the “any later version” clause from GeSHi’s license).
EDIT: 6/10/2007
I should mention that the way I do highlighting doesn’t care about “Nouns” at all: it just uses a list of Verbs, and matches anything that starts with a “Verb-” ... that means that for the sake of the highlighting, you can’t just say “Content” for Get-Content or (even though that actually works in a script). Also, I changed the version I was using so that it uses regular expression patters for command parameters, instead of a list. Because you can abbreviate parameters to the shortest distinguishable form, a list doesn’t really work.
Let’s just see in action, shall we? Read the rest of this entry »
EDIT I’m inserting an extra paragraph
Just to test if the textile stuff is misbehaving
Because I had an error report.
I’m releasing a new version of the WordPress Textile 2 plugin, as well as my own plugin for doing syntax highlighting with GeSHi. But I feel like I need to explain what’s going on, rather than just posting the downloads.
There are two big changes to the Textile 2 plugin. I’ve changed the way I’m distributing the plugin: instead of a single file, there are two, which must go together into a folder in your WordPress plugins directory. To simplify that I’ve packaged them as a .7z .tgz .zip which you can just unpack in the plugins folder. The reason for this change is that this allows me to distribute the unmodified classTextile.php from Dean Allen’s last textpattern release, and allows you the option of just replacing that file with the latest from the svn repository in the future.
I’ve changed the name to “TextileWrapper” to be more in line with what’s really going on. I want to make perfectly clear that I am not editing Textile at all this time. Any bugs with the way Textile work are Textile’s bugs, and should be filed via the Textile Homepage. Any bugs with the way it integrates into WordPress should be filed here. As far as the version number … Dean Allen has left Textile as “2.0 Beta” for a very long time, despite the fact that he’s on version 4.3 of Textpattern (which has been using Textile since the beggining). The internal revision number for the file has been divorced from actual revisions to Textile, because Subversion revision’s the whole project, so there’s nothing to go on there, either. At any rate, based on all that, I’ve decided to just call this version 2.8 as it’s really the next version of my “Textile 2” plugin, even though I’ve renamed it … and it really should work with any version of Textile since the first 2.0 Beta.
I finally came to my senses with this release and realized that the problem with code blocks is really not a Textile problem, but rather, a problem of the various syntax highlighters I’ve been using.
Read the rest of this entry »The purpose of ubernyms is to allow you configure a set of frequently used abbreviations that will be automatically encoded nicely whenever you use them. The goal is to make them visible in a way that is literate for both humans and computers. In other words: we tag them appropriately for your computer, and expand them as necessary for humans.
The main use for ubernyms is still going to be abbreviations, including acronyms. But you can also use it for other things like:
I’ve included a full configuration panel this time. No more hacking the plugin source to add abbreviations! Each time you go to the configuration panel there’s 5 empty slots for new definitions, and when you submit those, you get space for 5 more. You can remove definitions by simply deleting their Text or Definition. You can see a partial screenshot of the ubernyms configuration if you’re interested, but there’s not much to see besides long lists of definitions.
There’s a setting for each ubernym that lets you define if it is an acronym, an initialism, just a plain old abbreviation, or simply a replacement or link. And if you’re using the DomTT tool-tips, you can specify additional text (including HTML) to be placed below the main definition.
You can download the zip here, which includes the DomTT script which you can also get here with more details about how to use it and the many features, in case you want to play with the tool-tips. The installation is pretty simple, just unzip, and upload the whole ubernyms folder into your plugins folder.
Note that there’s now an option in the plugin configuration for including the default ubernym CSS, but you can feel free to copy that into your CSS and/or edit it as you see fit.
Incidentally, putting the photos in (as I did with my daughters) is extremely simple a?? without getting into the details of how I actually do it, all you have to do is put the img tag into the Description field, and make sure that you’ve checked the option for using the DomTT tooltips. You can use pretty much any HTML in the descriptions for DomTT, within reason
. Of course, the images have to be somewhere. You can just upload them to your webhost and link to them there, or just specify an image you already uploaded to flickr. Remember, just put the HTML in, like: <img src="http://static.flickr.com/48/136555658_f0eaa892a9_m.jpg" alt="Sitting in a field of flowers" />
I’ve just released an update of this, no major changes, but it’s now in sync with my HuddledParser plugin so that if you’re using them both, you don’t accidentally get two copies of the DomTT scripts loaded. Aren’t I clever?
I finally fixed a few annoying bugs related to having quotes, single-quotes, and apostrophes in your abbreviations and released ubernym 2.4
I tweaked the javascript and css so that it all validates as XHTML 1.0 Transitional, XHTML 1.0 Strict, or even XHTML 1.1, but the DomTT javascript still uses a CSS file with those neat rounded-corners and alpha-blending opacity, so it’s CSS won’t validate … which doesn’t really bother me.
Here’s a list of things that I still want to do: