My blog has been receiving a lot of spam lately, at a rate of about 50 dummy comments per day. As my current web hosting doesn’t allow me to open socket connections, a part of WordPress functionality (including Akismet, the spam checker plug-in shipped with WordPress) won’t work. I knew about the limitations and am currently looking for a hosting replacement (in fact, I guess I already found one). In the meantime, manual triaging so much spam was just becoming painful. 
Screenshot of SVG image after rotation, zoom and pan
I’ve just finished a demo which tries to fill a long caveat among SVG implementations: a consistent front-end for internal document navigation (zoom, pan, etc.). It took me a while to workaround and document a few subtle bugs in several implementations, as well as recently integrating SVG Web, which has it’s own set of limitations, but it’s ready (at last!). 
What are you waiting for? Go ahead and try it! 
Hello world!
First of all, a quick apology to fellow Portuguese readers for deciding to publish this blog in English. It wasn’t very hard to decide, as English is the language of the Internet, but me being a big fan of my mother tongue made the choice slightly less obvious. 
Naturally, I reserve myself the right to publish some blog entries in Portuguese but, in general, English it is (this applies to comments as well).
Firefox screenshot after rendering the page
OK, I better start by stating this post’s title is actually a pun: as far as I know, Emacs doesn’t cause any interoperability issues with SVG implementations, but I thought like a sensationalist headline from time to time won’t hurt…
Today I stumbled across emacsformacosx.com, a nice HTML+SVG use-case: HTML for the actual text content and SVG for visual improvements, which would degrade whenever no support is available (Internet Explorer, essentially). Unfortunately, the site seems to have triggered a few bugs in several implementations… 
Properties screenshot of a file shipped with Adobe Reader 8
A common belief is that ASV 6 Developer Release 1 was the last version of the famous Adobe SVG Viewer software (ASV 3.03 being the last stable release). Well, apparently not…
Distributed with Adobe Reader 8, one can take a peek at the ImageViewer.API file, placed within the plug_ins directory (full path will typically be %ProgramFiles%\Adobe\Reader\plug_ins\ImageViewer.API. The original filename, NPSVG8.dll (see screenshot), is probably familiar to whoever has played with previous ASV versions: NPSVGX.dll stands for Netscape Plugin, where X is the major version number; the file was used for deploying the plug-in in browsers, such as Firefox (Gecko) and Safari (WebKit), who didn’t natively support SVG by then. As of today, at least Firefox is no longer compatible with the plug-in (and Safari will likely follow) but they don’t need to anyway: a good level of native SVG support is available in modern browsers.
BIOS screenshot of USB controller speed configuration
Today, while browsing through my system’s BIOS for some tweaks, I noticed a strange sentence in my peripheral configurations:
Configures the USB 2.0 controller in HiSpeed (480Mbps) or FullSpeed (12Mbps).
Full-speed at 12 Mbps and Hi-speed at 480 Mbps? Damn, is this a typo in the BIOS textual description or am I missing something? I crawled the Web and found out that it was I who was confused: in fact, Hi-speed USB is the fastest one.