denniswilliamson

I meant to say that the problem the plugin is intended to solve was addressed in issue 169 and the CVS change. The problem in this support thread is not.
With Bryce’s help, I was able to determine that the indentation was being converted to \xCA (E-circumflex) characters instead of spaces on OS X.
In order to reproduce this, I copied the text from Safari to TextEdit, set it to a Text file and saved it. In the Terminal I did xxd file.txt (hexdump) and it showed the odd characters.
I’m investigating a work around.

You can set up basic authentication so a password is required to access your test site. That might slow ’em down a bit.

The advantage to using Link Manager is that you can categorize your static pages. Using wp_list_pages() (in wp-sidebar.php, for example), lists all of them together.

For number 1, try template-functions-comments.php, line 33, in CVS.

slanted – see the first paragraph of my post here.

I have really been pleased with CrystalTech.

Definitely take a look at the tools mentioned in this entry in Carthik’s WordLog. The code browser is more fun than fireworks!

Here’s the IE7 hack referred to above.

Correction: A space is added after the separator string in the output of the function. So calling the_category(',') would display “Category1, Category2, Category3”. The space is hard-coded and can’t be over-ridden.
See this entry in the Wiki for a replacement function which allows more flexibility in the use of separators and fixes the single/multiple bug (which has been fixed in the development version on the CVS).

Online user manual?

For me, the gaps look the same in IE6 Win and FF 1.0 Preview Win (0.10.1), but in Firefox the title image is smaller in height, but the same width. I don’t see an extra tag in the source. If you want things tighter, you could set your top margins in #side and #content to 475 or 460. As you know, CSS is rendered quite differently among different browsers, different OSs and even different versions of the same browser on the same OS.

I’ve found this list of functions and the files they’re located in to be helpful. Also, depending on your environment, grep and the multi-file search feature of less can be useful. Looking at the core code can help you understand what’s going on and plugins allow you to do lots of things without modifying it. The code isn’t rich with comments, but it’s well written and easy to follow — even if it is complicated.
A good editor that highlights syntax and parentheses and bracket pairs helps a lot. I use the free Crimson Editor and there are a number of other good ones.
It sounds to me that you’re going to need to write (or find) a plugin that works on the post as it’s published to process your footnotes using the filter hook feature. As suggested above, go to the Plugins section for inspiration (and example code).
Don’t forget the support forum and the WP Hackers List.

Take a look here to see if this helps.

Have you tried entering a post directly into WP and seeing if that has the extra tags?
Other than that, one of the plugins just about has to be the one touching the post on the way in or the way out.
I don’t know.

From the WordPress readme.html file:

You can now post to your WordPress blog with tools like BlogBuddy, Bloggar, WapBlogger (post from your Wap cellphone!), Radio Userland (which means you can use Radio’s email-to-blog feature), Zempt, NewzCrawler, and other tools that support the Blogging APIs! ??

Plus, a little further down, it describes the post-by-email feature.