-----BEGIN PGP SIGNED MESSAGE-----
On Tue, 14 Mar 2006 17:33:21 +0000,
Roy Schestowitz <newsgroups@xxxxxxxxxxxxxxx> wrote:
> __/ [ Peter Jensen ] on Tuesday 14 March 2006 16:30 \__
>> Roy Schestowitz wrote:
>>> ( ugly M$ URL: http://today.reuters.com/sponsoredby/amex/article.aspx ...
>>> ?type=innovationNews&storyID=2006-03-13T184438Z_01_L104 ...
>>> 36201_RTRUKOC_0_US-MEDIA-FRANCE-COPYRIGHTS.xml )
>> Sorry to bring this off-topic, but I have a comment about the way you
>> post long URLs. First, why not just all of it on one line? Surely that
>> is not breaking with netiquette, and I know of no news-reader that will
>> stop it (though some may complain). Second, if you must break, could
>> you perhaps do it without adding the space and dots at the end? A
>> regular broken-line URL can just be piped through 'tr -d \\n; echo' to
>> make it look nice. Not so for those lines. I know that you also
>> provide short-link versions, but I prefer not to use those for a variety
>> of reasons.
> You're quite right. There are arguments that go in both direction, but I'll
> take your preferred approach from now on.
> They are long essay that explain why long URL's should be avoided by Web
> sites. I think a good example of short URL's is the BBC. It gives context
> (section) while avoiding mysterious, excessively-long addresses that say
> plenty about the underlying CMS rather than the story.
> Best wishes,
It's especially annoying in that it's quite easy to set up Apache to
shorten URLs for you. But the writers of "yet another cms" don't seem to
have the vaguest idea how, more often than not. Sigh...
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v18.104.22.168 (GNU/Linux)
-----END PGP SIGNATURE-----
Jim Richardson http://www.eskimo.com/~warlock
Smut is one of the few things people will pay well for even if the
technology isn't very good.
-- Dale Worley