Slashdot Mirror

Subsetting is not EOT functionality - EOT is basically just a wrapper around a TTF file, and subsetting just involves modifying the TTF, so you can do exactly the same in browsers that read raw TTF files. I've written a font optimizer tool (open source) that does that. (Windows has an API to generate embedded fonts with subsetting, which the WEFT tool uses; I'm not currently aware of any other subsetting implementations.)

http://html5.org/tools/web-apps-tracker?from=1200&to=1201&context=10 -- I can't find that change in the WebKit repo quickly, but it must be after 2008-02-09. I don't have anything to cite for Chrome using WebKit from Saf3.1 or it being branched in Jan (though you should find that in the WebKit repo), as it was only ever said in IRC, by developers of the respective products. See if globalStorage exists in Chrome, as that was in WebKit then.

Actually, YouTube have provided feedback to the HTML 5 video element specification (and that feedback has led to spec changes):

• http://html5.org/tools/web-apps-tracker?from=1628to=1629
• http://html5.org/tools/web-apps-tracker?from=1629to=1630

Actually, YouTube have provided feedback to the HTML 5 video element specification (and that feedback has led to spec changes):

• http://html5.org/tools/web-apps-tracker?from=1628to=1629
• http://html5.org/tools/web-apps-tracker?from=1629to=1630

The actual removal can be found here.

"we need a codec that is known to not require per-unit or per-distributor licensing, that is compatible with the open source development model, that is of sufficient quality as to be usable, and that is not an additional submarine patent risk for large companies."

The sad thing is that Ogg/Theora is strong on all these points, and it's probably the only somewhat modern codec set that even comes close. Theora might not be state of the art, but it is orders of magnitude better 1980s tech that someone might propose as an alternative (and Vorbis clearly is a state of the art design).

Meanwhile the MPEG LA licensed codecs that Apple and Nokia are advocating have already landed several *licensees* in court for patent litigation, with two major cases ongoing. In particular the MPEG LA license agreement is quite specific that the license does not provide all the patents needed to implement the covered codecs. Some of the lawsuits have even been from members of the pool (such as Lucent), so paying up provides you with little protection from attack from the pool members, no zero protection from patent attacks by third parties.

Theora and Vorbis were designed to be free of serious patent problems. That doesn't mean that they are completely immune, *nothing can be* in our current patent climate. However, they should do better than their proprietary competitors... and the track record shows that.

From the page:

What part of initially suggesting Ogg Vorbis doesn't fit with the new quote? It just seems wierd. Like they could say what they mean, but not explicitly suggest Ogg.

A big advantage of XHTML was that the conversion to a parse tree was unambiguous. Why give up that at this late date?

The conversion of HTML5 to a parse tree is unambiguous too – the spec defines exactly what happens to any input document, including ones full of syntax errors. (Or at least it's unambiguous to machines – humans may have a harder time working out how a badly broken document gets parsed). There's currently an parse tree viewer from html5lib (Python and Ruby), and an independently-developed Java one, and some other private or incomplete implementations, and they should all give the same output for whatever input you try.