Re: A suggested tag

BruceLeban@akimbo.com
Sun, 13 Apr 1997 14:38:25 -0400 (EDT)


From: BruceLeban@akimbo.com
Date: Sun, 13 Apr 1997 14:38:25 -0400 (EDT)
Message-Id: <199704131838.OAA27135@mail.internet.com>
To: www-html@w3.org
Subject: Re: A suggested tag


>From:	msftrncs@htcnet.com (Carl Morris)
>I am not worried about words, what about long URL's?

Actually, there is a rule for just this case, it's just that browsers 
don't implement it along with lots of other things they don't implement. 
Everyone wants to re-invent the wheel.

The rule is that you can break a compound "word" after a / or - without 
inserting a hyphen. I.e., your url would hyphenate as
    http://
    199.120.83.179/
    msftrncs/
    products/
    onefossil/
    onefos-
    s1-
    ss2.txt.html
admittedly the break after a hyphen rule is a bad idea for URLs (although 
it works fine for most words) since you can't tell if the hyphen was 
inserted when the line broke or not. The reason for breaking after the / 
rather than before:
    http://199.120.83.179/msftrncs
    /products
    /onefossil/...
is that in normal English no word ends with a / so if a line ends with a 
/ you know the word has been broken. If you put the / (or hyphen for that 
matter) at the beginning of the next line you wouldn't know. Of course 
URLs *can* end in /, so nothing's perfect. I think the best thing is not 
to break the URLs, let all the table cells simply run over and make the 
text unreadable. As far as I can tell, making unreadable web pages is an 
art form.

    --- Bruce Leban
    Akimbo Systems
    http://www.akimbo.com/globetrotter
    Publish on the web without learning HTML! (Really.)