Re: Lynx as primary browser (was Re: [Lynx-dev] how to maximize client area???)

2005-02-01 Thread Stef Caunter
I think this is a nice side effect to google optimization practices which are
filtering down to web developers. I've long thought that googlebot sees like
lynx, and perhaps there is now evident confirmation of this.

On Mon, 31 Jan 2005, Seth House wrote:

 Lynx should (and does) keep up with modern standards, and I believe
 that web designers are moving toward more Lynx-friendly practices. If
 you need proof hit the new Disney Store UK or Chevrolet websites with
 Lynx: they're beautiful!

 http://disneystore-shopping.disney.co.uk/store/Home.aspx
 http://www.chevrolet.com/


Stef


___
Lynx-dev mailing list
Lynx-dev@nongnu.org
http://lists.nongnu.org/mailman/listinfo/lynx-dev


Re: Lynx as primary browser (was Re: [Lynx-dev] how to maximize

2005-02-01 Thread David Woolley
 I know. I see the broad adoption of
 XHTML as a boon for Lynx since it facilitates more attention payed to
 document structure

I hope you realise that IE doesn't support XHTML so most of the
XHTML on the web is actually served as malformed HTML and therefore
is not checked for well formedness by browsers, so there is believed
to be an awfully large amount of not-well formed documents with
purporting to be XHTML.

In practice, until IE6 and down die, it would be better to serve
HTML written against a subset DTD with no optional tags (however
some legacy browsers may not like having explicit closing tags
on elements that are always empty).  (Actually, simply validating
an HTML document is sufficient because the ommission of tags is
only syntactic sugar and a validated HTML document has a well
defined parse tree and can be converted into canonical form (and
there are tools to do that).)

XHTML is used more for fashion and to look good on CVs.

Note that valid XHTML 1.1 will never work with IE because it is illegal
to serve it with a text/html media type.  IE will display valid 
XHTML 1.1 as the parse tree!


___
Lynx-dev mailing list
Lynx-dev@nongnu.org
http://lists.nongnu.org/mailman/listinfo/lynx-dev


Re: Lynx as primary browser (was Re: [Lynx-dev] how to maximize

2005-02-01 Thread Thorsten Glaser
David Woolley dixit:

XHTML is a clean start and certainly isn't intended to be backwards
compatible.

It is. XHTML/1.0 and HTML/4.02(iirc) are the same spec,
just one with XML constraints added.

The proposed XHTML/2 is a joke, but XHTML/1.1 is HTML/5.

XHTML 1.1 isn't backwards compatible, because there
are no compatibility hacks

Enough to please most browsers.

and text/html can't be used as the
media type.

It can, see my other eMail.

bye,
//mirabile


___
Lynx-dev mailing list
Lynx-dev@nongnu.org
http://lists.nongnu.org/mailman/listinfo/lynx-dev


Lynx as primary browser (was Re: [Lynx-dev] how to maximize client area???)

2005-01-30 Thread Thorsten Glaser
Stef Caunter dixit:

On Sun, 30 Jan 2005 [EMAIL PROTECTED] wrote:

 surely, anyone outside the poorest parts of the World today
 has access to Firefox, Konqueror  other graphical browsers,
 which display WWW pages as their authors intend them to be seen.

FUD.

* I design my web pages (e.g. http://mirbsd.mirsolutions.de/ ) to
  be optimised for Lynx and still look not too bad in Konqueror,
  and be XHTML/1.1 compliant.
* The only browser faster than Lynx is Dillo, which is just broken.
* Graphical browsers (especially Firefox(tm)) start _very_ slow and
  are _very_ ressource-hungry
* Graphical browsers imply a GUI, which is not always what I have
  (e.g. when I'm sitting on a vt420, or lending me a shell at a
  friend's laptop, ssh to home, lynx, have my bookmarks and cookies
  and all)
* Graphical browsers don't run in screen (I tend to kill my X by accident)

 Lynx still has important uses, but in limited contexts.

No, Lynx is the primary browser for many people, including myself.
I'm using it for about 98% of all websites. Links+ (in X11, with
pics) for 1.8% of all websites and as image-viewer (Manga scans,
e.g. www.narutofan.com has some), and Firefox(tm) or Konqueror,
depending on which is there, for the remaining 0.2%.

I think choice to have or not have indents is important; personally, I -dump
out pages and have to :%s/^   // out the spaces in vi, and anything over 79
cols wraps, (small gripe).

Funny enough, lynx -dump sometimes honours 80c and sometimes (eg.
when run in an xterm or from midnight commander, don't remember)
doesn't ;)

But post-processing in jupp (joe-editor.sf.net) is easy too.

But I won't see lynx marginalized here. For many people it is our primary
browser for HTTP; no one's personal usage has a priori primacy in a universal
context. The lynx browser is as useful as you choose to make it.

And it's the only browser I know which supports
* textfields-need-activation
* navigation by numbering links and form fields
* partial displaying with a threshold of 1
* a source view starting where in the rendered form
  of the page you're in right now
* tables rendered in a way not trashing keyboard navigation
  when not using numbered
* spawning $EDITOR on a form field (COOL!)

I miss a few things, but I can live with it.
And not one of these features I miss does a
graphical browser give me.

bye,
//mirabile


___
Lynx-dev mailing list
Lynx-dev@nongnu.org
http://lists.nongnu.org/mailman/listinfo/lynx-dev