Re: [whatwg] Internal character encoding declaration, Drop UTF-32, and UTF and BOM terminology

2007-06-24 Thread Ian Hickson
On Sun, 24 Jun 2007, Peter Karlsson wrote: > >> > >> I don't think forbidding BOCU-1 is a good idea. If there is ever a > >> proper specification written of it, it could be very useful as a > >> compression format for documents. > > > > BOCU-1 has been used for security attacks. It's on the "no f

Re: [whatwg] The issue of interoperability of the element

2007-06-24 Thread Silvia Pfeiffer
On 6/25/07, Maciej Stachowiak <[EMAIL PROTECTED]> wrote: Our current plan is to primarily support MPEG-4, including H.264/AVC video and AAC audio. We may support other codecs as well - it won't necessarily be the full set of codecs supported by QuickTime. This has been discussed to death already,

Re: [whatwg] The issue of interoperability of the element

2007-06-24 Thread Maciej Stachowiak
On Jun 23, 2007, at 10:58 AM, Ivo Emanuel Gonçalves wrote: Dear WHATWG members, It has come to my attention that Apple developers behind the WebKit platform, which powers the web browser Safari, apparently intend to support the video element of the HTML 5 spec, section 3.14.7. It's all fine a

Re: [whatwg] The issue of interoperability of the element

2007-06-24 Thread Silvia Pfeiffer
On 6/25/07, Spartanicus <[EMAIL PROTECTED]> wrote: Personally I detest Java (resource hog, slow as wading through molasses) and don't have it installed, so forgive my potential ignorance. Don't we all hate java? ;-) Why create an HTML element with the express purpose of supporting video nati

[whatwg] Usefulness of nested /

2007-06-24 Thread Simon Pieters
The spec suggests that and elements can be nested in different ways to represent different things. http://www.whatwg.org/specs/web-apps/current-work/multipage/section-phrase.html#the-kbd This was discussed on IRC: http://krijnhoetmer.nl/irc-logs/whatwg/20070615#l-294 Summary: * U

Re: [whatwg] The issue of interoperability of the element

2007-06-24 Thread Spartanicus
"Silvia Pfeiffer" <[EMAIL PROTECTED]> wrote: >> Imo for content providers to choose over Flash, client support >> needs to be close to Flash. Requiring IE and Safari users to go and >> download and install third party software to play content would imo be >> considered too much of a hindrance whe

Re: [whatwg] Internal character encoding declaration, Drop UTF-32, and UTF and BOM terminology

2007-06-24 Thread Peter Karlsson
Ian Hickson: >> I don't think forbidding BOCU-1 is a good idea. If there is ever a >> proper specification written of it, it could be very useful as a >> compression format for documents. > BOCU-1 has been used for security attacks. It's on the "no fly" list. Do you have any references on that, o

Re: [whatwg] The issue of interoperability of the element

2007-06-24 Thread Silvia Pfeiffer
On 6/24/07, Spartanicus <[EMAIL PROTECTED]> wrote: Imo for content providers to choose over Flash, client support needs to be close to Flash. Requiring IE and Safari users to go and download and install third party software to play content would imo be considered too much of a hindrance when Fla

Re: [whatwg] The issue of interoperability of the element

2007-06-24 Thread Spartanicus
"Silvia Pfeiffer" <[EMAIL PROTECTED]> wrote: >A element that is natively part of html and has a standard set >of API functions will enable applications that are impossible today, >even with embedded elements such as flash. > >Imagine e.g. a mash-up of video extracts from several video hosting >si

Re: [whatwg] The issue of interoperability of the element

2007-06-24 Thread Ivo Emanuel Gonçalves
On 6/24/07, Silvia Pfeiffer <[EMAIL PROTECTED]> wrote: A element that is natively part of html and has a standard set of API functions will enable applications that are impossible today, even with embedded elements such as flash. Imagine e.g. a mash-up of video extracts from several video hosti

Re: [whatwg] The issue of interoperability of the element

2007-06-24 Thread Silvia Pfeiffer
On 6/24/07, Spartanicus <[EMAIL PROTECTED]> wrote: Allan Sandfeld Jensen <[EMAIL PROTECTED]> wrote: >> Thus, I suggest to change the wording to "User agents must support >> Theora video and Vorbis audio, as well as the Ogg container format". >> >Or a clear sign that the video tag was doomed to f

Re: [whatwg] The issue of interoperability of the element

2007-06-24 Thread Spartanicus
Allan Sandfeld Jensen <[EMAIL PROTECTED]> wrote: >> Thus, I suggest to change the wording to "User agents must support >> Theora video and Vorbis audio, as well as the Ogg container format". >> >Or a clear sign that the video tag was doomed to failure anyway. I really >can't imagine Microsoft or

Re: [whatwg] Entity parsing

2007-06-24 Thread Anne van Kesteren
On Sat, 23 Jun 2007 20:12:45 +0200, Sam Ruby <[EMAIL PROTECTED]> wrote: Before, "A &mdash B" == "A — B", now "A &mdash B" == "A &mdash B". Is that what we really want? Testing with Firefox, the old behavior is preferable. Yeah, it makes sense to follow Internet Explorer 7 for this. -- Anne

Re: [whatwg] The issue of interoperability of the element

2007-06-24 Thread Allan Sandfeld Jensen
On Sunday 24 June 2007 01:07, Silvia Pfeiffer wrote: > Such a development is a clear sign to change the spec to require > theora/vorbis support instead of just recommending it. A baseline > codec has to be a requirement. > > Thus, I suggest to change the wording to "User agents must support > Theor