Just a quick note. For those of you who are early adopters moving over to OS X 10.7 “Lion”, the method described in my previous tutorial on using IPA fonts with Mac OS X still works and produces good results on Lion.

For what it’s worth, Praat (5.2.29) works just fine as well. :)

So, go forth and Lionize your Mac without phonetic phear.

EDIT: But Lion does hide the library folder. In order to install the keyboard layout, you’ll need to unhide the ~/Library folder or to access it using the Finder’s “Go to folder” option.

Tagged with Computers and Software, Followups | 2 Comments


This is a quick guide on compiling and installing the Festival Text-to-Speech Package on OS X. This was somewhat of a gigantic pain, but eventually, seemed to work fine. The below is a collection

This tutorial assumes you have MacPorts installed from http://www.macports.org/ and can use the port command.

1. Festival and friends seem to work best on a Mac when compiled from the latest sources, obtained from SVN

1a. To install SVN:
sudo port install subversion

1b. Make a directory in your home folder called “tts”:
mkdir ~/tts

1c. Move into that folder:
cd ~/tts

1d. Checkout the latest versions:
svn checkout http://svn.berlios.de/svnroot/repos/festlang/trunk

1e. Copy the “festival”, “speech_tools” and “festvox” folders into the ~/tts folder, using the finder or otherwise.

2. According to , you’ll need to open speech_tools/include/EST_math.h and change:

/* Apple OSX */
#if defined(__APPLE__)
#define isnanf(X) isnan(X)
#define isnan(X) __isnan(X)
#endif

to:

/* Apple OSX */
#if defined(__APPLE__)
#define isnanf(X) isnan(X)
#if (__GNUC__ >= 4)
#define isnan(X) __inline_isnan(X)
#else
#define isnan(X) __isnan(X)
#endif
#endif

3. Now compile speech tools:
cd ~/tts/speech_tools
./configure
make
make test
make install

4. Now compile Festival:
cd ~/tts/festival
./configure
make
make install

5. Now compile festvox
cd ~/tts/festvox
./configure
make

6. Now ready OS X’s audio for this. This next part is stolen (and updated slightly) from :

Fire up Xcode (you do have the Developer Tools installed don’t you?):
File -> Open… /Developer/Examples/CoreAudio/Services/AudioFileTools/AudioFileTools.xcodeproj
Build the project.

Open up a terminal:

sudo mv /Developer/Examples/CoreAudio/Services/AudioFileTools/build/Debug-Tiger/afplay /usr/bin/
sudo chown root:wheel /usr/bin/afplay

If you find yourself missing any of the above files, download a precompiled version of afplay and copy it to /usr/bin/afplay as described above.

7. Open ~/tts/festival/lib/siteinit.scm and add the following:

(Parameter.set 'Audio_Required_Format 'riff)
(Parameter.set 'Audio_Command "afplay $FILE")
(Parameter.set 'Audio_Method 'Audio_Command)

If the file doesn’t exist, create it as a plaintext file such that it contains only the above lines.

8. Go to and download:
festlex_CMU.tar.gz
festlex_OALD.tar.gz
festlex_POSLEX.tar.gz

Then drag the folder inside the festival/lib/dicts folder in that file into ~/tts/festival/lib/dict (create it if it doesn’t exist yet)

Also download:

festvox_kallpc16k.tar.gz

Then drag the festival/lib/voices into ~/tts/festival/lib/ on your machine.

9. Open ~/.profile and add the following lines:

export PATH=/Users/stylerw/tts/festival/bin:/Users/stylerw/tts/speech_tools/bin:$PATH
export ESTDIR="/Users/stylerw/tts/speech_tools"
export FESTVOXDIR="/Users/stylerw/tts/festvox"

9. Don’t bother with the “prompt them” script for recording. It’s a gigantic pain. Instead, do any recordings in . Then, for instance, if you’re recording files for a clock, split the recorded prompts into “time0001.wav”, “time0002.wav”, etc. If you want to attempt “prompt them”, you’ll need to install sox (sudo port install sox) then change any calls to na_play with “play” and the na_record line with ” rec wav/$f.wav trim 0 $duration” (Thanks to ).

10. From there, run whatever tutorial you’d like, you should be good to go. Also, sorry, but I can’t really support this method. Please don’t email me or comment looking for additional tech support information about this.

Enjoy! (and sorry for the exceptionally dry post, but this is a useful bit of information to have out there :))

Tagged with Computers and Software | 3 Comments


