Chromium remains buggy; and I get charged twice for parking (thrice if you count my rates)

I am happy to say that Firefox 4 Release Candidate 1 is working smoothly with no crashes to date. It reminds me of, well, Firefox 3·0, before Mozilla started doing weird things to it and we had the multiple-crashing 3·5 and 3·6. Let’s hope this situation lasts.
   Meanwhile, the bugs I reported to the Chromium people in October and November 2010 have finally received responses. It’s too long compared with Mozilla. I told the chap that I had given up on Chrome, but I downloaded it today just to see where things were at.
   Based on the latest Chromium, the incomplete font menu bug has, indeed, been fixed, though various font-changing ones still appear present. There are still font-linking and character-set issues. (The images below have had their colour depth reduced for faster loading.)

Chromium 12
Chromium 12Above and left: When Chromium hits a ligature, the line or part of the line changes font. Opera does something similar: it changes the font of the one word that contains the ligature.

Chromium 12Left: Chromium might just decide to change fonts anyway—likely a Postscript error already sorted in Mozilla thanks to the likes of Jonathan Kew.

Chromium 12
Above: The font-linking problem on the home page of Lucire still has not been solved. There is no problem on IE8, Firefox or Opera. I can’t report on IE9 as my psychic powers are not strong enough to determine what is being told to me through the heavenly dimensions.

Chromium 12
Above: This one paragraph is properly linked—what causes it to work and the others not to is unknown.

Chromium 12
Above: Go outside the regular Latin set, and Chromium falls all to pieces, just as it always did.

Chromium 12
Above: At least there are fewer font changes than last time—though Chromium continues to struggle with soft hyphens.

   Meanwhile, after I reported spam faxes (a breach of the Telecommunications Act) to Telstra Clear, I was surprised to learn that my case was never examined. I had to open a new ticket with new faxes today. The excuse was the backlog of work post-Christchurch earthquake and, in the circumstances, I had to accept that.
   One was for a law firm, as far as I could make out. I wouldn’t hire a lawyer who breaches the Telecommunications Act. They shot themselves in the foot with that one.
   My main reason for calling, however, was the Text-a-Park service that the WCC offers. I hate cellphones, but had brought one with me on one of those rare occasions, and decided to give the service a go. I fed in the code, dialled 7275, and was told by the meter that the transaction had failed. No parking ticket was generated.
   Just as well. I prefer to use a credit card anyway, and fed that in. I got my ticket and my credit card was charged.
   Problem: as I walked away from my car, I received an SMS saying (sic), ‘Thanks for using TXT-a-Park. Your transaction for $6.50 has been accepted.’ I have no idea how one gadget says it’s failed and another says it’s succeeded, and my quantum physics isn’t good enough to figure out into which alternative universe this supposedly successfully printed ticket went to.
   Of course, the charge appeared on my Telstra Clear bill today.
   There’s a reason that jokers like me don’t use cellphones. Because, each time we do, they bite us on the bum. Though a buttcheek bite is better than testicular cancer.
   I’d urge folks to check their bills—if you haven’t received a ticket from a Wellington parking meter, and you still got charged for it, then give the telco a call.


You may also like




Leave a Reply

Your email address will not be published. Required fields are marked *