Tag Archives: opentype

What Does Your Name Sound Like?

Add to iTunes | Add to YouTube | Add to Google | RSS Feed

This is one of the coolest things I’ve seen in awhile. I typed in my name, and chose a sound effect. I could then hear what my name sounds like using sounds other than a human speaking voice. If you go over to P22, you can turn your text into music.

The P22 Music Composition Font was proposed in 1997 to the John Cage Trust as an accompaniment to the John Cage text font based on the handwriting of the composer. The idea was basic and simple-every letter of the alphabet was assigned to a note on a scale. This would allow for any text to be converted into musical notation.

The font used in the P22 MTCG is a basic version that closely follows the initial Cage inspired idea. Each letter, number and punctuation mark is assigned a note on the C major scale. When the user generates their composition the same substitutions are applied to their text that the eventually released Opentype font performs.

The P22 Music Text Composition Generator allows any text to be converted into a musical composition. This composition is displayed in musical notation and simultaneously generated as a midi file.

This is really interesting, and a lot of fun. Reading the history is very cool, and something I honestly enjoyed learning about. Of course, I can’t stop playing around and making music out of text! Try it out for yourself, and see how your name sounds.

Want to embed this video on your own site, blog, or forum? Use this code or download the video:

Fix Windows Vista's Fonts!

I’ve been labeled a nitipicker for seeing skipped details that few others seem to see on the surface of an application’s user interface. Guilty as charged! Download this simple registry patch, but please read this entire post before applying it?

I’m not happy that Microsoft has added yet another shell font to the mix with Windows Vista: Segoe UI. On its own, Segoe UI is an awesome font – but when it’s slapped up against Tahoma, MS Sans Serif, Microsoft Sans Serif, and/or Arial – it’s no longer a clean user experience. In fact, Vista is downright messy when it comes to shell fonts – with some aliased faces reaching back to the days of Windows 3.11!

These blatant font oversights were shoved onto the backburner for the sake of (a) 100% backwards compatibility and (b) time. However, that didn’t stop me from diving into REGEDIT and setting things straight. The good news? I believe I’ve figured out how to make everything inside of Windows Vista stick to Segoe UI. It’s a subtle, yet radical, transformation.

There are benefits and drawbacks that come with my font tweaks. The biggest benefit is that most (if not all) of your application fonts will finally be in the same font family. The drawbacks happen to be a matter of perspective.

Text in size-restricted config dialogs may appear tight or truncated, but you will never see Arial, Times New Roman, Microsoft Sans Serif, MS Serif, MS Sans Serif, or Tahoma font faces ever again. I can’t imagine this being a tremendous problem for most people – myself included.

I’ve killed most of the aliased fonts that will ship in Windows Vista – there’s virtually no other (or easier) way to do it other than through this registry patch. Software installers finally conform to a single Segoe UI typeset, Google Earth finally looks clean, and .NET apps finally don’t look any different than other apps on the system – and Web sites that call on Arial (like Google.com) look amazing after this tweak, too. I posted a few before and after screen shots to Flickr.

If you bother to look at the .REG file I’ve compiled, you’ll see that the tweaks are relatively straighforward. I’m essentially redirecting font rendering from fonts I don’t want (Arial, Tahoma, MS Sans Serif, etc.) to a font that I do want (Segoe UI). The essential key is in HKEY_LOCAL_MACHINE SOFTWARE Microsoft Windows NT CurrentVersion FontSubstitutes.

I’m releasing this tweak in the hope that others will help me refine it. You should set a System Restore point if you’re feeling gunshy. I’ve applied them safely to my own system, and have bug squished and cross-checked compatibility with both Robert McLaws and Brandon LeBlanc. They were both quite helpful and suffered through countless reboots with me. If you find any other tweaks that should be added to the .REG file, let me know and I’ll incorporate them ASAP.

For further optimization, you might also set your icon font to 8pt (it’s 9pt by default). Right-click the desktop, choose Personalize, click the first “Windows Color and Appearance” option, click the “Open classic appearance properties for more color options” link near the bottom, then click the Advanced button on the “Appearance Settings” dialog, select the “Icon” item, then flip the Size field to “8.” Windows Vista: transparently convoluted!

While my font patch is harmless, I’m not responsible for anything that might happen to your system (or life) if you decide to apply it. I’m sure incompatibilities will spring up, but that’s when I’ll really need your troubleshooting assistance.

I’ll certainly be sharing this information with a few key Microsofties, though I do not expect them to officially incorporate my patch into future builds of Windows. If you don’t even care about the fonts on your screen, then why did you bother to read this far – and what have you got to lose by applying my patch? I simply couldn’t recommend running Windows Vista without it.

Moreover, to all the people who slapped me around for complaining about Vista’s font mayhem: at least I did something about it instead of rolling over and pretending we were past the point of no return. Feh. If only I could fix other visual hiccups – like Vista’s Task Manager, which has 16-color icons and doesn’t ToolTip truncated fields. Maybe SpeedUpMyPC will fix it eventually?