This morning, I stumbled Adobe Systems Incorporated’s Permissions and Trademark Guidelines. This is basically Adobe’s way of dictating how it wants people to use and display its trademarks. Many companies have these, but Adobe’s policies regarding Photoshop are more restrictive (and thus, more laughable) then most.

Photoshop “to photoshop” out of your lexicon

They begin the Photoshop section with the phrase “Trademarks are not verbs”. Here, they’re objecting to the ubiquitous use of “to photoshop”, meaning “to use Adobe® Photoshop® software or similar image manipulation software to manipulate an image”. This prohibits phrases like “Dude, that is so photoshopped” or “the printing company photoshopped it for us”. This seems to be a common theme, with paralells to Xerox fighting to stop us from Xeroxing documents, but it’s still a bit crazy.

I think it’s ridiculous that they think they can stop this usage. One of the unifiying features of human language is our lazyness, and our desire to only do the minimum amount of speaking necessary. To think that we’ll gladly surrender “Could you photoshop this real quick?” in favor of “Could you enhance this image using Adobe® Photoshop® software real quick?” is completely insane.

The fact of the matter is that the verbed form is more versatile as well. In English, we can use other particles to change the meanings of an established verb, and “to photoshop” is no exception. One can photoshop something in, photoshop it out, photoshop something away, and so on. However, one cannot “enhance using Adobe® Photoshop® software out the guy in the background”. Instead, we’re asked to “enhance an image using Adobe® Photoshop® software in such a way that the guy in the background is removed from the picture”. Yeah, we’re going to do that, Adobe. Sure thing.

Adobe doesn’t know what they want

The real beauty comes in that the next heading: “Trademarks are not nouns”. Adobe, you’re in blatant violation of your own trademark policies on this very website.

…and Photoshop is one of Adobe’s most valuable trademarks…
…Adobe and Photoshop are either registered trademarks or trademarks…
…Get everything in Photoshop CS3 plus tools for editing 3D and motion-based content and performing image analysis….

In each of the above phrases, “Photoshop” is acting as a noun. So, I don’t think noun-like usage is what Adobe’s really worried about. Let’s look at their explanation:

CORRECT: The image pokes fun at the Senator.
INCORRECT: The photoshop pokes fun at the Senator.

It looks like what they’re really trying to ban is “Photoshop-Related Metonymy“. Metonymy is where a commonly associated element (or part of something) is used to refer to the whole thing. For instance, “The White House was silent on the corruption charges” or “The press is more and more biased every day” are both metonymic expressions, using parts of these establishments to represent the whole.

So, although I suspect they have no problem with noun form use (“Photoshop® is exceptionally good at what it does”), they’re worried about metonymy with manipulated images, like “Photoshops are causing more scandals every day for the embattled prince”. Perhaps they should be clarifying that on their website, lest they be forced to sue themselves.

Other miscellaneous escapes from reality

According to Adobe, “Trademarks may never be used as slang terms”. This is just charming because it’s an attempt to control casual usage. I can understand their not wanting an ad campaign with “Help Photoshoppers Photoshop better”, but trying to regulate casual conversation shows Adobe to be out of touch with not only language usage, but with reality.

Finally, I’m not sure I buy this “Proper Adjectives” thing. To claim that “Adobe Photoshop” is incorrect and meaningless without adding “software” is a bit ridiculous. Whether or not they want to pretend that Photoshop isn’t a noun, it won’t really change how speakers view and use the term. It just makes them seem stodgy and delusional.

Adobe Systems Incorporated v. Continental Drift

I’ve said it before, and I’ll say it again: A speaker (or grammarian) trying to stop language from changing is like a gardener trying to stop continental drift.

Adobe can write this up, and heck, they can even try and enforce parts of it with marketing and high-profile cases. However, I hope they realize the folly of trying to change established words and constructions, especially when the ones suggested are longer and less useful than the originals. No matter what they do, in everyday speech, people will photoshop images, those images will be photoshops, and photoshopping will be an entertaining pastime on the internet.

Know, however, that we’re not doing it to hurt you, Adobe. Our language is a language of love for your software, and the fact that “Photoshop” is so ubiquitous is a sign of our respect for your work. So, dearest Adobe, please stick to manipulating images, and leave the language manipulation to us.

Tagged with Computers and Software, Conventional Linguistics, Corporate Language, Language Censorship, Language Change, Language Usage, Words, Phrases, and Idioms | 5 Comments

«Read newer posts — Read older posts »

All content © Linguistic Mystic 2006-2012 unless otherwise indicated.
Please contact me for permission to reprint or repost.

Site Information

  • Categories

  • Latest Non-linguistic Posts

  • Archives

    • Site features