n a more general basis?
-h&kon
Håkon Wium Lie CTO °þe®ª
howc...@opera.com http://people.opera.com/howcome
ries were thought to be too far along the Recommendation track to
> be fixed. color/color-index/monochrome/scan/grid are also somewhat dubious
> in this day and age.
There are enough e-ink devices out there for color/monochrome to still
make sense. The others could probably b
that (and I'll do
> it off list, for th sake of the whatwg mailing list :-)
It's great if you can find information on this. I believe many people
on this list would be interested, so I suggest you send it to the
list.
Cheers,
-h&kon
Håkon Wium Lie CTO °þe®ª
howc...@opera.com http://people.opera.com/howcome
in your new experimental
service [4].
[4] http://www.youtube.com/html5
The web is based on free and open formats. Google would not have
existed without the web. It will be a terrible tragedy if you tip the
scales in favor of patent-encumbered formats on the web. We expect
higher standards from you.
tuck to the terms
> of the license instead of trying to parse the examples :)
The example in #11 seems fairly clear. Do you see any
incompatibilities between the example text and the general clauses?
Cheers,
-h&kon
Håkon Wium Lie CTO °þe®ª
howc...@opera.com http://people.opera.com/howcome
then the only way you could
satisfy both it and this License would be to refrain entirely from
distribution of the Library.
This if statement seems to be true, and I therefore still don't
understand your reasoning.
I do appreciate your willingness not discuss these matters, thou
tion.
I also understand that the LGPL doesn't explicitly "require [anyone]
to pass along patent rights we may have obtained elsewhere". However,
it seems quite clear that the intention of #11 is to say that you
cannot redistribute the code unless you do exactly that.
What am I missing?
-h&kon
Håkon Wium Lie CTO °þe®ª
howc...@opera.com http://people.opera.com/howcome
elated
> third-party is irrelevant as long as it doesn't prevent Party B from
> granting people the rights LGPL 2.1 requires they grant them (namely,
> only those rights it in fact received from Party A).
Thanks for your willingness to discuss these matters.
So, to be clear, you&#x
bute may still be a more
compelling option in a less-is-more way. It already exists and can
easily be used for styling purposes. Styling is bait for authors to
disclose semantics.
Cheers,
-h&kon
Håkon Wium Lie CTO °þe®ª
howc...@opera.com http://people.opera.com/howcome
end" -- that's a presentational issue.
Cheers,
-h&kon
Håkon Wium Lie CTO °þe®ª
howc...@opera.com http://people.opera.com/howcome
this works:
http://www.w3.org"; style="display:inline">W3C
But, the markup isn't pretty. Also, I'd like for links to use the
element.
-h&kon
Håkon Wium Lie CTO °þe®ª
[EMAIL PROTECTED] http://people.opera.com/howcome
Also sprach Philipp Serafin:
> > http://www.w3.org/";>W3C
> What's wrong with
>
> W3C
It's not a link. I'd like for buttons to work as links so that they
take me to a page when I click on them.
-h&kon
Håkon Wium Lie
.
Cheers,
-h&kon
Håkon Wium Lie CTO °þe®ª
[EMAIL PROTECTED] http://people.opera.com/howcome
h consensus and put the wording back in.
That will restore faith in HTML5 for many.
-h&kon
Håkon Wium Lie CTO °þe®ª
[EMAIL PROTECTED] http://people.opera.com/howcome
ext can be revised. But not before.
-h&kon
Håkon Wium Lie CTO °þe®ª
[EMAIL PROTECTED] http://people.opera.com/howcome
Håkon Wium Lie CTO °þe®ª
[EMAIL PROTECTED] http://people.opera.com/howcome
the quest for a better web. Not just a
better element.
Cheers,
-h&kon
Håkon Wium Lie CTO °þe®ª
[EMAIL PROTECTED] http://people.opera.com/howcome
Also sprach Bjoern Hoehrmann:
> > > the SVG 1.2 WD requires support for Ogg Vorbis:
> > > http://www.w3.org/TR/2004/WD-SVG12-20041027/media.html
> >And as Håkon Wium Lie
> >pointed out in another email, the latest SVG standard already mandates
> >Vorbi
twice as efficient as MPEG2,
> competitive with H264 and VC-1 and substantially more efficient
> than Theora.
Given that you are competitive with H264, are you also demanding the
same kind of processing power?
Cheers,
-h&kon
Håkon Wium Lie
losed source browsers -- except for vendors pushing a
proprietary media platform.
-h&kon
Håkon Wium Lie CTO °þe®ª
[EMAIL PROTECTED] http://people.opera.com/howcome
Also sprach Laurens Holst:
> > is *very badly* implemented. It has been a decade since
> > was first created and browsers STILL don't do it right in all cases (or
> > even in most cases, frankly). Adding more complexity to such a disaster
> > zone is bad design.
>
> If the existing pro
s.
For example, should the audio play in the background all the time? I
can see some neat effects, but more frustrated users.
Cheers,
-h&kon
Håkon Wium Lie CTO °þe®ª
[EMAIL PROTECTED] http://people.opera.com/howcome
d? On the
right-click menu or somewhere where it doesn't take up space?
-h&kon
Håkon Wium Lie CTO °þe®ª
[EMAIL PROTECTED] http://people.opera.com/howcome
http://my.opera.com/saito/blog/show.dml/787937
http://coolastory.blogspot.com/2007/03/sv-web-builders-event-world-premier-of.html
http://www.youtube.com/watch?v=hUqC1URVytk
http://www.youtube.com/watch?v=tKXomOLraXg
http://www.flickr.com/photos/biao/406571288/
http://www.flickr.com/phot
rld can
use.
If MPEG4 is the alternative, we might as well continue using Flash and
. But it's not a world I want to live in.
-h&kon
Håkon Wium Lie CTO °þe®ª
[EMAIL PROTECTED] http://people.opera.com/howcome
er, for whatever reason. Hopefully they will reconsider when
Wikipedia starts using it for real.
-h&kon
Håkon Wium Lie CTO °þe®ª
[EMAIL PROTECTED] http://people.opera.com/howcome
es devices with limited processing power. On the other
hand, these devices may also have limited connectivity so compression
is called for.
It would be interesting to see a comparison of video quality vs.
processing requirements.
-h&kon
Håkon Wium Lie
ding bet that computers we buy 40 years from now
(the bet was entered into ten years ago) will be able to read web
pages from 1997.
I think it's time to add video and audio codecs to this select list.
-h&kon
Håkon Wium Lie CTO °þe®ª
[EMAIL PROTECTED] http://people.opera.com/howcome
p in
mind that the specs we designs must be usable in many types of
enviroments.
-h&kon
Håkon Wium Lie CTO °þe®ª
[EMAIL PROTECTED] http://people.opera.com/howcome
enefit of actually working in my web browser. It
> also happens to be much simpler than the equivalent "HTML5" document.
It doesn't work in my browser. What does the code do?
-h&kon
Håkon Wium Lie CTO °þe®ª
[EMAIL PROTECTED] http://people.opera.com/howcome
u mean make the elements themselves optional to support?
Yes. If a vendor, for some reason, is unable to support the Ogg
codecs, I think it's better that they (a) do not support , than
(b) they support with proprietary codecs only.
Interoperability has more value than conforma
ments (for whatever reason) can still
comply with the spec. They can also support proprietary codecs through
.
-h&kon
Håkon Wium Lie CTO °þe®ª
[EMAIL PROTECTED] http://people.opera.com/howcome
Also sprach Laurens Holst:
> > http://www.whatwg.org/specs/web-apps/current-work/#video
> Correct me if I
or unresolved)
patent claims. I don't think this is the case for the codecs on the
other side of the t:video element.
-h&kon
Håkon Wium Lie CTO °þe®ª
[EMAIL PROTECTED] http://people.opera.com/howcome
s inappropriate while video is appropriate or vice versa?
I don't think so. Both deserve to be first-class citizens on the web
and they are, therefore, entitled to their own element.
-h&kon
Håkon Wium Lie CTO °þe®ª
[EMAIL PROTECTED]
so we shouldn't try
to change it.
Finally, I think open formats are better than closed formats. The
standards we write should not be neutral on this. Perhaps we should
not name specific formats, however, only require that codecs are
freely available for use across all platforms?
-h&kon
and that (b) many video formats are impossible to
support on all devices (mostly due to legal issue), I think we should
consider your proposal.
-h&kon
Håkon Wium Lie CTO °þe®ª
[EMAIL PROTECTED] http://people.opera.com/howcome
a simple way to add video to HTML
pages. I don't think one shoulr rely on other languages for this,
although I'm perfectly happy supporting those other languages as well.
Part of the reason why we could to this so quickly is the work we have
done on SVG.
-h&kon
s follows:
> `Don't wait for rec\-ord companies, re\-cord rec\-ords yourselves.'
is probably the best way to encode this. However, it can be done
through CSS as well:
Dont's wait for record
companies, record
yourself.
-h&kon
Håkon Wium Lie CTO °þe®ª
[EMAIL PROTECTED] http://people.opera.com/howcome
fy, e.g., which non-letters to treat as part of words and which to
> give
> special treatment. (As we all know, TeX hyphenates xxx-yyy as xxx-
> yyy; in addition, the hyphen prohibits xxx and yyy from being hyphenated,
> which may or may not be suitable depending on, e.g., column width.)
>
> How does Prince deal with these issues?
Prince6 does't try to go beyond Tex.
-h&kon
Håkon Wium Lie CTO °þe®ª
[EMAIL PROTECTED] http://people.opera.com/howcome
ictionaries
You can plug these into Prince as per:
http://www.princexml.com/howcome/2006/p6/p6demo2.html
I agree that browsers should read these dictionaries. However, the
dictionaries don't have to ship with browsers -- they can be web
resources just like style sheets and images are.
-
:
http://www.princexml.com/howcome/2006/p6/p6demo2.html
Currently, Prince will only hypenate paragraphs with 'text-align:
justify'. I agree that hypenation is useful in other cases as well.
-h&kon
Håkon Wium Lie CTO °þe®ª
[EMAIL PROTECTED] http://people.opera.com/howcome
] http://people.opera.com/howcome/2006/phd/#h-37
-h&kon
Håkon Wium Lie CTO °þe®ª
[EMAIL PROTECTED] http://people.opera.com/howcome
() }
>
> ...to indicate where all those endnotes should go.
The proposal suggests this:
article::after {
content: pending(endnote);
}
http://www.w3.org/TR/2006/WD-css3-gcpm-20060919/#endnotes
-h&kon
Håkon Wium Lie CTO °þe®ª
[EMAIL PROTECTED] http://people.opera.com/howcome
121&rl=1
[4] http://people.opera.com/howcome/2005/ala/sample.html
[5] http://www.alistapart.com/articles/boom
Cheers,
-h&kon
Håkon Wium Lie CTO °þe®ª
[EMAIL PROTECTED] http://people.opera.com/howcome
print
publishing in general [4][5]. All by way of HTML and CSS.
[1] http://www.princexml.com/samples/
[2] http://people.opera.com/howcome/2006/ibsen
[3] http://www.princexml.com/howcome/2006/slogans/slogans.pdf
[4] http://www.w3.org/TR/css3-gcpm
[5] http://www.w3.org/TR/css3-multicol
-h&am
ill not helping authors for some time anyway).
It's still early in the life of the canvas element, and we still have
the luxury of listening to good proposals. We can deal with the minor
problems that arise, and authors down the road will have a more
intuitive syntax. I like the proposal.
Che
eType Webfonts.
http://news.com.com/Microsofts+forgotten+monopoly/2010-1032_3-6085417.html
Cheers,
-h&kon
Håkon Wium Lie CTO °þe®ª
[EMAIL PROTECTED] http://people.opera.com/howcome
eate a style sheet language for it
(FOSI/DSSSL). Likewise with HTML. Given that CSS existed when MathML
was created, I think the developers made a mistake by not creating a
markup language that could be presented using existing CSS properties.
Cheers,
-h&kon
Håkon Wium Lie
an co-exist just like WebForms and XForms
can co-exist.
I agree with your other points, though -- nice list.
-h&kon
Håkon Wium Lie CTO °þe®ª
[EMAIL PROTECTED] http://people.opera.com/howcome
mpelling case for adding math to HTML the simple
way. Personally, I'm open to adding it to HTML5. How much would it add
to the specification?
-h&kon
Håkon Wium Lie CTO °þe®ª
[EMAIL PROTECTED] http://people.opera.com/howcome
Also sprach Ian Hickson:
> > > This triggers SGML comment parsing mode (which you don't want to be
> > > testing)
> > > in a number of browsers.
> >
> > Why? The closer we can define the behaviour to be compatible with existing
> > standards mode behaviours, the better it will be for back
52 matches
Mail list logo
