Ian Hickson schreef:
I've defined the parsing and conformance requirements in a way that
matches IE. As a side-effect, this has made things like "naïve"
actually conforming. I don't know if we want this.
As a front-end developer I'd say "no". This makes it much harder to read
the source code,
Øistein E. Andersen schreef:
Kristof Zelechovski wrote:
Only the vowel U can have either
This is not quite right. All Latin vowels (a, e, i, o, u, y) can take the
trema/diæresis
(ä, ë, ï, ö, ü in Dutch; ë, ï, ü*, ÿ** in French), and a, o, u can all be
umlauted (ä, ö, ü
in German).
On Sat, 11 Mar 2006, Henri Sivonen wrote:
> The encoding labels with LE or BE in them mean BOMless variants where
> the encoding label on the transfer protocol level gives the endianness.
> See http://www.ietf.org/rfc/rfc2781.txt When the spec refers to UTF-16
> with BOM in a particular endianness
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
Theora video and Vorbis audio, as well as the Ogg container format".
On 15 Jun 2007, at 2:5AM, Ian Hickson wrote:
> it's pragmatic (after all, why require the semicolon?), and is equivalent to
> not requiring quotes around attribute values.
This would be a good simile if it the optionality were systematic,
but it currently applies to a highly erratic set of entitie
Sander wrote:
> Are there any char-sets that have both umlaut and trema variations of
> characters?
Unicode does not make the distinction, so this is somewhat unlikely.
(Personally, I tend to think that the apparent preference for umlaut dots closer
to the letter than trema dots can be linked t
Hi,
There is currently no way to detect a change in the url of a page other
than polling for changes in document.location.hash all the time (which
is slow and potentially complex, and doesn't always work in IE -) or
listening for click events on all links (which doesn't catch changes not
started b
On 6/14/07, Ian Hickson <[EMAIL PROTECTED]> wrote:
On Sun, 5 Nov 2006, Øistein E. Andersen wrote:
>
> From section 9.2.3.1. Tokenising entities:
> > For some entities, UAs require a semicolon, for others they don't.
>
> This applies to IE.
>
> FWIW, the entities not requiring a semicolon are the
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 and well, but not a victory for web interoperability, as they
d
What should happen if you try drawing a 0x0-pixel repeating pattern?
(I can't find a way to make a 0x0 image that any browser will load,
but the spec says you can make a 0x0 canvas. Firefox and Opera can't
make a 0x0 canvas - it acts like it's 300x150 pixels instead. Safari
returns null from creat
I hadn't thought of that one ;-) (in Dutch there are no native words
with umlauts, only some of German or Scandinavian descent).
My question was about char-sets that contain both a trema version and a
(seperate) umlaut version of the same character. Are there any?
cheers,
Sander
Kristof Zele
On Friday 15 June 2007 03:05, Ian Hickson wrote:
> On Sun, 5 Nov 2006, �istein E. Andersen wrote:
> > From section 9.2.3.1. Tokenising entities:
> > > For some entities, UAs require a semicolon, for others they don't.
> >
> > This applies to IE.
> >
> > FWIW, the entities not requiring a semicolon
On Sat, 11 Mar 2006, Henri Sivonen wrote:
>
> I think allowing in-place decoder change (when feasible) would be good
> for performance.
Done.
> > > I think it would be beneficial to additionally stipulate that
> > >
> > > 1. The meta element-based character encoding information declaration
>
13 matches
Mail list logo
