<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<br>
<br>
Benjamin Hawkes-Lewis wrote:
<blockquote cite="mid1167386283.14280.36.camel@galahad" type="cite">
<pre wrap="">FROIDURE Nicolas wrote:
</pre>
<blockquote type="cite">
<pre wrap=""> - 2 attributes for <textarea> : max (like other fields) and type
(to specify a text mime type for the content edition bbcode, html,
xhtml, xbbcode etc...). It will be a good way to improve the quality
of the web by improving the quality of user interventions.
</pre>
</blockquote>
<pre wrap=""><!---->
Already done, see maxlength and type at:
<a class="moz-txt-link-freetext" href="http://www.w3.org/TR/web-forms-2/#extensions1">http://www.w3.org/TR/web-forms-2/#extensions1</a>
Although as I've pointed out before, MIME types are not a sufficiently
specific tool: they don't differentiate between different versions of
HTML, can't suggest microformats, can't differentiate between full
documents and fragments, and so forth. Also BBCode, XBBCode, and the
various Wiki dialects don't even have MIME type. (Mind you, WHATWG could
actually submit some MIME type registrations to make type work a bit
better for the real web.) So this area still desperately needs more
work.
</pre>
</blockquote>
Maybe that the DTD syntax could be use. The official DTD for W3C
standards and a personal DTD for other languages. In all cases, i think
that bbcode, wiki and other 'easy' web languages with disappear when
browsers will include real WYSIWYG editors.<br>
<blockquote cite="mid1167386283.14280.36.camel@galahad" type="cite">
<blockquote type="cite">
<pre wrap=""> - 1 attribute for <input> : autocomplete (it exists in XUL, a
value could be an URL to load when some contain is typed).
</pre>
</blockquote>
<pre wrap=""><!---->
Autocomplete already exists as an security attribute for banks to use
and browser developers not to implement:
<a class="moz-txt-link-freetext" href="http://www.w3.org/TR/web-forms-2/#the-autocomplete">http://www.w3.org/TR/web-forms-2/#the-autocomplete</a>
(Well, it works in Safari and OmniWeb which can subvert nonce-based
methods of preventing the autofilling of passwords.)
However, the autocompletion functionality you're talking about is
essentially provided by:
<a class="moz-txt-link-freetext" href="http://www.w3.org/TR/web-forms-2/#the-datalist">http://www.w3.org/TR/web-forms-2/#the-datalist</a>
and
<a class="moz-txt-link-freetext" href="http://www.w3.org/Submission/web-forms2/#fetching-data">http://www.w3.org/Submission/web-forms2/#fetching-data</a>
</pre>
</blockquote>
Marvelous <span class="moz-smiley-s1"><span> :-) </span></span><br>
<blockquote cite="mid1167386283.14280.36.camel@galahad" type="cite">
<pre wrap="">
</pre>
<blockquote type="cite">
<pre wrap=""> - 1 attribute for code : type.
</pre>
</blockquote>
<pre wrap=""><!---->
Not done really. One option would be to add microformats to the Wiki for
different languages, I suppose. If you were to do so, I suggest
including version numbers. PHP4 should not necessarily be highlighted
the same as PHP5. Otherwise one might as well use type and MIME types,
just as for <script/>, although I suspect many languages lack MIME
types.
</pre>
</blockquote>
Maybe a syntax like this could be used :<br>
W3C official types list : PHP4 | PHP5 | JS | Java | (...) | _*<br>
The _ prefix should be used for personal (or non official) types.
Maybe another attribute indicating the plugin needed could improve the
functionality of this new feature.<br>
<blockquote cite="mid1167386283.14280.36.camel@galahad" type="cite">
<pre wrap=""></pre>
<blockquote type="cite">
<pre wrap=""> - maybe an attribute for em and strong. Something like "degree"
and a numeric value to notice the emphase degree of the sentences.
</pre>
</blockquote>
<pre wrap=""><!---->Whenever this semantic problem is raised, two alternatives are proposed:
either add an attribute to <em/> and <strong/> or specify the semantic
meaning of nesting <em/> and <strong/>. Web Applications 1.0 currently
goes for the second option:
</pre>
</blockquote>
It's strange. The em implementation in the CSS is approaching of the
first option. I think a degree attribute could correspond to the
font-weight graduation implemented with CSS.<br>
<blockquote cite="mid1167386283.14280.36.camel@galahad" type="cite">
<pre wrap="">
<a class="moz-txt-link-freetext" href="http://www.whatwg.org/specs/web-apps/current-work/#the-em">http://www.whatwg.org/specs/web-apps/current-work/#the-em</a>
<a class="moz-txt-link-freetext" href="http://www.whatwg.org/specs/web-apps/current-work/#the-strong">http://www.whatwg.org/specs/web-apps/current-work/#the-strong</a>
Question for the editor: how many <em/> equal one <strong/>?
--
Benjamin Hawkes-Lewis
</pre>
</blockquote>
By adding a smiley with Thunderbird, I'm wondering if any
standardization currently exists.<br>
<br>
Thanks for your answers, it was nice talking with you. By the way, do
you know if the CSS will allow to include SVG images to an HTML
document ? Will the HTML5 stop the XHTML 2 progression (i prefer use
XML...) ?<br>
<br>
Best regards, Nicolas FROIDURE<br>
<a href="http://bbcomposer.elitwork.com/home.html">BBComposer : XHTML,
BBCode, Wiki and XBBCode WYSIWYG Editor for Firefox</a><br>
</body>
</html>