Re: [whatwg] [HTML5] Accessibility question - SSML
Well I already do include embedded SSML on my website. I also submitted some XSLT to transform XHTML into a full SSML document which can be piped to speech synthesisers like Swift, that understand the format. http://bugs.webkit.org/show_bug.cgi?id=10363 On 18 Mar 2008, at 10:23 pm, Keryx Web wrote: Benjamin Hawkes-Lewis skrev: I think it's a mistake to assume a accessible or screen-reader- friendly view should be non-interactive. In so far as this is true at all, it's largely a result of web interactivity depending on non-standard widgets. AFAICT, this is one of the problems HTML5 tries to solve. Hear, hear! We also need to work with screen readers and browser developers so that that CSS media rules actually start to be applied. And Webkit should join the ARIA party! A thought (an just a thought), however, that might be worth investigating is if SSML could be embedded into HTML, using similar principles as is being considered for SVG. Lars Gunther — Nicholas Shanks. smime.p7s Description: S/MIME cryptographic signature
Re: [whatwg] A comment to character encoding declaration
On Mar 7, 2008, at 10:12, Jjgod Jiang wrote: On Fri, 7 Mar 2008, Alexey Proskuryakov wrote: In my testing, it appears that IE 7 and Firefox 2 do treat GBK as an equivalent of GB2312, but this cannot be said about GB18030. In particular, 0x80 and 0xA2E3 are treated differently. Yep, I missed that point in my previous post, my fault. Yes, they should be treated differently. So I guess my request should be changed to only treat GB2312 as GBK. According to source code[1], WebKit trunk also changes GB_2312-80 to GBK. Gecko aliases gb_2312-80 to GB2312 (due to FrontPage output according to source comment). Also, WebKit changes KS_C_5601-1987 and EUC-KR to windows-949-2000. Gecko aliases[2] KS_C_5601-1987 to x-windows-949 (due to FrontPage output according to source comment). However, Gecko doesn't use its alias mechanism to alias EUC-KR to windows-949. I haven't tested if EUC-KR is treated equivalently to windows-949 by other means. Yet another weird alias tidbit supported both by Gecko and WebKit source as well as Googling the subject: Looks like x-x-big5 needs to be an alias for Big5 due to FrontPage output. [1] http://trac.webkit.org/projects/webkit/browser/trunk/WebCore/platform/text/TextCodecICU.cpp#L90 [2] http://mxr.mozilla.org/seamonkey/source/intl/uconv/src/charsetalias.properties#335 -- Henri Sivonen [EMAIL PROTECTED] http://hsivonen.iki.fi/
Re: [whatwg] Legal colspan values
On Tue, Mar 18, 2008 at 2:23 PM, Christoph Päper [EMAIL PROTECTED] wrote: + h4Attributes common to codetd/code and codeth/code elements/h4 + pThe codetd/code and codeth/code elements may have a dfn + title=attr-tdth-colspancodecolspan/code/dfn content + attribute specified, whose value must be a spanvalid non-negative + integer/span greater than zero. Isn't that the description of a valid positive integer? If that term is not used or defined yet, why not? The mathematical definitions of positive and negative integers exclude zero, but the less-expert reader might not realize that zero is not valid for colspan unless it is made explicit. integer greater than zero would be one way to say it. Otherwise positive non-zero integer? March 14th was Talk like a physicist day. Is there a connection? I doubt it.
[whatwg] Typo in section 4.6.2 Application Caches
The text: A browsing context can be associated with an application cache. A child browsing context is always associated with the same browsing context as its parent browsing context, if any. should be: A browsing context can be associated with an application cache. A child browsing context is always associated with the same *application cache* as its parent browsing context, if any. Anders
