Richard Rathe skrev/wrote: >... But doesn't the same problem crop up after you've done the conversion >with a text editor? I'd much rather work around the exceptions (the need >for weird characters in my files) than the rule (MacPerl blind to every >UNIX script in existence!) unix perl wants text files, macperl wants text files... If one transfers text unix <-> mac they have to be converted to the current OS text format, but most ftp clients do that >Another example is the directory delimiter. What >harm would be done if MacPerl automatically changed '/' to ':' and back >again when it works on directories and files? '/' is a valid character in names on macs. Should we escape it?? David Turley skrev/wrote: >(Now if I could only get GD.pm to install on my Unix >account) I have the same problem... Am I spoiled by the ease of macperl? Christian <http://www.solvare.se/individer/christian/> ________________________________________________________ Solvare - mathematics consulting & macintosh automation <mailto:info@solvare.se> <http://www.solvare.se> ***** Want to unsubscribe from this list? ***** Send mail with body "unsubscribe" to mac-perl-request@iis.ee.ethz.ch