 | | PLEASE fix links
|
| 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: (URL) Mirror 4,> (all on one line). (...) (18 years ago, 17-Feb-07, to lugnet.admin.suggestions)
| | | | | 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 actually one of the short list of reasons why my Lugnet frequency has dropped (besides obviously the biggee, time constraints). I am getting more and more frustrated with the broken links as more and more people are using the web interface (...) (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)
| |
