FREEPAGES-ADVANCED-L Archives

Archiver > FREEPAGES-ADVANCED > 2007-04 > 1175628283


From: "Jill Muir" <>
Subject: Re: [FP-ADVAN] Unable to ftp
Date: Tue, 3 Apr 2007 20:24:43 +0100
In-Reply-To: <e3afe72a0704011736q1280c6bdo83f031a260773090@mail.gmail.com>


I thought that Judy was simply trying out a way of triggering the server to
reject her file, so that the person she was helping would better understand
why their file was triggered.

As I read it Judy was being helpful and not uploading one of her files with
an error.

Best wishes, Jill
http://goldenridge-genealogy.co.uk
SEO Work page:
http://goldenridge-genealogy.co.uk/about-our-site.htm


-----Original Message-----
From:
[mailto:] On Behalf Of Judy Florian
Sent: 02 April 2007 01:37
To:
Cc:
Subject: Re: [FP-ADVAN] Unable to ftp

I just did an experiment to my PAGenWeb on RW account on the issue of file
accept on RW specifically.

I had a page named aldous_to_allan which was already successfully uploaded
weeks ago.

Tonight I took that page, did save as, and named it aldous_to,allan
no space, just the replacement of one underscore with one comma.

This was rejected... message on the problem was File Accept on Server.

If you do your own experiment, you will find which characters are NOT
accepted on RW. These same characters are valid as files on Windows.

Hope this helps explain more.

Judy


On 4/1/07, Glenn Holliday <> wrote:
>
> Patricia Geary wrote:
> > Replies are inline-
> >
> >
> >> 2. Characters in file names. Submitters who are used to using commas
> >> in names on WinXP send me files with lots of commas (and spaces). I
> have to
> >> double-check each to make sure I re-named every file. The only
> characters
> >> allowed at - hyphen or _ underscore. Double periods before an
> extension on
> >> jpgs (as sent to me) would not upload.
> >>
> The advice to be cautious is good, but I'm just checking a point or two
> here ...
> The characters allowed in a URL (or URI) besides the things like / that
> mark
> the different parts of the URL are alpha, numbers, and
>
> - _ . ! ~ * ' ( )
> Most operating systems reserve * to mean something else, so
> you can't use that one. The rest are OK in both MS Windows
> file names and URLs on the Web. In Unix ' ( ) are legal but
> also used by most shells, so it's easy to confuse yourself
> if you use them. Programs that don't accept the legal characters
> are broken.
>
> > Very good advice. I see file names written as full sentences with
> > punctuation AND double file extensions.
> >
> Do you mean RootWeb has trouble with file names that include more than
> one dot/period? A URL doesn't care how many dots are in the
> file name. The suffix after the last dot is still widely used to hint
> what the
> type of the file is, but "double file extensions" have been legal
> since MS Windows abandoned the old 8+3 file naming convention.
> Some email programs assume that an attachment named with 2 dots
> is a virus, but that's a different problem.
>
> I'm not surprised that some programs dislike double dots, but if they
> follow the rules they should not care about that either. I prefer to
> discard programs that have bugs like that, and encourage vendors who write
> better alternatives.
>
> It's always possible to use simpler filenames, and generally wise to be
> conservative.
> On the other hand, if you have already named files by the rules, you don't
> want to spend extra time trimming them back to fit additional conventions
> that don't help you. Do any of these examples help us avoid problems at
> RootsWeb?
>
> --
> Glenn Holliday
>
>
>

-------------------------------
To unsubscribe from the list, please send an email to
with the word 'unsubscribe' without
the quotes in the subject and the body of the message

--
This email has been verified as Virus free
Virus Protection and more available at http://www.plus.net

This thread: