“A recent study at my ol’ Alma Mater has concluded that when whiny kids grow up, they become conservatives. When they don’t, they become liberals.”
— Liberal Larry explains shoddy researchMore toying with dictionaries
[Update: the editing form is now hooked up to the database, in read-only mode. I’ve linked some sample entries on it. …and now there’s a link from the dictionary page; it’s still read-only, but you can load the results of any search into the form]
I feel really sorry for anyone who edits XML by hand. I feel slightly less sorry for people who use editing tools that can parse DTDs and XSDs and validate your work, but still, it just strikes me as a bad idea. XML is an excellent way to get structured data out of one piece of software and into a completely different one, but it’s toxic to humans.
JMdict is well-formed XML, maintained with some manner of validating editor (update: turns out there’s a simple text format based on the DTD that’s used to generate valid XML), but editing it is still a pretty manual job, and getting new submissions into a usable format can’t be fun. The JMdictDB project aims to help out with this, storing everything in a database and maintaining it with a web front-end.
Unfortunately, the JMdict schema is a poor match for standard HTML forms, containing a whole bunch of nested optional repeatable fields, many of them entity-encoded. So they punted, and relied on manually formatting a few TEXTAREA fields. Unless you’re new here, you’ll know that I can’t pass up a scripting problem that’s just begging to be solved, even if no one else in the world will ever use my solution.
So I wrote a jQuery plugin that lets you dynamically add, delete, and reorder groups of fields, and built a form that accurately represents the entire JMdict schema. It’s not hooked up to my database yet, and submitting it just dumps out the list of fields and values. It’s also ugly, with crude formatting and cryptic field names (taken from the schema), but the basic idea is sound. I was pleased that it only took one page of JavaScript to add the necessary functionality.
[hours to debug that script, but what can you do?]
Dictionaries as toys
There are dozens of front-ends for Jim Breen‘s Japanese-English and Kanji dictionaries, on and offline. Basically, if it’s a software-based dictionary that wasn’t published in Japan, the chance that it’s using some version of his data is somewhere above 99%.
Many of the tools, especially the older or free ones, use the original Edict format, which is compact and fairly easy to parse, but omits a lot of useful information. It has a lot of words you won’t find in affordable J-E dictionaries, but the definitions and usage information can be misleading. One of my Japanese teachers recommends avoiding it for anything non-trivial, because the definitions are extremely terse, context-free, and often “off”.
Dear Apple,
Please stop making products that subject your customers to electric shocks.
Really, there are better ways to keep the cult alive.
Dear Apple,
Please stop. Plugging in my iPod is not an appropriate time for you to be plugging MobileMe. iTunes should never display an ad when I sync my device.
Never mind that I’m already a .Mac user and you damn well know it; I just haven’t enabled it on my iPod Touch, because the sync is still broken and your servers go offline at random intervals. I don’t want to hose my email, bookmarks, calendar, and contacts by syncing them through an unreliable service.
[speaking of which, plugging in an iPod Touch does not trigger a sync; you have to hit the button manually. WTF?]
Dear Matias,
[Update 10/24/08: after informing them on 10/2 that the replacement was also defective and that it was heavily used (the one I exchanged for it was pristine, by the way), I have never heard from them again. Their customer service is as bad as their engineering.]
[Update: the replacement arrived used. Not “previously owned”, used. As in filthy, sticky, and filled with hair and food from the previous owner. It’s also even worse for typing, generating phantom keys under even more conditions, like attempting to type the word “since” (which comes out “sincey”) at a normal speed. It’s junk, and I’ll never buy a keyboard from them again.]
Fuck you. “Thank you sincerely for eventually agreeing to replace the defective product and ship the replacement in parallel.”
When I sent a support message about my still-under-warranty expensive keyboard suddenly generating spurious keystrokes, I expected a better answer than this:
What you are experiencing is called a "shadow key" or "phantom key" or "ghost key". Every keyboard has them (in different locations) but most people don't notice them, because they don't type the key combinations that produce them. They are an artifact of how keyboards are built.
There is a workaround...
You can turn On the Sticky Keys feature on the Universal Access control panel, in System Preferences. This will allow you to press & release the Command and Shift keys together, and then press the key being modified on its own.
We are very sorry for the inconvenience...
This is the most useless “workaround” I’ve ever seen. “Can’t touch-type on your keyboard? DON’T TRY!! Problem solved!”
Never mind that I simply don’t believe their explanation…
