Thread: Pielrf - Text to LRF with Easy TOC, Headers, Curly-Quotes, etc. (Mac!)
View Single Post
Old 06-13-2007, 03:41 PM   #42
EatingPie
Blueberry!
EatingPie puts his or her pants on both legs at a time.EatingPie puts his or her pants on both legs at a time.EatingPie puts his or her pants on both legs at a time.EatingPie puts his or her pants on both legs at a time.EatingPie puts his or her pants on both legs at a time.EatingPie puts his or her pants on both legs at a time.EatingPie puts his or her pants on both legs at a time.EatingPie puts his or her pants on both legs at a time.EatingPie puts his or her pants on both legs at a time.EatingPie puts his or her pants on both legs at a time.EatingPie puts his or her pants on both legs at a time.
 
EatingPie's Avatar
 
Posts: 888
Karma: 133343
Join Date: Mar 2007
Device: Sony PRS-500 (RIP); PRS-600 (Good Riddance); PRS-505; PRS-650; PRS-350
Quote:
Originally Posted by JSWolf View Post
Not a problem. But can I ask that the new version be tested on a Windows environment (XP Please) so you can sort out the issues with the install and filename extensions? Thanks!

Jon
Indeed, I certainly plan to do so. I have already tested one zip utility and it seemed to work fine.

I am actually not sure what I want to do about the file extension. I prefer to keep it off, since it executes as a script correctly under Mac OS X and Linux (or any other UNIX supporting python). Windows requires you to either add the extension -- as you're suggesting -- or type "python" first.

While adding two letters isn't a big deal, the ".py" extension suggests a "library" as opposed to an executable command. Leaving it off means Windows users have to type "python" first, while putting it on means UNIX users may interpret it as a library function rather than an executable.

I'd love to hear what others think. This kind of issue is exactly why this thread exists!

-Pie
EatingPie is offline   Reply With Quote