Categories
Technology Web

First, let’s fire the boy-racer HTML programmers

Recovered from the Wayback Machine.

Joe Clark, author of Building Accessible Webs in a Jonathon Delacour interview:

 

And of course we’ll also have to fire the boy racers’ clueless Dockers-wearing manager dweebs, who consider themselves old-timers because they got online in 1998 (!) and whose entire experience of the Internet is the commercial Web as rendered through Internet Explorer for Windows. These people cannot even *spell* “W3C” and still think banner ads have not been given a fair shake.

Boy racers and clueless Dockers-wearing managers, beware!

(And will Jonathon ask the question we’re dying to know: Does Joe use a Dishmatique?)

Categories
Technology

Office and XML

Recovered from the Wayback Machine.

Sam Ruby has an interesting thread going about Microsoft’s next version of Office and its support for XML:

 

On one side, the ability of MS tools to adapt to formats that users can describe will be an incredible step forward. On the other hand, this doesn’t explain an unwillingness to working with others to describe the semantics that PowerPoint 11 uses to capture a pie chart.

Interesting thread and comments. However, I’m also linking to this post in case Sam’s comments run out; the interested parties can then come over here and use the comments attached to this posting. I’m providing a Weblogger Comment Overflow Buffer.

Always a good neighbor.

Categories
Web

Accessible web pages

Recovered from the Wayback Machine.

Jonathon Delacour is reviewing Joe Clark’s Building Accessible Web Sites. In addition, he interviewed Joe and will be posting results of the interview over the next few days. This promises to be excellent reading, and I do want to get the book when I can scrape the pennies together.

I used Mark Pilgrim’s Dive into Accessibility in the current re-design and re-organization of my web sites. Between the two — Mark’s online book and Joe’s hard copy book — I hope that I’ll be providing accessible and usable pages, in addition to meeting the CSS and XHTML 1.0 strict specification validation criteria.

Oh, and I’ll be using RDF as the primary data structure for the applications I’m integrating into the site. I am just as determined to make RDF as friendly and usable to all of you, as Mark, Joe, and Jonathon are determined to make web pages accessible to those who need this effort.

I will make even the most RDF-resistant among you into RDF appreciators, if not out-and-out RDF fans. It is my goal. I have a mission.

Categories
Technology

Comments

Recovered from the Wayback Machine.

As you can see, I’ve added in functionality to display the most recent comments regardless of post. I’ve found that I do get comments on older posts, and they’re ‘lost’ because no one knows they occur. Now, every comment has its moment in the sun, so to speak.

Speaking of comments, there have been several attached to the Dripping with Irony post. Some agreement, more disagreement, including a comment from Tim O’Reilly, and I appreciate Tim taking the time to stop by and write a spell.

Discussion related to the post is well and good, and my appreciations are also extended to those others who have commented. However, I have a feeling that some of the people are using me and my posting as a way to hit and jab at each other, indirectly, rather than because they were interested in anything I have to say. Just a feeling, a hunch I have. Silly, eh?

However, if per chance this Is true, then all I can say is that these same individuals must not have learned the lesson that when you play with fire, you get burned. Same could be said of playing with firey birds.

Continuing this post’s topic, I want to talk about anonymous comments. Lately I’ve been getting some nasty anonymous comments, including some of a personal nature unrelated to the postings. There is a difference between posting a comment anonymously because you’re uncomfortable using your name — because of work or other valid considerations — and not using your name because you want to say vicious things without reprecussion.

I don’t want to sound too much like Warf in Star Trek, but people who hide behind the cloak of anonymity in order to take petty, mean shots at others have no honor. Hint: the worst thing I will ever say to another is that they have no honor*.

Starting today, you post a nasty, petty, vicious, and personal comment — about me or anyone else — without attaching your name or some other known psuedonym or your weblog or true email address, I’m deleting it. As simple as that. Don’t like my new rules? Take it up with management. I tire of wasting my time, and my readers time, with Anonymous Coward.

* I actually did this myself, once, by accident. With Happy Tutor from Wealth Bondage, no less. I wrote what I thought was a funny comment, under a joke psuedonym. However, when I checked later, I realized the comment was incredibly mean. I must have been exhausted when I wrote it. I do know that I felt horrid about it afterwards. Personally, I wish that Happy had deleted it.

This is late, but sorry Happy.

Categories
Technology

Comment How-To

Recovered from the Wayback Machine.

In comments to my last posting Jonathon, asked the following about my new comment modification:

Is that standard in (later versions of) MT? Or a custom-coded Burningbird special?

Answer: a bit of both.

The code is based on templates and an example that Ben and Mena provided, but I customized. So I thought I would provide a how-to if others are interested in incorporating at their weblogs.

First, I added permalinks for my comments, so that clicking on the specific comment takes the person directly to the comment. I changed the MT template code for comments within the individual entry archive template to the following (modifications are in bold text):

<a name=”comment<$MTCommentID>”></a>
<$MTCommentBody$>
<span class=”comments-post”>Posted by:
<$MTCommentAuthorLink spam_protect=”1″$> on
<a href=”<$MTEntryLink$>#comment<$MTCommentID$>”>
<$MTCommentDate$></a>
</span>

Once permalinks have been added, I then added the comment code to the main template page. This is a modification of example code the Trotts have provided:

Update: Code has been altered to remove hard coded URL per note from Sam Kington — thanks Sam!

<MTComments lastn=”10″ sort_order=”descend”>
<a href=”<$MTBlogArchiveURL$>/<$MTCommentEntryID pad=”1″$>.htm#comment<$MTCommentID$>”>
<$MTCommentAuthor$></a> on <MTCommentEntry>
<$MTEntryTitle$>
</MTCommentEntry><br />
</MTComments>

From top to bottom: The outer comment block is necessary for using the comment tags. In addition, it also provides instruction to list the last ten comments. The next line then forms the link, which is based on the static archive location appended with the entry id and the comment entry id, both based on MT tags. The next lines add the comment author and title, again both from MT tags.

I’m using MT 2.51, but this should work with any version of MT that supports all of the tags I’ve outlined.

Holler if you have any questions.

Update (12/29/02)

Jonathon Delacour, Mr. Markup to us angle-bracket challenged, pointed out that the name anchor reference is deprecated for XHTML. Instead, the preference is to use id. When I update the weblog to XHTML, I’ll be using the id attribute instead, which is gonna bust heck out of any remaining old browser here abouts.

Anyway the change would be to pull the anchor tag (the <a name=…>) and replace with:

 

<div class=”comments-body” id=”comment<$MTCommentID>”>

 

Thanks to Jonathon for heads up and correction.