Another year, another mta_digg_it Textpattern plug-in update. This time, version 0.3:

mta_digg_it-0.3.txt (see full info)

This release brings some minor updates to the documentation, the compact attribute’s functionality has been moved to the more flexible skin attribute (you can now use either full size, compact, or icon sizes), and you can optionally use the article’s excerpt as the content of the bodytext attribute.

Drop me a line if you have any questions, comments, or bug reports.

I’ve been using em-based text-sizing on this site for a number years using Richard Rutter’s methods and have done well by them. He recently expanded upon his tricks for A List Apart and proved the consistency you can achieve with them.

But there’s one thing that’s occasionally in the back of my mind: what exactly is an em? I had some remembrance that it originally got its name from some aspect of the size of a capital M, but that’s about it.

I must have glossed over Richard’s definition having read the article too many times:

“Classically, an em (pronounced emm) is a typographer’s unit of horizontal spacing and is a sliding (relative) measure. One em is a distance equal to the text size.”

Oh, that’s right, it’s the height of the font. Actually, there’s more to it than that, especially depending on whether you’re a typographer, a type designer, or a software engineer. Font Beureu’s Type 101 blog has the full details (including illustrations) in their post The Em. Go read it.

I’ll leave you with the following excerpt (and many thanks directed at Grant Hutchinson for noting the article):

“In my view, the em is a fundamental unit of typography. It plays a critical role in the design of a typeface, in the technology to compose and render the typeface, and finally in the decisions made by the typographer when setting the type. In fact, from the type designer’s point of view, the em is what forms the basic module used to compose letters into words, words into lines, and lines into paragraphs. It makes movable type possible.”

Thomas Brand has updated [his] Newton Blog to even further emulate the Newton OS 2.1 experience by applying the Apple Casual font to his Tweets section.

This is a twofold implementation so as to support as many browsers as possible, using sIFR (Scalable Inman Flash Replacement) and CSS2’s @font-face (see A List Apart’s CSS @ Ten: The Next Big Thing for further details).

Many thanks to Thomas for implementing the latter after a brief chat via Twitter!

I’ve updated my mta_digg_it Textpattern plug-in to v0.2 today.

This version includes the following fixes:

1. Correctly escapes apostrophes, quotes, backslashes, etc., when used in the title or bodytext attributes (pulled from the article title by default).
2. Prevents cross-pollination of variables when multiple “Digg This” buttons appear on a single page.

The latest version and full description can always be found on the development page or you can download it directly:

mta_digg_it-0.2.txt

As always, please let me know if you have any questions, comments, or bug reports.

I happened across the fact that Digg has implemented new ‘smart’ digg buttons on the 6th. The biggest new feature here is that you no longer have to first ‘submit’ an article to get its “digg url” to use with the “Digg This” buttons and can now just reference the article’s permalink instead.

With that, it means you no longer have to manually submit articles to Digg, copy the digg URL into a custom field in Textpattern, and have the “Digg This” button pull the URL from said custom field (or, worst case, paste the JavaScript into each and every article manually).

With this in mind, I decided it was finally feasible to write a plug-in to do this (I almost did it for the digg-url-in-a-custom-field solution). So, here’s version 0.1 of mta_digg_it: mta_digg_it-0.1.txt (full description here).

Please send in your comments, suggestions, and bug reports.

Update: Sorry about the broken link, it should be fixed now.

Update #2: Version 0.2 is now available.

I wrote a quick Textpattern plug-in today to spit back a “URL title” for an article ID instead of the numerical “ID” that <txp:article_id /> does and called it mta_article_id. Basically it’s intended to be a replacement of article_id.

I needed it to be able to implement human-readable anchors for articles in sections (for example the autobiograpy and colophon parts of this site’s about section) that aren’t sections that one would really “browse” (so no permalinks), but are mainly fake static pages. In fact, I had intended to have this functionality before I posted my holiday wish list, but I couldn’t find a way to extract just the “URL title” that appears at the end of a Textpattern “Clean URL” permalink (atleast not without writing some custom PHP code).

I asked around on the Textpattern support forum and one kind soul pointed me to this post by one of the moderators describing exactly what I needed.

So, I downloaded the Textpattern plug-in template (see Anatomy of a Textpattern Plug-in for more details on Textpattern plug-in development), and merged the moderator’s code (basically a one-liner) with that of the implementation of the built-in article_id in taghandlers.php (another one-liner), and—Voilà!—my first Textpattern plug-in.

Of course, I discovered that there’s now an <article_url_title /> tag as of Textpattern 4.0.5, but I’m still running 4.0.3. So, my plug-in was depricated before it was released, but the mention of article_url_title only appeared on December 1st, right in the middle of when I was first working on getting “URL titles”, so I guess it’s excusable.

Regardless, you can download mta_article_id from the development section if you like.

Update: It turns out I had overestimated which version Textpattern is currently at. It’s currently only at version 4.0.4, so although version 4.0.5 will include the article_url_title tag my plug-in is still needed in the meantime.

Note: This cookbook is based on building MRTG 2.14.7 on Mac OS X 10.4.8 (Tiger) client as of October 31st, 2006. It should work for Tiger Server as well, but you’ll want to check to see if libpng is pre-installed or not.

Disclaimer

This cookbook is intended for those that are atleast slightly familiar with building and configuring unix applications on Mac OS X and Mac OS X Server. No support is offered and the author is not responsible for any lost data due to following these steps or mistakes made while attempting to follow these steps.

With that in mind, these steps did work for the author and will provide a quick copy & paste solution for those that don’t want to waste ten minutes figuring out that the --without-fontconfig flag needs to be set when running configure for gd.

Reference

• http://oss.oetiker.ch/mrtg/
• http://oss.oetiker.ch/mrtg/doc/mrtg-unix-guide.en.html
• http://www.libpng.org/pub/png/libpng.html
• http://www.boutell.com/gd/
• http://www.stepwise.com/Articles/Workbench/2001-11-13.01.html

Setting Up the Build Environment

cd ~/Desktop/
mkdir build-mrtg2
cd build-mrtg2

Building & Installing libpng

curl -O http://superb-east.dl.sourceforge.net/sourceforge/libpng/libpng-1.2.12.tar.bz2
md5 libng-1.2.12.tar.bz2
tar -xjf libpng-1.2.12.tar.bz2
pushd libpng-1.2.12
./configure
make check
sudo make install
popd

Building & Installing gd

curl -O http://www.boutell.com/gd/http/gd-2.0.33.tar.gz
tar -xzf gd-2.0.33.tar.gz
pushd gd-2.0.33
./configure --without-freetype --without-jpeg --without-fontconfig
make check
sudo make install
popd

Building & Installing MRTG:

curl -O http://oss.oetiker.ch/mrtg/pub/mrtg-2.14.7.tar.gz
md5 mrtg-2.14.7.tar.gz
tar -xzf mrtg-2.14.7.tar.gz
pushd mrtg-2.14.7
./configure --prefix=/usr/local/mrtg-2
make
sudo make install
popd

Closing:

That’s it, you’re done. You can delete the ~/Desktop/build-mrtg2/ directory once you’re confident that MRTG is working as intended and you won’t have to rebuild any part of it.

Download This Cookbook as Text:

Cookbook – MRTG 2.14 on Mac OS X 10.4 (Tiger).txt – 2006-10-31

I apologize for the mess in article headers over the last couple days. I’ve been restyling them, but only have a few hours in the mornings to do so and have been taking my sweet time to finish them up.

Update: This has been cleaned up. Thanks for your patience.