> It turns out, no, Unicode won't work, but using x\99 for the TM character > does, at least on my system (no idea if this will be universal): That's strange. Windows is Unicode based! All text operations done in Windows are first converted to unicode, calculated, and then back. That's even been mentioned on this list...