Print Story A Day in the Life
Working life
By ReallyEvilCanine (Fri Oct 05, 2007 at 06:34:02 AM EST) A Day in the Life, fonts, Arial, fuckwit, pie (all tags)
Font of Knowledge
There are many levels of stupidity. Drinking too much on a work night is just plain stupid. Drinking until 3:00a.m., then coming home, turning on all the lights, having another beer while playing computer games with the volume turned up to 11, waking up the guy who drank too much and has to go to work in the morning to pay the bills is really incredibly stupid. But there's a level of stupidity so mind-bogglingly high, so gobsmackingly, migraine-causing, teeth-gnashingly extreme that it makes Steve Martin's character in Dirty Rotten Scoundrels look like the Oracle of Delhi in comparison. I shall let Harish explain it for me in a ticket copied verbatim with only identifying bits munged.

Poll: Degrees
x-posted to da brog

Harish works for $BigBank. $BigBank decided that it would probably be a good idea if the Japanese customers could type in their native language. $BigBank got all Unicodified with the help of our guys on the scene. Huzzah! But then they left $BigBank to their own devices, said devices being sniveling, drooling incompetents who probably type with a pointer stick attached to their safety caps.
We're rolling out $YourBigApp to multiple countries (including Asian countries) and hence, there is a need to enable capability to enter and retrieve multi-lingual characters. To do so, we've made the required changes in all templates by mentioning 'Arial Unicode MS', wherever 'Arial' was specified as the font. It works and we're at UAT stage now.

However, we've observed a strange behavior wherein a few testers reported that they are not able to view the special language characters and instead viewed junk characters (Screen shot 1 attached).

On further investigation, we found that there is a font (Arial Unicode MS), which should be installed on tester's machines. It was installed on their machines, but we copied this font from other tester's machine, where language characters were appearing correctly. On doing so, testers, who reported the problem, were able to view the expected characters (Screen shot 2 attached).

However, to determine the root cause, now when we replace fonts to old fonts, the problem does not persist. We don't know that what has fixed the issue? Is it that when we copied the fonts first time, issue was fixed permanently? Now those testers see junk characters only when we 'Remove' the font altogether from their respective machines. What are your thoughts and what should we take into account while rolling out the application?

Please note that on a Windows 2000 machine, we're navigating to Start->Settings->Control Panel->Fonts to perform the font copy-paste operations.

I was too stunned to smash my head into my desk to relieve the pain. All I could think of was this bash quote. Why is this guy alive? How the fuck does this man remember to take the fork out of his mouth before chewing? How does he remember to breathe in?

If you missed it for all the words in there, let me highlight the important bit:
Is it that when we copied the fonts first time, issue was fixed permanently? Now those testers see junk characters only when we 'Remove' the font altogether from their respective machines.

He installed the font and everything worked. Then he deleted the font and it stopped working. And this surprises him, the "system administrator".

Perhaps this will stop the J'accuse comments about my intolerance. Enough's enough! Give me my fucking Root Cause: 17-Fuckwit already!

< Hey Bob | BBC White season: 'Rivers of Blood' >
A Day in the Life | 6 comments (6 topical, 0 hidden)
haha by cam (2.00 / 0) #1 Fri Oct 05, 2007 at 07:10:35 AM EST
that gave me a laugh.

Freedom, liberty, equity and an Australian Republic

this is why I requested a 'stupidity' topic by discordia (2.00 / 0) #2 Fri Oct 05, 2007 at 07:45:12 AM EST

If it makes you feel better. by Breaker (4.00 / 2) #3 Fri Oct 05, 2007 at 07:48:11 AM EST
Two support issues I dealt with this week:
  1. A new dll I built to deal with an import file format change "did not work at $BANK".  Despite my explicit instruction to unregister the old dll, and overwrite it with the new one, then re-register it, they decided to not bother with that and just saved it to the root of the C: drive.  Oddly, when the new format files were processed, there were errors.
  2. Despite $CLIENT claiming he'd followed our instructions, $MARKET_DATA_FEED was not working.  We finally managed to get a remote access onto his server today:
   * No entry in hosts file for the data feed server, despite that being in the instructions
   * The sample configuration file we'd told him to modify contained:
   [YOUR_DATA_SERVER]:10033:[YOUR_LOCAL_HOSTNAME] despite us sending verbose instructions on how to modify it
   * Deleted the SYSTEM database on the machine because "there's no market data in it".

Words have failed me this week.

To be fair by jayhawk88 (4.00 / 2) #4 Fri Oct 05, 2007 at 08:52:29 AM EST
There probably wasn't anything in the documentation that explicitly stated "Problem is fixed when the client computer begins working properly."

Sometimes the tech support types are the fuckwits. by wiredog (4.00 / 4) #5 Fri Oct 05, 2007 at 10:09:41 AM EST
Admittedly, cable co fuckwits, but still...

From The Post

So, about two months ago I changed my home phone service provider to another provider that was offering a much cheaper rate. I do not wish to embarrass anyone here, so I will refer to the new provider as Tsacmoc Elbac Oc. phone connection began to disappear entirely for hours at a time. It was apparently modem problem. So I arranged for Tsacmoc to come and take a look, which required me to stay at home for the convenient four-hour "window" that cable companies tend to insist upon. This is one major panoramic picture window they allow themselves.

No one showed up. When I called to ask why, they informed me that it is their policy for the technician to phone ahead just before he comes, and if no one answers the phone, they cancel the appointment.

After I stopped screaming inarticulately, I calmly asked the customer service rep if he saw anything wrong with the logic of that policy. He did not.

Earth First!
(We can strip mine the rest later.)

It hurts when I do that! by duxup (4.00 / 1) #6 Fri Oct 05, 2007 at 03:57:59 PM EST
A Day in the Life | 6 comments (6 topical, 0 hidden)