Whomever wrote the .xsl file for the v9.5.0 web display should be shot.

[Jinmei_Tatuya at isc.org]

At Tue, 10 Jun 2008 23:46:58 -0700,
"D. Stussy" <spam at bde-arc.ampr.org> wrote:
> 
> <Jinmei_Tatuya at isc.org> wrote in message news:g2nlk6$2ss8$1 at sf1.isc.org...
> > At Tue, 10 Jun 2008 00:28:13 -0700,
> > "D. Stussy" <spam at bde-arc.ampr.org> wrote:
> >
> > I couldn't decode the message body...I suspect it was due to
> > the mime-encoded from field of my response.  This time I only use
> > plain ascii characters, so could you resend it to this one?
> 
> 
> As requested:  Message-ID: <g2nkut$2q0d$1 at sf1.isc.org>
> 
> Actually, I've been discussing this via private e-mail with another ISC
> member.  I guess some of my comments have made the rounds.
> 
> You are correct in that "not everyone will have [at least] an 800-pixel wide
> screen."  However, except for the original 480x640 VGA standard of over a
> decade ago, everyone else will have 800 pixels wide (or more).

I expect someday people will also check the stat via their iphone, but
I can only be shot once:-)  In any case, abusing the table structure
for this purpose is bad for other reasons.  Now that we are fixing it,
we should do it right rather than a bandaid tweak.

> All I was going to do with it was change the columns from 10 to 6 in the
> tables that don't have tabular data.  As noted, that's a low priority here
> (thus I haven't sent in my diff yet).  Did your change do something else?

My patch doesn't use tables in the first place.  It sets pairs of
dt/dd for named counters and lets the browser layout properly with
customized styles.

Since the mail server doesn't seem to accept attachments, I've
temporarily copied the patch at http://www.jinmei.org/bind9stat.diff
in case you're interested in it.

---
JINMEI, Tatuya

p.s.
> The only non-ascii sequence in my message came from your "From:" header when
> quoting your message.  If this causes you problems, then don't use your
> ISO-2022-JP sequence.

It should have been ascii sequence (but just mime-encoded) when it
arrived at your server.  I suspect some entity then converted it to
non-ascii sequence in the wire.  I've never seen the non-recoverable
error I encountered this time even with such a half-broken header.
Anyway, I'm not intending to argue about this point with you.  I'll
avoid using the encoded ascii sequence when I ever need to write to
you again.