Troublesome comma
Herb
<http://www.guardian.co.uk/environment/georgemonbiot/2009/jul/22/george-monbiot-wind-power?showallcomments=true>
(search for my surname) is included in the link when one clicks on it,
leading to a broken link error?
In any case, I am somewhat disappointed that all FF has to say on the
matter is "The requested URL /, was not found on this server" (likewise
IE8), whereas Google Chrome helpfully suggests the correct URL as an
alternative.
--
Herbert Eppel
www.HETranslation.co.uk
Jay Garcia
--- Original Message ---
I don't see a comma at the end of your URL after scrolling endlessly to
find it. !!!
--
Jay Garcia - Netscape/Flock Champion
www.ufaq.org
Netscape - Flock - Firefox - Thunderbird - Seamonkey Support
Herb
> On 23.07.2009 08:24, Herb wrote:
>
> --- Original Message ---
>
>> How come the comma after the URL I provided in my comment at
>> <http://www.guardian.co.uk/environment/georgemonbiot/2009/jul/22/george-monbiot-wind-power?showallcomments=true>
>> (search for my surname) is included in the link when one clicks on it,
>> leading to a broken link error?
>>
>> In any case, I am somewhat disappointed that all FF has to say on the
>> matter is "The requested URL /, was not found on this server"
>> (likewise IE8), whereas Google Chrome helpfully suggests the correct
>> URL as an alternative.
>>
>
> I don't see a comma at the end of your URL after scrolling endlessly to
> find it. !!!
>
Thanks for your reply.
I'm not sure why endless scrolling was required - did you see my "search
for my surname" hint? O:-)
The link I'm referring to is "<http://prowa.org.uk/,>" - I should have
made this clear in my original message, sorry.
--
Herbert Eppel
www.HETranslation.co.uk
clay
> On 23.07.2009 15:22 UK Time, Jay Garcia wrote:
>> On 23.07.2009 08:24, Herb wrote:
>>
>> --- Original Message ---
>>
>>> How come the comma after the URL I provided in my comment at
>>> <http://www.guardian.co.uk/environment/georgemonbiot/2009/jul/22/george-monbiot-wind-power?showallcomments=true>
>>> (search for my surname) is included in the link when one clicks on
>>> it, leading to a broken link error?
>>>
>>> In any case, I am somewhat disappointed that all FF has to say on the
>>> matter is "The requested URL /, was not found on this server"
>>> (likewise IE8), whereas Google Chrome helpfully suggests the correct
>>> URL as an alternative.
>>>
>>
>> I don't see a comma at the end of your URL after scrolling endlessly
>> to find it. !!!
>>
>
> for my surname" hint? O:-)
I did. And, I did.
Don't see any url's in your blog, only links.
>
> The link I'm referring to is "<http://prowa.org.uk/,>" - I should have
> made this clear in my original message, sorry.
Don't see this url on your blog.
...maybe a copy and paste of the paragraph in question.
Andrew DeFaria
On 23.07.2009 15:22 UK Time, Jay Garcia wrote:
On 23.07.2009 08:24, Herb wrote:
--- Original Message ---
How come the comma after the URL I provided in my comment at <http://www.guardian.co.uk/environment/georgemonbiot/2009/jul/22/george-monbiot-wind-power?showallcomments=true> (search for my surname) is included in the link when one clicks on it, leading to a broken link error?
In any case, I am somewhat disappointed that all FF has to say on the matter is "The requested URL /, was not found on this server" (likewise IE8), whereas Google Chrome helpfully suggests the correct URL as an alternative.
I don't see a comma at the end of your URL after scrolling endlessly to find it. !!!Thanks for your reply.
I'm not sure why endless scrolling was required - did you see my "search for my surname" hint? O:-)
The link I'm referring to is "<http://prowa.org.uk/,>" - I should have made this clear in my original message, sorry.
When I can, I use HTML. When I have to use wiki like syntax on a forum or comment blog I look at the syntax and try to use the equivalent (e.g. [url=http://prowa.org.uk/]this link[/url]). Lacking that, if typing a URL and knowing that it ends in a "," or "." I type a space before it.
Pete Holsberg
<snip>
> The link I'm referring to is "<http://prowa.org.uk/,>"
The comma is enclosed between the angle brackets! If you do not want it
to be considered part of the URL, do this
Jay Garcia
--- Original Message ---
> On 23.07.2009 16:39, CET - what odd quirk of fate caused Herb to
> generate the following:? :
> the specified end of a URL is a break or a space. As there is no space
> nor line break, the link sees the comma as part of the URL.
> Try to get used to putting a URL in a separate line:
> http://like.this.com
> and continue the text again on a separate line. It may be grammatically
> incorrect, but it saves heartburn
>
> You could have written that URL like this http://prowa.org.uk/ ,
> continued line of text... that would have placed it correctly. Note the
> space before the comma, to separate the link from the text
>
>
> reg
That's one reason I don't put urls in < > ... If the < > are not added
then the offending comma would not have been part of the url. ;-)
Jay Garcia
--- Original Message ---
> On 23.07.2009 21:40, CET - what odd quirk of fate caused Jay Garcia to
> actually, Jay... the reason that URLs are put in angle brackets (by us
> here) is to prevent TB from performing a linebreak at 72 (or whatever)
> characters/line... the <....> keeps the URL in one piece (at least,
> that's the theory).
> But true - if Herb had done that, the link would still have been bummed,
> due to the comma not being separated.
>
> anyways - (hope - and in hope we live) Herb has learnt this lesson
>
> reg
>
I know what it's used for, I don't. And I never add a url anywhere close
to a line break, usually on a line by itself.
Pete Holsberg
That's one reason I don't put commas in < > If the comma had not been added,
it wouldn't have offended. ;-)
Pete Holsberg
> On 23.07.2009 17:09, squaredancer wrote:
>> actually, Jay... the reason that URLs are put in angle brackets (by us
>> here) is to prevent TB from performing a linebreak at 72 (or whatever)
>> characters/line... the <....> keeps the URL in one piece (at least,
>> that's the theory).
>> But true - if Herb had done that, the link would still have been bummed,
>> due to the comma not being separated.
>>
>> anyways - (hope - and in hope we live) Herb has learnt this lesson
>>
>> reg
>>
>
> I know what it's used for, I don't. And I never add a url anywhere close
> to a line break, usually on a line by itself.
Suppose you have a URL that is 142 characters long??? Some email editors
will add a newline after just so many characters.
Tarkus
> actually, Jay... the reason that URLs are put in angle brackets (by us
> here) is to prevent TB from performing a linebreak at 72 (or whatever)
> characters/line... the <....> keeps the URL in one piece (at least,
> that's the theory).
TB may wrap the link, but it does not insert a linebreak. The URL
remains in one piece. I've posted many, many links longer than one
line, so I know this from experience.
Now, the receiving software may break the link, but that's their problem
for using a crappy client.
Jay Garcia
--- Original Message ---
That's the very reason I use tinyurl. And when I use tinyurl, my
recipient's have no problem with it.
David McRitchie
> if a Maileditor is stupid enough to line-break where no line-break is
> intended.... then the programmer of that Newsreader is a twit!
Nonsense, there are lots of reasons for links to be be broken with a line-break.
Firefox 3.5 should be ignoring them if pasted to the location bar.
Open Long Url :: Add-ons for Firefox
"Adds an option to your File menu to allow you to open long, multi-line, urls. "
https://addons.mozilla.org/firefox/132
As far as the comma being included in a url that is just plain bad coding.
The poster should have included the information needed to find the
link not cryptic information which did not help. I found the link myself
by using a bookmarklet. "href:" described on my kws.htm page
though a keyworded bookmarklet is easiest to use,
something similar can be found in the Web Developer extension.
Web Developer --> Information --> Display Link Information
--
HTH,
David McRitchie, extensions I use are briefly documented on my site
Firefox Custom: http://www.mvps.org/dmcritchie/firefox/firefox.htm
Rick Carter
> That's the very reason I use tinyurl. And when I use tinyurl, my
> recipient's have no problem with it.
Ouch! You may know when to avoid misuse of commas and periods, but
apparently you still have a problem with using apostrophe's for
plural's. <g>
Ron Hunter
> On 23.07.2009 19:06, Pete Holsberg wrote:
>
> --- Original Message ---
>
>> Jay Garcia wrote:
>>> On 23.07.2009 17:09, squaredancer wrote:
>>>> actually, Jay... the reason that URLs are put in angle brackets (by
>>>> us here) is to prevent TB from performing a linebreak at 72 (or
>>>> whatever) characters/line... the <....> keeps the URL in one piece
>>>> (at least, that's the theory).
>>>> But true - if Herb had done that, the link would still have been
>>>> bummed, due to the comma not being separated.
>>>>
>>>> anyways - (hope - and in hope we live) Herb has learnt this lesson
>>>>
>>>> reg
>>>>
>>> I know what it's used for, I don't. And I never add a url anywhere
>>> close to a line break, usually on a line by itself.
>> Suppose you have a URL that is 142 characters long??? Some email editors
>> will add a newline after just so many characters.
>>
>>
>>
>>
>>
>
> That's the very reason I use tinyurl. And when I use tinyurl, my
> recipient's have no problem with it.
>
because they are afraid it will send them someplace they don't want to
go. For those people there is an extension that fetches, and displays
the full URL so that you can make up your mind.
Andrew DeFaria
That's the very reason I use tinyurl. And when I use tinyurl, my recipient's have no problem with it.I know what it's used for, I don't. And I never add a url anywhere close to a line break, usually on a line by itself.Suppose you have a URL that is 142 characters long??? Some email editors will add a newline after just so many characters.
Andrew DeFaria
Tarkus
An extra step, completely unnecessary for modern clients (including such
"modern" clients as 40tude Dialog, and, of course, Thunderbird).
»Q«
Herb <HE@UK> wrote:
I see the thread's been hijacked to talk about the comma itself.
When a URL isn't found on a server, the server responds with an html
page, and that's what Firefox is displaying. In this case, that server
isn't giving a very useful one, but some 'not found' pages are very
useful, with hints or search boxes for the site. If Chrome isn't
displaying the error page the server sends, I'd consider Chrome
broken; OTOH, if Chrome's helpful suggestion is in addition to
displaying the server's error page, that sounds like a good idea.
--
»Q« /"\
ASCII Ribbon Campaign \ /
against html e-mail X
<http://asciiribbon.org/> / \
Sjouke Burry
> On 23.07.2009 19:06, Pete Holsberg wrote:
>
> --- Original Message ---
>
>> Jay Garcia wrote:
>>> On 23.07.2009 17:09, squaredancer wrote:
>>>> actually, Jay... the reason that URLs are put in angle brackets (by
>>>> us here) is to prevent TB from performing a linebreak at 72 (or
>>>> whatever) characters/line... the <....> keeps the URL in one piece
>>>> (at least, that's the theory).
>>>> But true - if Herb had done that, the link would still have been
>>>> bummed, due to the comma not being separated.
>>>>
>>>> anyways - (hope - and in hope we live) Herb has learnt this lesson
>>>>
>>>> reg
>>>>
>>> I know what it's used for, I don't. And I never add a url anywhere
>>> close to a line break, usually on a line by itself.
>> Suppose you have a URL that is 142 characters long??? Some email editors
>> will add a newline after just so many characters.
>>
>>
>>
>>
>>
>
> That's the very reason I use tinyurl. And when I use tinyurl, my
> recipient's have no problem with it.
>
on a blogside.
I never click on a blogside, when I can avoid it.
At least give people a choice, and paste in both links.
Pete Holsberg
> Well, I hate tinyurls,and in the few cases I re-tried, ended up
> on a blogside.
What is a "blogside"?
»Q«
squaredancer <square...@t-online.de> wrote:
> ummm - yessss - but if you actually take the time out to READ the OP
> - and in it, the VERY FIRST LINE - you just MAY (if you are
> attentive enough) see this:
No need to shout.
> but of course - as you are probably still using your antiquated
> Newsreader.....
This had to do with a comma in a link on the web, nothing to do with
newsreaders. As for "antiquated", I'm using a much newer newsreader
than you are, and I wonder how long you can keep that chip on your
shoulder about it. I've set the followup to m.general in case you need
to go on some more about it.
> <<snipped previously discussed theories>>
Not only did I not post any "theories", I didn't post anything that had
already been discussed in the thread.
Andrew DeFaria
Jay Garcia
--- Original Message ---
Typo for blogsite?!
Herb
> How come the comma after the URL I provided in my comment at
> <http://www.guardian.co.uk/environment/georgemonbiot/2009/jul/22/george-monbiot-wind-power?showallcomments=true>
> (search for my surname) is included in the link when one clicks on it,
> leading to a broken link error?
>
> In any case, I am somewhat disappointed that all FF has to say on the
> matter is "The requested URL /, was not found on this server" (likewise
> IE8), whereas Google Chrome helpfully suggests the correct URL as an
> alternative.
Thank you for all the comments (pertinent and 'tangential').
Just a few points of clarification - apologies if my original message
wasn't entirely clear.
I'm well aware of the purpose/effect of the angle brackets, and I'm
therefore aware that the <http://prowa.org.uk/,> notation I used
therefore causes the comma to be included in the link when one clicks on it.
I merely posted <http://prowa.org.uk/,> here to illustrate the issue I
was referring to in my original message in relation to my comment at
<http://www.guardian.co.uk/environment/georgemonbiot/2009/jul/22/george-monbiot-wind-power?showallcomments=true>.
The problem is that the square brackets are probably distracting at best
in online forums (that 'activate' links - even long ones -
automatically) or may not even work (i.e. links inside square brackets
may not be recognised), so the best option is probably to try and avoid
the use of potentially troublesome punctuation even if it is
grammatically correct or indeed required, or to introduce a space before
the punctuation mark.
Nevertheless, I'll say again that I am somewhat disappointed that all FF
has to say if it encounters a link with a comma at the end is "The
requested URL /, was not found on this server" (likewise IE8), whereas
Google Chrome helpfully suggests the correct URL as an alternative.
--
Herbert Eppel
www.HETranslation.co.uk
Pete Holsberg
There <> are angle brackets. These [] are square brackets.
> Nevertheless, I'll say again that I am somewhat disappointed that all FF
> has to say if it encounters a link with a comma at the end is "The
> requested URL /, was not found on this server" (likewise IE8), whereas
> Google Chrome helpfully suggests the correct URL as an alternative.
I just pasted http://prowa.org.uk/, into Google chrome and did NOT get a
suggestion!! However, pasting <http://prowa.org.uk/,> into Chrome
triggers Google's search engine!!
When I do the latter in FF, openDNS makes a suggestion.
Opera offers to do a Google search as soon as that illegal string is pasted.
Herb
>> I merely posted <http://prowa.org.uk/,> here to illustrate the issue I
>> was referring to in my original message in relation to my comment at
>> <http://www.guardian.co.uk/environment/georgemonbiot/2009/jul/22/george-monbiot-wind-power?showallcomments=true>.
>>
>>
>> The problem is that the square brackets are probably distracting at
>> best in online forums (that 'activate' links - even long ones -
>> automatically) or may not even work (i.e. links inside square brackets
>> may not be recognised), so the best option is probably to try and
>> avoid the use of potentially troublesome punctuation even if it is
>> grammatically correct or indeed required, or to introduce a space
>> before the punctuation mark.
>
> There <> are angle brackets. These [] are square brackets.
Yes, sorry about the confusion.
>> Nevertheless, I'll say again that I am somewhat disappointed that all
>> FF has to say if it encounters a link with a comma at the end is "The
>> requested URL /, was not found on this server" (likewise IE8), whereas
>> Google Chrome helpfully suggests the correct URL as an alternative.
>
> I just pasted http://prowa.org.uk/, into Google chrome and did NOT get a
> suggestion!! However, pasting <http://prowa.org.uk/,> into Chrome
> triggers Google's search engine!!
I just pasted http://prowa.org.uk/, into Google Chrome and I get this:
***************************************************
Oops! This link appears to be broken.
Suggestions:
Go to www.prova.org
Go to www.prowa.co. uk
Go to prowa.org.uk
***************************************************
Not bad, and in any case better than FF's unhelpful message:
***************************************************
Not Found
The requested URL /, was not found on this server.
Additionally, a 404 Not Found error was encountered while trying to use
an ErrorDocument to handle the request.
Apache/2.0.63 (Unix) mod_ssl/2.0.63 OpenSSL/0.9.8e-fips-rhel5
mod_auth_passthrough/2.1 mod_bwlimited/1.4 FrontPage/5.0.2.2635 Server
at prowa.org.uk Port 80
***************************************************
I just realised that the FF message even contains the correct server
name, so why can't it make the link active?
--
Herbert Eppel
www.HETranslation.co.uk
Pete Holsberg
> I just pasted http://prowa.org.uk/, into Google Chrome and I get this:
>
> ***************************************************
> Oops! This link appears to be broken.
> Suggestions:
> Go to www.prova.org
> Go to www.prowa.co. uk
> Go to prowa.org.uk
> ***************************************************
>
> Not bad, and in any case better than FF's unhelpful message:
>
> ***************************************************
> Not Found
> The requested URL /, was not found on this server.
> Additionally, a 404 Not Found error was encountered while trying to use
> an ErrorDocument to handle the request.
> Apache/2.0.63 (Unix) mod_ssl/2.0.63 OpenSSL/0.9.8e-fips-rhel5
> mod_auth_passthrough/2.1 mod_bwlimited/1.4 FrontPage/5.0.2.2635 Server
> at prowa.org.uk Port 80
> ***************************************************
I pasted
http://prowa.org.uk/,
into Google Chrome and got this:
Not Found
The requested URL /, was not found on this server.
Additionally, a 404 Not Found error was encountered while trying to use
an ErrorDocument to handle the request.
Apache/2.0.63 (Unix) mod_ssl/2.0.63 OpenSSL/0.9.8e-fips-rhel5
mod_auth_passthrough/2.1 mod_bwlimited/1.4 FrontPage/5.0.2.2635 Server
at prowa.org.uk Port 80
???
Pete Holsberg
> Herb wrote:
>
>> I just pasted http://prowa.org.uk/, into Google Chrome and I get this:
>>
>> ***************************************************
>> Oops! This link appears to be broken.
>> Suggestions:
>> Go to www.prova.org
>> Go to www.prowa.co. uk
>> Go to prowa.org.uk
>> ***************************************************
>>
>> Not bad, and in any case better than FF's unhelpful message:
>>
>> ***************************************************
>> Not Found
>> The requested URL /, was not found on this server.
>> Additionally, a 404 Not Found error was encountered while trying to use
>> an ErrorDocument to handle the request.
>> Apache/2.0.63 (Unix) mod_ssl/2.0.63 OpenSSL/0.9.8e-fips-rhel5
>> mod_auth_passthrough/2.1 mod_bwlimited/1.4 FrontPage/5.0.2.2635 Server
>> at prowa.org.uk Port 80
>> ***************************************************
>
>
> I pasted
> http://prowa.org.uk/,
> into Google Chrome and got this:
>
> Not Found
>
> The requested URL /, was not found on this server.
>
> Additionally, a 404 Not Found error was encountered while trying to use
> an ErrorDocument to handle the request.
>
> Apache/2.0.63 (Unix) mod_ssl/2.0.63 OpenSSL/0.9.8e-fips-rhel5
> mod_auth_passthrough/2.1 mod_bwlimited/1.4 FrontPage/5.0.2.2635 Server
> at prowa.org.uk Port 80
I had suggestions turned off.
David Pyles
mistyped a URL.
Dave Pyles
Jay Garcia
--- Original Message ---
What you're describing is URL correction and the Netscape 9 devs created
that and they were supposed to be "code-sharing" since Netscape 9 is/was
sourced from Firefox. Guess nobody was interested.
Jay Garcia
--- Original Message ---
What I get with FF 3.5.1 is this:
The requested URL /, was not found on this server.
Additionally, a 404 Not Found error was encountered while trying to use
an ErrorDocument to handle the request.
No addons relative to the error are installed.
Ron Hunter
site, NOT suggest 100 sites similar to it, after referring me to another
place, losing all my laborious URL entering. REALLY ticks me OFF.
Jay Garcia
--- Original Message ---
That's not what the function does in NS 9. If you type www.somewhere.cmo
it corrects it to .com so forth and so on, it does not make 100's of
suggestions.
Ron Hunter
and presents me with a long list of what IT thinks I meant, and, in the
process, destroys whatever I typed. INFURIATING!
Jay Garcia
--- Original Message ---
The feature in NS 9 is not dependant on any ISP but rather an internal
database of correct syntax. com for cmo, net for ten, org for ogr and so
on for other common typos.
Andrew DeFaria
That depends on your ISP. Mine (Charter Pipeline) captures the error, and presents me with a long list of what IT thinks I meant, and, in the process, destroys whatever I typed. INFURIATING!
Ron Hunter
Andrew DeFaria
Humm. Can it tell if you mean whitehouse.gov instead of whitehouse.com? Grin.
Jay Garcia
--- Original Message ---
No because both are valid addresses and web sites. It doesn't correct
ignorance. :-D
Ron Hunter
years, direct mental interface.
Andrew DeFaria
I need a go where I mean, not where I say, routine. Maybe in a few years, direct mental interface.