Fw: breaking with nonspace characters

-|- Carl Morris (N0YUV) -|- 1:285/302 -|- msftrncs@htcnet.com -|-
-|- Hooper Connections BBS -|- 1-(402)-654-2102 -|- 28.8kbps V.34 -|-
-|- http://199.120.83.179/~moreese/ -|-

----------
| From: Carl Morris <msftrncs@htcnet.com>
| To: Walter Ian Kaye <boo@best.com>
| Subject: Re: breaking with nonspace characters
| Date: Saturday, September 21, 1996 12:48 PM
| 
| At 5:39p -0500 09/20/96, Carl Morris wrote:
| >Is there any standard or proposed methods to break words apart
between
| >characters as if a space had been there only when needed ) (ie:
| >suggest) and to suggest that a word could be broken with a hyphen?
| 
| | How about the <WBR> tag and the &shy; (soft hyphen) entity?
| 
| <WBR> is Netscape support feature only, and most other browsers don't
| support it without the use of <NOBR></NOBR> ... which is not what I
| want to do ... I also think that no browser I have available to me
| supports &shy... but will try it in MSIE later on...
| 
| >http://home.aol.com/kiwi7416.  We also have our own WEB page
| >at http://199.120.83.179/msftrncs/ and at http://www.htcnet.com
| >/~msftrncs/msftrncs/index.html.  You may also get to the
| >ONEFOSsil page directly with http://199.120.83.179/msftrncs/
| >products/onefossil/index.html and with http://www.htcnet.com/
| >~msftrncs/msftrncs/products/onefossil/index.html
| 
| | You should enclose the URLs within <>'s so that software can parse
| them:
| 
| | at <http://199.120.83.179/msftrncs/> and at <http://www.htcnet.com
| | /~msftrncs/msftrncs/index.html>.
| 
| | Eudora Pro 3.0 recognizes the 2-line URL, thanks to the <>'s;
| otherwise
| | it doesn't know to include the second line as part of the URL. This
| | unambiguates the trailing period, too.
| 
| Sorry, thats a "software" feature and Microsoft proved its not
| required, MSIMN has "hyperlinked" every address in this message... 
| HTML doesn't need such conventions anyway ... this was an HTML file
| that includes anchors around the above mentioned URL's ... and the
| reason URL's were used is because this HTML is converted to TXT for a
| DOS based manual... nothing special about it...
| 
| | As far as the "/" goes, I think I prefer the break to occur before
it
| | rather than after it.
| 
| heres something to think about:
| 
| http:
| //www.
| htcnet.
| com
| /~msftrncs
| /msftrncs
| /products
| /nwsamd
| /index.html
| 
| or
| 
| http://
| www.
| htcnet.
| com/
| ~msftrncs/
| msftrncs/
| products/
| nwsamd/
| index.html
| 
| I think both ways have arguements ...  any one else care to say
| something?  (notice that my last algorythem breaks after consequetive
| slashes...)
| 
| >The other example...  spell out the word used in "marry poppens"
| (sure,
| >its in the dictionary even I think...), thats pretty long winded...
| >lets say it won't fit in a single line on the browser...  how can
the
| >browser be suggested of the proper points to break it, and place a
| >hyphen there when it does?
| >
| >no, I am not even going to try to write that word out here.. but we
| had
| >to know how to spell it in the 4th or 5th grade... (it starts
| >"super"...)
| 
| | supercalifragilisticexpialidocious  -- only 34 bytes long.
| 
| and so, the word we were looking for was
| supercalifragilisticexpialidocious, I hope in this example that you
see
| where the soft hyphens could be used :)
| 
| I think the point is, any time you have a word that is aproaching
half
| the display line in length, you aughta suggest where it can be
| hyphenated...  you don't have complete control over the widths or
| location of its appearence on the viewers screen.
| 
| Thanks
| -|- Carl Morris (N0YUV) -|- 1:285/302 -|- msftrncs@htcnet.com -|-
| -|- Hooper Connections BBS -|- 1-(402)-654-2102 -|- 28.8kbps V.34 -|-
| -|- http://199.120.83.179/~moreese/ -|- (and on
| www.htcnet.com/~msftrncs)
|

Received on Saturday, 21 September 1996 20:55:21 UTC