Re: [whatwg] Entity parsing [trema/diaresis vs umlaut]

2007-06-26 Thread Křištof Želechovski
Of course you are right; I was thinking of the tréma when I wrote that and I changed it to a dieresis afterwards to make it more English (to get rid of the red underlines). A general qui pro quo followed. Slovak ä is an original invention; the tréma palatalizes the preceding consonant. I did

Re: [whatwg] Entity parsing

2007-06-26 Thread Křištof Želechovski
The difference between I.2 and I.3 is that I.2 is in English and I.3 is in French. Internet Explorer apparently chose to support English natively while SGML preferred remaining language-agnostic. Chris -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of

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

2007-06-26 Thread Maik Merten
Silvia Pfeiffer schrieb: So a company which owns a patent on a standard that can bought and read at freedom is just as bad as a company which owns a patent on a standard that has absolutely no public documentation? If you're talking about Ogg Theora, then you've got your facts wrong. First

Re: [whatwg] Gears design goals

2007-06-26 Thread timeless
Aaron Boodman wrote: - One major issue that we found here was that lots of existing applications serve different resources at the same URI depending on who is logged in. We could ask these applications to redesign so that they don't do that, but we would prefer to not have to. On 6/26/07,

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

2007-06-26 Thread timeless
On 6/26/07, Spartanicus [EMAIL PROTECTED] wrote: Desktop client content support will determine the format most content will be published in. Interesting claim, however Apple so far has introduced AAC (high quality drm-less) and MPEG4 for large audiences (OK, YouTube MPEG4 is merely announced

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

2007-06-26 Thread Spartanicus
timeless [EMAIL PROTECTED] wrote: Desktop client content support will determine the format most content will be published in. Interesting claim, however Apple so far has introduced AAC (high quality drm-less) and MPEG4 for large audiences (OK, YouTube MPEG4 is merely announced and not

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

2007-06-26 Thread Jerason Banes
I believe an aim of whatwg is a viable implementable standard that reflects the realities of the web while encouraging innovation. MPEG4 is part of the web (a growing part too). If I may, I'd like to echo Timeless's point here. I've been watching this thread with great interest and believe I

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

2007-06-26 Thread Charles Iliya Krempeaux
Hello Jerason, From a technical point-of-view, you make a very good argument. However, I think it is inappropriate for the HTML spec to (directly or indirectly) mandate people pay to implement it. As you point out, H.263 is encumbered by patents and has licensing costs associates with it.

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

2007-06-26 Thread Maik Merten
Jerason Banes schrieb: Out of those solutions, VP6, WMV, Sorenson, and RealVideo can immediately be discarded for their lack of standardization. That leaves H.263 and MPEG4 as the only viable options. H.263 is not a bad choice, IMHO. It's well supported by nearly every major video player,

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

2007-06-26 Thread Jerason Banes
Hi Charles, While I agree with your sentiment, I don't see a better option. The purpose of the HTML5 spec is to provide a unified web applications platform that supports the existing web in a practical manner. If the spec sticks with Theora as the baseline implementation, it runs the risk of no

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

2007-06-26 Thread Maik Merten
Jerason Banes schrieb: * The spec can specify Theora as the baseline, very few browsers will implement it, few users will use it (due to a lack of support), and thus the intent of standardizing on a free format will be lost. Opera and Mozilla already have implemented

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

2007-06-26 Thread Maik Merten
Jerason Banes schrieb: If that's true, then I'm greatly relieved. VP3 (the source of Theora) is generally compared to MPEG1, a standard far exceeded by H.263. I have not seen any publicly available Theora benchmarks that would overturn such impressions. (Do any exist?) Most public benchmarks

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

2007-06-26 Thread Jerason Banes
On 6/26/07, Maik Merten [EMAIL PROTECTED] wrote: Opera and Mozilla already have implemented (early) Ogg Vorbis and Ogg Theora support. And (if this thread is any indication) are likely to be the only ones. Internet Explorer still holds the majority of the market, and Safari is still the

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

2007-06-26 Thread Maik Merten
Jerason Banes schrieb: On 6/26/07, *Maik Merten* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Opera and Mozilla already have implemented (early) Ogg Vorbis and Ogg Theora support. And (if this thread is any indication) are likely to be the only ones. Internet Explorer

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

2007-06-26 Thread carmen
But I don't accept that idealistic advocacy regarding encoding format support for the video element is pointless in the situation in which we are today where the market leaders haven't yet decided what they are going to do. they havent? it seems pretty clear to me adobe - push swf/flv/apollo

Re: [whatwg] Gears design goals

2007-06-26 Thread Aaron Boodman
changing email addresses, sorry... On 6/26/07, Aaron Boodman [EMAIL PROTECTED] wrote: -- Forwarded message -- From: Robert O'Callahan [EMAIL PROTECTED] Date: Jun 26, 2007 2:56 AM Subject: [whatwg] Gears design goals To: whatwg@lists.whatwg.org Agree on all those. Great! So

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

2007-06-26 Thread Nicholas Shanks
I don't quite get some of the arguments in the thread. Browsers don't (and shouldn't) include their own av decoders anyway. Codec support is an operating system issue, and any browser installed on my computer supports exactly the same set of codecs, which are the ones made available via the

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

2007-06-26 Thread Geoffrey Sneddon
On 26 Jun 2007, at 00:57, Silvia Pfeiffer wrote: So a company which owns a patent on a standard that can bought and read at freedom is just as bad as a company which owns a patent on a standard that has absolutely no public documentation? If you're talking about Ogg Theora, then you've got

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

2007-06-26 Thread Silvia Pfeiffer
Hi Jerason, I think there may be a lack of information about Theora rather than anything else. On 6/27/07, Jerason Banes [EMAIL PROTECTED] wrote: If I may, I'd like to echo Timeless's point here. I've been watching this thread with great interest and believe I understand both sides of the

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

2007-06-26 Thread Geoffrey Sneddon
On 26 Jun 2007, at 17:46, Maik Merten wrote: * The spec can be practical about implementing the video tag and specify H.263 or MPEG4 as a baseline. Existing multimedia toolkits can be reused in implementation and thus all browsers can support the standard. Users

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

2007-06-26 Thread Robert O'Callahan
On 6/27/07, Jerason Banes [EMAIL PROTECTED] wrote: The question that I hate to ask (because it goes against my own grain to ask it) is, which is more useful to the web market: Asking Windows users to install Ogg/Theora codecs Actually, we just ask them to install Firefox :-) or asking Linux

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

2007-06-26 Thread Spartanicus
Silvia Pfeiffer [EMAIL PROTECTED] wrote: Opera have already implemented support for Ogg Theora and the video tag. (see http://video.google.com.au/videoplay?docid=5545573096553082541pr=goog-sl) Opera has published a one off interim experimental build (Windows only) with video support and native

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

2007-06-26 Thread Ivo Emanuel Gonçalves
I would like to make clear one more thing: When I attended the iCommons Summit earlier this month, I have met the project manager of the OLPC project, you know the $150 laptop for children in developing nations, and the information that I have right now is that it will not support proprietary

Re: [whatwg] Signed Numeric Type NOT_SUPPORTED_ERR

2007-06-26 Thread Michael A. Puls II
On 6/26/07, Simon Pieters [EMAIL PROTECTED] wrote: In http://forums.whatwg.org/viewtopic.php?t=69, Daren says: Upon reading the current work document, I encountered the following: Unless other specified, if a DOM attribute that is a signed numeric type is assigned a negative value, a

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

2007-06-26 Thread Michael A. Puls II
On 6/26/07, Silvia Pfeiffer [EMAIL PROTECTED] wrote: It is not true that Theora is not used today. revision3.net is another site that uses/provides Theora. http://revision3.net/diggnation With videolan at least, the theora ones use less cpu than the other formats, which makes it easier to