Basically, I selected ttxt because everybody (unless they've nuked it off their system) has SimpleText. Anytime we create documentation for IE/OE it gets saved either as "TEXT/MSIE" (Internet Explorer, for HTML), "TEXT/ttxt" (regular SimpleText -- actually, we seldom use this) or "ttro/ttxt" (SimpleText read-only, for stuff like readme and license files), because almost every Mac out there with Internet Explorer installed will understand those file types. This can cause problems, though, because if you have a TEXT/ttxt file that goes over SimpleText's limit (32K? I forget) you can't open it by just double-clicking. Better in that case to give it a creator type of a program that's actually on your system that doesn't have a limit, like BBEdit or Alpha. Final aside: A space is a legal character in a type or creator code. If you ever see a file with a creator code of YO! , you know it's actually "YO! ". Same goes for resource types, which <WHAP!>pummelpummelpummel dragdragdrag > -----Original Message----- > From: Brian McNett [mailto:webmaster@mycoinfo.com] > > And why are you using SimpleText (SmpleText?) anyway? Oh, > yah, the original poster wanted that. ;-) Well, for everyone > else, why not set the creator code to something more useful, > like McPL, or R*ch (MacPerl or BBEdit)? Aside: file type and > creator codes can be mixed-case, and may contain 8-bit > characters like "Mërc" and "Mpïf" (plug-in files for the > shareware game "Escape-Velocity, FYI). > ===== Want to unsubscribe from this list? ===== Send mail with body "unsubscribe" to macperl-request@macperl.org