AppleInsider has found the icons for the new iTunes countries, thereby confirming iTunes is about to start in Australia, Switzerland, Sweden, Norway, and Denmark. Not before time for those AU-ers among us. I’m seeing more and more of those white earplugs on the train to work.

It’ll be interesting to see how it goes. So far all the Australian online music stores have concentrated on selling protected WMA files. These haven’t been setting the world alight, partly of course because the files are useless for legions of iPod owners, and from observations, there are hardly any non-iPod portable music players out there in userland. And for myself, I’d refuse to buy files that won’t live beyond the (hopefully long but inevitably limited) life of my player.

Record companies must surely be waking up to it by now. They can’t copy-protect conventional CDs properly — it either breaks the Red Book standard (and thus compatibility) or it doesn’t work. Anything they try is either useless or has been hacked. So you might as well just sell MP3s. They’re no more vulnerable than CDs. And it’s better to be selling copyable songs than no songs at all.

And the reported Apple price of A$1.80 per track is competitive. A quick scout of some WMA-selling stores showed a typical price of A$1.89 per track, with top ten hits at A$0.99.

The other thing this week for Apple fans is the OS X “Tiger” release, though I’m sure they all already know that.

I was digging about in the Unix system directories on MacOS X today (actually, searching for ‘joe’ which I thought I had installed, but is nowhere to be found) and stumbled upon the directory /usr/share/misc. Within this folder is the file flowers which is a listing of flowers and their meanings. I don’t know if it is actually referenced by any command; my guess is that a Berkeley programmer got bored and decided to put in an interesting, if not entirely useful in an OS environment, text file.


# Flower : Meaning
# @(#)flowers 8.1 (Berkeley) 6/8/93
#
# Upside down reverses the meaning.
African violet:Such worth is rare.
Apple blossom:Preference.
Bachelor's button:Celibacy.
Bay leaf:I change but in death.
Camelia:Reflected loveliness.
Chrysanthemum, other color:Slighted love.
Chrysanthemum, red:I love.
Chrysanthemum, white:Truth.
Clover:Be mine.
and so on

A couple of weeks ago I decided to give my Mac a spring clean. Though Mac OS X is pretty good at housekeeping itself, it can’t take account for all the unused software and redundant system bits-’n'-pieces that I’ve added over the years. I decided to load up Font Book and clean out some of my dusty fonts.

At some point in the past I remember installing the same font in multiple places, which is just plain wasteful of disk space, when all that’s required is to put fonts in a publicly accessible place and ensure that all users can access them from their accounts (particularly as I am the only ‘power user’ with a couple of other accounts for my wife and for guests that rarely get used, font management shouldn’t be a big issue).

Well, I got fed up with plodding through each font family deleting the ones I didn’t want. There were a heck of a lot of duplicates, as I suspected, and I knew it would be quicker to dive into the terminal window as superuser and delete them from the command line.

Having searched for them, I found a number of /Library/Fonts folders and located the duplicates. rm‘ed them, then mv‘ed the remaining ones into one sensible place.

Reboot…

OK the Mac OS X loading screen appeared with the progress bar, but no descriptive text. Errm… what have I removed?

Next, the desktop pattern and white menubar appeared, with the spinning rainbow disk, and then the screen blanked out for a second, and the desktop reappeared… looped again, and again, and again…

The system had stopped responding to any input. I had stupidly removed all the fonts from the main /System/Library/Fonts folder, and now not only was all the text invisible, but the system couldn’t even boot to a point where I could blindly get to the Terminal and correct it.

Help, what now?

Booting from the Mac OS X install disk didn’t help, as all it wanted to do was to reinstall the system (logical, I guess), and I wasn’t prepared to go back point-eight versions then spend the next day downloading all the updates again.

Fortunately, my Mac is old enough that Apple hadn’t disabled the “Boot into Mac OS 9″ mode, so I fired it up—having remembered both the firmware and the OS 9 passwords I’d set and promptly forgotten about—I then checked out the OS X install disk again (after realising that I couldn’t even cry for help on the Apple website as my new Net settings weren’t configured in OS 9). I was very pleased that it wasn’t simply an image file, but had the real system directories and files—I found the /System/Library/Fonts folder. Now the dilemma – can I just copy those fonts over the top of my Mac OS X volume or will it corrupt the other files?

Sometimes you just have to bite the bullet. I tentatively dragged and dropped the 17 fonts from the CD to Kayleigh (my OS X volume), reset the startup disk, and prayed as I restarted.

Splash screen … woo-hoo – text is appearing. Desktop … I can see the menu! Problem solved, after not a little agonising over the best thing to do.

I don’t know how many of the fonts in the root System folder are required, but a sensible guess is all of them.

Moral? Don’t mess about with anything in the System folder, even things that seem as innocuous as fonts, without a very good reason. Not being able to read text properly is one thing; causing your computer to refuse to boot up is quite another. I don’t know what the solution would have been if Mac OS 9 mode hadn’t saved the day, but it would probably have been expensive.