blogger dashboard blog archive
xyzzy homepage

REXX, Full Frontal mpeg, IANA

2008-05-08

Blogger trackback form

Encouraged by an immediately working backlink for the last post I added an experimental trackback form to the template of this blog, it allows manual trackback pings:

<!-- trackback form --><b:if cond='data:blog.pageType == &quot;item&quot;'>
 <b:if cond='data:blog.title != &quot;&quot;'><!-- trackback blog_name -->
 <b:if cond='data:blog.pageName != &quot;&quot;'> <!-- trackback title -->
 <form action='#requires.javascript' id='track' method='get' name='track'
       onsubmit='document.track.action=document.track.back.value;
                 document.track.method=&quot;post&quot;' target='_blank'>
 <input expr:value='data:blog.url' name='url' type='hidden'/>
 <input expr:value='data:blog.title' name='blog_name' type='hidden'/>
 <input expr:value='data:blog.pageName' name='title' type='hidden'/>
 <input name='back' size='50' type='text' value='http://delorie.com:81/'/>
 <input type='submit' value='ping'/></form>
</b:if></b:if></b:if><!-- end of trackback form -->

Apparently you can add this form to any type='HTML' widget after going to Layout: Edit HTML and checking Expand Widget Templates. I used #track:target { display: block; } in the CSS to show the form only when it's the target. Text mode browsers will see it anyway, but maybe they have no JavaScript.

I ✅ Unicode

Some days ago Mark noted on the Official Google Blog that UTF-8 finally managed to be more popular than US-ASCII, I found it on the Q&A Weblog.

Actually it is not that impressive, it merely shows the Unicode conspiracy at work, UTF-8 is designed to replace US-ASCII in the next decades, one encoding to rule them all.

But it is fascinating to see the usual suspects working together on IDNAbis, another important step in the master plan, among others Vint as author of RFC 20, Mark as co-author of UTF-7 when UTF-8 was not yet ready for prime time, Harald as author of RFC 2277, and John who recently added two critical missing pieces to the puzzle:

  • RFC 5137 - ASCII Escaping of Unicode Characters (BCP 137)
  • RFC 5198 - Unicode Format for Network Interchange

2008-05-02

Hamburg-Web

An attempt to add this blog to HH-web.de finally worked, while I was at it I created a HH-web search googlet and learned some new CSS tricks.

For years I used hreflang="de" in links to German sites on English pages or vice versa, without visible effect, and likely no effect at all. Now I found a way to do something with it:

:link[hreflang]:hover:after {
     content: " " attr(hreflang); font-weight: 100;  
     vertical-align: super; font-size: xx-small;   }

This construct matches links with a hreflang, and displays the value as small as possible at the end of the link while the mouse hovers over it. Test it with the HH-web link above.

Another nice CSS feature is :target, not displaying the ugly blogger dashboard is one thing, but now I can also get it back when I need it with an invisible link in the upper left corner of this blog.

Googlet gallery

After a year one of my googlets is apparently used by some folks, great, it encouraged me to work on the whole set, add some settings such as the help language on the PDA LEO googlets, and create a gallery.

New entries are googlets for the German and English Heise whois for older browsers without OpenSearch support. For a different preview see googlemodules. No, I've not given up on the command line rxwhois client, but allegedly some users don't like command lines... ;-)

Another new entry is a MetaWikiHelp googlet, the Wikipedia help often is not good enough when working on other MediaWikis with different features and rules.

2008-04-12

Custom search googlet

Transforming Google CSEs into OpenSearch descriptions is simple, even when Firefox needs some proprietary <moz:SearchForm> magic to get it right.

For older browsers not supporting OpenSearch each CSE has its own default gadget for uses on iGoogle, blogger, and elsewhere. I created a smaller configurable tiny CSE variant, to use it edit the cx-number, e.g., 001904119753490578822%25:zvsejdqm-pw for the xyzzy-CSE.

CSEs hosted by Google have one issue, creators cannot easily publish the source for users wanting to know what the CSE really does. Here's a snapshot of the sites currently covered by the xyzzy-CSE:

2008-03-08

MD5 1.6: POP3 and UUID

Version 1.6 of the MD5 test suite covers RFC 5034 (Digest-MD5 for POP3), RFC 4122 (UUID version 3), and an old RFC 1910 example. The POP3 example belongs to the MD5-sess series.

The UUID example is apparently wrong, it swaps the byte order unnecessarily. Examples published by python.org and ossp.org agree with that theory, I'll submit it as erratum.

2008-02-22

MD5-sess and RFC 5090

RFC 5090 was published, it fixes some problems with the MD5 examples in RFC 4590. Version 1.5 of the MD5 test suite now contains the new RFC 5090 RADIUS examples.

The updated test suite contains a new procedure AUTHTTP for the RFC 2617 idea of MD5-sess noted in the errata. The old DIGEST procedure uses the RFC 2831 MD5-sess algorithm. Six new test cases cover MD5-sess examples published in RFC 2831 and 4643 using the RFC 2617 algorithm. Hopefully this will be documented in an RFC moving RFC 2831 to HISTORIC.

2008-02-18

Hamburg's vote on ooXML

Microsoft's quest to forge the one ring will soon reach a critical stage. In the BRM on OfficeOpen XML a so-called German delegation will have six votes, one of them the tax authorities of the city of Hamburg. In 2007 DIN supported ooXML in a controversial procedure, with Hamburg's fiscal authority under the yes votes.

Historical background, Hamburg was once the home of StarOffice, a name still used for Sun's OpenOffice version, closely related to what later became ODF, an ISO standard roughly covering what MS Office 2007 as so far only potential ooXML implementation offers. Of course MS Office isn't free like OpenOffice, and with about 6000 pages the ooXML draft is considerably more elaborated than ODF.

It is not obvious why Hamburg's fiscal authority supported a draft allegedly identifying 1900 as leap year, where dates before 1900 don't work. As Excel simplification that is funny or even acceptable, but Excel is a commercial product and no international standard. Just one of many ooXML issues, maybe addressed in the additional 2293 pages submitted for the BRM.

It fits that the citizens of Hamburg get a chance to elect a new parliament one day before the BRM. Related, Google doesn't like ooXML, their German HQ is in Hamburg, and they got no vote in the relevant DIN committee.

2008-02-13

Patch that zeppelin

XML 10th anniversary
XML is ten years old, good to know, waiting for the monthly W2K patch orgy to finish I used the time for my education. The worst update this month are 36 MB for Adobe Reader 8.1.2.

Also ten years old is RFC 2277, the IETF Policy on Character Sets and Languages. This is a nice piece of RFC number magic, RFC 2278 used to be the IANA Charset Registration Procedures, now 2978, and RFC 2279 used to be UTF-8, now 3629 (STD 63). The magic also works backwards, the predecessor of 2279 was 2044, and RFC 2045...2049 is MIME. The MIME type registration procedures used to be 1590 next to RFC 1591, i.e. what is today ICANN. After ten years they are now getting serious with I18N for domain names and other missing pieces in this puzzle.

Labels

Creative Commons Licencexyzzy blog
CC Attribution-ShareAlike 4.0 License
Search only IANA, ICANN, IETF, OpenSPF, Unicode, W3C, xyzzy

About Me

My photo
Hamburg, Germany
There's no EX in ex-Wikiholic. Now having fun with the last days of Google+ and its self-proclaimed murderess.