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 00:26:03 -0400 (EDT)


On Sat, 26 Apr 1997, Al Gilman wrote:

>   From: Wayne Buttles <address@hidden>
>   
>   What does "Orthogonalizing different dimensions of the content" mean?
> 
> Let us take a very small example: the counter that tells you that
> you are the 39457th visitor to the page.  Through a quirk of the
> standards, to make this dynamic, you have to make it an image.
> Despite the fact what the image shows is a bit map of text.

In this example, you are stating a falsehood.  There are some pages that
employ dynamic content that can send you the text.  I do get your meaning
though. 

> When the bitmap is build up by character values plus type face
> modulation, the characters can be stripped out and passed through
> text-to-speech for the blind.  When the bitmap of the characters
> is only passed as a GIF, the independence is lost and you eyeball
> it or nothing. 

The GIF spec actually has a comment field that could be used for dynamic
content... 

> The text-plus-font code is more orthogonalized,
> it is broken down into more components and the components are
> more independent in how you process them.  In the GIF case, there
> is a take-it-or-leave-it entirety, without any structure by
> which you can decompose and re-compose presentation views.
> 
> Is this any clearer?

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.  

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]