W3C home > Mailing lists > Public > whatwg@whatwg.org > December 2006

[whatwg] Graceful Degradation and Mime Types [was: trailing slash]

From: Karl Dubost <karl@w3.org>
Date: Mon, 4 Dec 2006 15:07:01 +0900
Message-ID: <D81A34DD-7EEC-4A5E-BD6E-AFBF8437833B@w3.org>

Le 4 d?c. 2006 ? 14:48, Mike Schinkel a ?crit :
>>> Consequently these systems implement some sort of
>>> markdown format that's simpler and allows users to
>>> enter data in plain text or increasingly with a WYSIWYG
>>> editor. All that's needed is for these systems to generate
>>> valid markup, and we're done. Mot users don;t need to
>>> know any details of this.
> Not all use markdown, many allow HTML, especially blogs.  And the  
> more I've
> thought about it, the more I think markdown might be a bad idea  
> (future blog
> post planned on that topic, once I've crystalized my full thoughts  
> on the
> matter.)

Give the possibility that the "textarea" of a form to trigger an  
editor, (A kind of setenv $EDITOR "editorname")(potentially wysiwyg).
and/or implement a real wysiwyg editor for forms in browsers (which  
sounds a bit silly when you really think about it)
There will be less nightmare of hand code editing.

> P.S. If markdown IS the answer, I think the W3C needs to define a  
> standard
> for such markdown.  There are too many competiting implementations for
> userrs to learn today.

hundreds, each developers implementing a Wiki is starting with the  
WikiWikiWeb syntax and then add stuff. If there is an abstract model  
of "Web Documents", then the rest is just a question of  
serialization. What Sam Ruby is doing in fact in the discussion.
	- textish format

Karl Dubost - http://www.w3.org/People/karl/
W3C Conformance Manager, QA Activity Lead
   QA Weblog - http://www.w3.org/QA/
      *** Be Strict To Be Cool ***
Received on Sunday, 3 December 2006 22:07:01 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:58:50 UTC