

Re: Proposition on advanced URL features (#1)

From: Mirsad Todorovac <tm@rasips2.rasip.etf.hr>
Date: Tue, 28 Nov 1995 18:23:34 +0100 (MET)
Message-Id: <199511281723.SAA08479@rasips2.rasip.etf.hr>
To: S.R.E.Turner@statslab.cam.ac.uk (Stephen Turner)
Cc: tm@rasips2.rasip.etf.hr (Mirsad Todorovac), www-html@w3.org, www-talk@w3.org, uri@bunyip.com
> These are interesting ideas, and IMHO there may be a case for something like
> them. The things I wouldn't want to see implemented are the line numbers,
> unless it meant the nth line of the source (the nth line of the output changes
> every time I change my browser window size)

The line numbers are very usefull in preformatted documents though.
There should be a way to reference a line in HTML source, too, but note
that there can be new newlines inserted in HTML source without changing
appearance of the document.  It seems that linenumber addressing makes sense
only in preformatted documents, and it seemed nice to address eg. 3'rd
visible line in some preformatted text, without having to count lines of
heading which are not displayed.  For other documents, context-sensitive
addressing would make more sense, and addressing line in HTML source could
be a last resort.

>                                             and regexps (much as I use Unix
> myself, regexps seem designed to hinder rather than aid searching: let's
> stick to plain search strings).

Regexps don't hurt.  They are in standard C library, and people don't have to
know about them until maybe someday ...  However, they add some flexibility.

>                                 Another point about searching is that the
> same URL could then come out differently on different browsers if an
> <img alt> is used in HTML.

Searching is not likely to help in display-sensitive tags, it should be
avoided anyway if it doesn't display always. -- Mirsad
Received on Tuesday, 28 November 1995 12:27:47 GMT
