long URLs

Replies are listed 'Best First'.
Re: long URLs by grinder (Bishop) on Dec 23, 2001 at 18:59 UTC
Why do you think that the Chatterbox is slow? What reasons do you have to convince us that we should deactivate the Chatterbox nodelet? Why do you think KISS and Occam's Razor is an evil node, written by an evildoer? I subcribe to the Occam's Razor school of thought. Hell, I even programmed in Occam for a transputer in a previous life. Maybe the external web references in that other node could have been formed using the `[http://url\|title of web page]` method, but I'm not too fussed about that. Hell, a few months ago, a bug in Perl Monks' HTML met a bug in Mozilla and pages suddenly because tens of thousands of pixels wide. Stuff happens, deal with it. For these reasons and more, I downvoted your node. Another thing. I don't think the Freshmeat solution is a good one. It fails the print test (print the page and the information is useless). A better alternative would be to break long URLs automatically. Once upon a time, you could do such a thing in Netscape with the `<wbr>` tag, which would signal an optional word break. Perform a `$url =~ s{/}{/<wbr>}g` and you're set. Unfortunately, when the W3C got around to standardising HTML 4.0, in their infinite fooli^Wwisdom they refused to put it in the spec. Too bad. Hyphenation and justification (H&J) is really badly done on the web. Without the hint of something like `<wbr>` there is no way to deal with this elegantly. The real issue is not that long URLs are bad, it's just that browsers suck. -- `g r i n d e r just another bofh print@_{sort keys %_},$/if%_=split//,'= & *a?b:e\f/h^h!j+n,o@o;r$s-t%t#u';`	[reply] [d/l] [select]
(crazyinsomniac) Re: long URLs by crazyinsomniac (Prior) on Dec 24, 2001 at 06:56 UTC
This is a non issue. There is no problem with the "URL"s. This is a long url: http://www.uni-rostock.de/fakult/philfak/fkw/iph/strobach/veranst/mittelalter/OCKAMLAT.html What appears to be bothering you, is the fact that an "anchor", also referred to as a "html link" aka "href" is giving you trouble by preventing the text from wrapping. This has, and always will remain, a purely html display issue (why isn't your browser smart enough to handle this). People who post nodes should have enough common sense to limit the size of their HREF's. http://www.uni-rostock.de /fakult/philfak/fkw/iph/strobach /veranst/mittelalter/OCKAMLAT.html ___crazyinsomniac_______________________________________ `Disclaimer: Don't blame. It came from inside the void` `perl -e "$q=$_;map({chr unpack qq;H;,$_}split(q;;,qH*));print;$q/$q;"`	[reply]
(ar0n) Re: long URLs by ar0n (Priest) on Dec 23, 2001 at 22:43 UTC
It's not that my 19" monitor wouldn't be big enough chough* but it's said that there are people w/ 17" or even smaller displays.* What size your monitor is has very little to do with it. What's more to the point, is at what resolution someone's browsing. I have a 17 inch monitor, but my screen resolution is set to 1280 by 1024, and I don't have any problem viewing that 'evil node.' Try viewing it at a higher resolution. [ ar0n -- want job (boston) ]	[reply]

g r i n d e r just another bofh print@_{sort keys %_},$/if%_=split//,'= & *a?b:e\f/h^h!j+n,o@o;r$s-t%t#u';

`g r i n d e r just another bofh print@_{sort keys %_},$/if%_=split//,'= & *a?b:e\f/h^h!j+n,o@o;r$s-t%t#u';`