| |
Can someone PLEASE fix the formatting for links in posts? While it may
work for FTX, it SUCKS in SeaMonkey/Mozilla/Thunderbird.
Example:
I'm reading from Tbird, and a post by someone has the following link:
<http://www.brickmodder.net/downloads/brickjournal/issue5/issue6.pdf
Mirror 4,>
(all on one line).
Clicking that link doesn't work, as it produces and invalid URL of:
http://www.brickmodder.net/downloads/brickjournal/issue5/issue6.pdfMirror4,
(again, all one line).
This gets annoying when trying to visit multiple links, as you have to
remember what text to remove (it's not always obvious), and completely
blows any chance of doing a Save As on a link to view later.
It's been broken since Day One of the FTX formatting in posts, and I've
not complained yet, but it's seriously starting to get to me.
<http://www.brickmodder.net/downloads/brickjournal/issue5/issue6.pdf
Mirror 4,> is NOT, NOT, NOT, I repeat NOT a valid URL to send to any
normal client! Until Lugnet releases FTX plugins for every known news
reader out there, it should NOT be sending/formatting invalid URLS for
the rest of the world.
It should be sending standard URL formatting like <a
href="http://www.brickmodder.net/downloads/brickjournal/issue5/issue6.pdf">
Mirror 4,</a>, or just sending the link text with the URL behind it in
parens:
Mirror 4 (
http://www.brickmodder.net/downloads/brickjournal/issue5/issue6.pdf )
(yet again, all one line)
Going against W3 standards isn't the brightest idea, it isolates you.
--
Tom Stangl
* http://www.vfaq.com/
* DSM Visual FAQ home
* 90 Talon AWD
* http://www.vfaq.net/
* Prius Visual FAQ Home
* 04 Prius AM #7
* 06 Prius NL #7
|
|
Message has 5 Replies:
 | | Re: PLEASE fix links
|
| As a note - my own post here via Tbird shows valid links for the first, third, fourth, and fifth URLs. So the incorrect links are most likely coming from direct web posting via Lugnet's interface. Its' engine (FTX, I'd assume) is creating invalid (...) (18 years ago, 17-Feb-07, to lugnet.admin.suggestions)
| | | Re: PLEASE fix links
|
| (...) After 7 years?!? OK, I put it to the list, but to be honest, this is not the most important thing I will work off, sorry! (...) I'm in favour of standards too, but I wouldn't see it so heavily dramatic ;-) -Rene (18 years ago, 17-Feb-07, to lugnet.admin.suggestions)
| | | Re: PLEASE fix links
|
| (...) I agree with this! Reading in a newsreader, I always have to copy the text of links and edit them before having a chance to use them in a browser. That's counterproductive, and makes me reluctant to follow most FTX links. (18 years ago, 17-Feb-07, to lugnet.admin.suggestions)
| | | Re: PLEASE fix links
|
| (...) This is already on the .suggestions sidebar list, and I seem to recall it was discussed some time ago, I found this: (URL) but I'm sure there was a more lengthy discussion, I just don't seem to be able to find the right search terms... ROSCO (18 years ago, 17-Feb-07, to lugnet.admin.suggestions)
| | | Re: PLEASE fix links
|
| (...) Which W3 standard does it go against? I'm not aware of any. RFC 1738 is vague on the issue. RFC 1738 says that space characters are not valid HTTP URL components; lexical scanners are therefore supposed to halt a URL production when they read (...) (18 years ago, 17-Feb-07, to lugnet.admin.suggestions)
|
7 Messages in This Thread:
 
 
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
