Subject: 32-bit PC-Pine: attachment filenames

From: Bill Stewart <[email-masked]>
Date: Mon, 16 Sep 1996 00:53:53 -0600

I'm using the Win32 winsock version of PC Pine.

Whenever I try to attach to a message, it seems that PC Pine has
real trouble with filenames that have spaces. The short-term
solution is to use the 8.3 filename of course, but this is
awkward because it's easier to be able to pick a file from a
list.

Are there any plans to fix this?

-----------------------------
Bill Stewart
[email-masked]
http://www.unm.edu/~wstewart/
-----------------------------

---

From: Ed Greshko <[email-masked]>
Date: Mon, 16 Sep 1996 16:52:53 +0800 (GMT)

> Are there any plans to fix this?

	I've not tried PC-Pine....but do you have any better luck if
you enclose the filename in quotes?

	Regared,

		Ed

-- 
Edward M. Greshko                       Technical Manager, Electronic Commerce
                                        Control Data Asia/Pacific Region
Voice: +886-2-715-2222 x287             6/F, 131 Nanking East Road, Section 3
FAX  : +886-2-712-9197                  Taipei, Taiwan R.O.C

---

From: Bill Stewart <[email-masked]>
Date: Mon, 16 Sep 1996 22:07:32 -0600 ()

On Mon, 16 Sep 1996, Ed Greshko wrote:

>I've not tried PC-Pine....but do you have any better luck if you
>enclose the filename in quotes?

(Regarding: tring to attach a file that has spaces in its name)

Thanks for the response. Yes, I tried quotes, and I tried
replacing the spaces with underscores, and I tried the
combination of both. Sometimes it seems to work at first, but
when I press ^X to send, it says "problem with attachment."

However, if I enter the "alias" filename, it works.

For example, suppose I want to attach a file called "Little
Picture.gif." I press ^J and enter "c:\pictures\Little
Picture.gif" (without the quotes). Pine doesn't like it. But if I
use "c:\pictures\little~1.gif" (the 8.3 alias), it works.

When you use ^T to pop up a list of files, it uses the Win32
common dialog box (which uses long filenames). This is a problem
because if you pick a file from the list, it inserts it correctly
onto the "attachment" header line in Pine, but it won't let you
send it.

This is probably something the Pine development team will want to
fix...