lynx-dev
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: LYNX-DEV Internal MIME types


From: Wayne Buttles
Subject: Re: LYNX-DEV Internal MIME types
Date: Sun, 27 Apr 1997 01:24:20 -0400 (EDT)


On Sun, 27 Apr 1997, Al Gilman wrote:

>   From: Wayne Buttles <address@hidden>
>   Subject: Re: LYNX-DEV Internal MIME types
>   
>   Yes, except for how it relates to Lynx specifically.  To really make
>   things accessable things must be done at the server side (at least in
>   part).  There are already methods to accomplish what you are describing
>   (in this particular example) with the existing format.  This makes me very
>   skeptical that another format will force people to do the right thing.  
>   
> This is the point of my reply to Klaus.  We need to re-engineer
> the underlying model so it captures the information that the
> authors _do_ give us, better.  Presently there is some
> information that the authors would be glad to have captured as
> they create their pages, but it doesn't get represented in the
> Web media that are passed along.

I totally dissagree.  Just like people don't read the manual, people will
only do as much as they need to to get something done.  Unless you FORCE
them to create multiple views you can forget it.

> There has to be very little left over to "force people to do."
> It has to be easy as falling off a log to do it right.

I am writing a kids story and have a graphic of a puppy, but the name is
001.gif.  Here is my story:  

Then, the <img src="001.gif"> ran into the woods.

There is no way to get extra info out of that.  You need to force it
somehow.  Either it is a new graphic format with a manditory comment
section, a manditory ALT reference or whatever...it just can't be done
without changing the server and/or the creator.  It shouldn't have to
effect current browsers at all.

Anyhow, this is all pretty off base.  If some other format of web data
becomes the dominant method then someone will attempt a text viewer when
it happens.  Either it can become part of Lynx, replace Lynx or become
Lynx's helper.  Whatever.

Wayne

;
; To UNSUBSCRIBE:  Send a mail message to address@hidden
;                  with "unsubscribe lynx-dev" (without the
;                  quotation marks) on a line by itself.
;

reply via email to

[Prev in Thread] Current Thread [Next in Thread]