Håkon Wium Lie CTO °þe®ª
howc...@opera.com http://people.opera.com/howcome
. 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 be deprecated without missing
much.
-hkon
Håkon Wium Lie CTO
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,
-hkon
Håkon Wium Lie CTO °þe®ª
howc...@opera.com http://people.opera.com/howcome
Håkon Wium Lie CTO °þe®ª
howc...@opera.com http://people.opera.com/howcome
the examples :)
The example in #11 seems fairly clear. Do you see any
incompatibilities between the example text and the general clauses?
Cheers,
-hkon
Håkon Wium Lie CTO °þe®ª
howc...@opera.com http://people.opera.com/howcome
that you
cannot redistribute the code unless you do exactly that.
What am I missing?
-hkon
Håkon Wium Lie CTO °þe®ª
howc...@opera.com http://people.opera.com/howcome
.
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, though.
Cheers,
-hkon
Håkon Wium Lie CTO °þe®ª
howc...@opera.com http://people.opera.com
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're saying that situation 2 applies in your case?
-hkon
Håkon Wium Lie
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,
-hkon
Håkon Wium Lie CTO °þe®ª
howc...@opera.com http://people.opera.com/howcome
Håkon Wium Lie CTO °þe®ª
howc...@opera.com http://people.opera.com/howcome
.
Cheers,
-hkon
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
, this works:
form action=http://www.w3.org; style=display:inlinebutton
type=submitW3C/buttonform
But, the markup isn't pretty. Also, I'd like for links to use the a
element.
-hkon
Håkon Wium Lie CTO °þe®ª
[EMAIL PROTECTED] http
and put the wording back in.
That will restore faith in HTML5 for many.
-hkon
Håkon Wium Lie CTO °þe®ª
[EMAIL PROTECTED] http://people.opera.com/howcome
Wium Lie CTO °þe®ª
[EMAIL PROTECTED] http://people.opera.com/howcome
I suggest we add this line to the style of our specifications so that
long lines break when necessary:
pre { white-space: pre-wrap }
To see and example of where it makes a differnece, search for The
drag-and-drop processing model in the HTML 5 draft.
Cheers,
-hkon
Håkon Wium
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
Vorbis support, so half of what is needed is already
a
proprietary media platform.
-hkon
Håkon Wium Lie CTO °þe®ª
[EMAIL PROTECTED] http://people.opera.com/howcome
Also sprach Laurens Holst:
object is *very badly* implemented. It has been a decade since object
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
-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/photos/mimizone/406561638/
-hkon
Håkon Wium Lie CTO °þe®ª
been specified? On the
right-click menu or somewhere where it doesn't take up space?
-hkon
Håkon Wium Lie CTO °þe®ª
[EMAIL PROTECTED] http://people.opera.com/howcome
using it for real.
-hkon
Håkon Wium Lie CTO °þe®ª
[EMAIL PROTECTED] http://people.opera.com/howcome
is the alternative, we might as well continue using Flash and
object. But it's not a world I want to live in.
-hkon
Håkon Wium Lie CTO °þe®ª
[EMAIL PROTECTED] http://people.opera.com/howcome
be usable in many types of
enviroments.
-hkon
Håkon Wium Lie CTO °þe®ª
[EMAIL PROTECTED] http://people.opera.com/howcome
(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.
-hkon
Håkon Wium Lie CTO °þe®ª
[EMAIL PROTECTED] http://people.opera.com/howcome
, 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.
-hkon
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
codecs through
object.
-hkon
Håkon Wium Lie CTO °þe®ª
[EMAIL PROTECTED] http://people.opera.com/howcome
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 video, than
(b) they support video with proprietary codecs only.
Interoperability has more value than conformace.
-hkon
Håkon Wium Lie
?
-hkon
Håkon Wium Lie CTO °þe®ª
[EMAIL PROTECTED] http://people.opera.com/howcome
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.
-hkon
Håkon Wium Lie CTO °þe®ª
[EMAIL PROTECTED] http://people.opera.com/howcome
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.
-hkon
Håkon Wium Lie CTO °þe®ª
[EMAIL PROTECTED] http
video formats are impossible to
support on all devices (mostly due to legal issue), I think we should
consider your proposal.
-hkon
Håkon Wium Lie CTO °þe®ª
[EMAIL PROTECTED] http://people.opera.com/howcome
through CSS as well:
Dont's wait for span style=hypenation-dictionary:
rec-ord.dicrecord/span
companies, span style=hypenation-dictionary: re-cord.dicrecord/span
yourself.
-hkon
Håkon Wium Lie CTO °þe®ª
[EMAIL PROTECTED] http
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.
-hkon
Håkon Wium Lie
will only hypenate paragraphs with 'text-align:
justify'. I agree that hypenation is useful in other cases as well.
-hkon
Håkon Wium Lie CTO °þe®ª
[EMAIL PROTECTED] http://people.opera.com/howcome
/howcome/2006/phd/#h-37
-hkon
Håkon Wium Lie CTO °þe®ª
[EMAIL PROTECTED] http://people.opera.com/howcome
the efforts [5].
[1] http://www.w3.org/TR/2006/WD-css3-gcpm-20060919/#footnotes
[3] http://www.awprofessional.com/bookstore/product.asp?isbn=0321193121rl=1
[4] http://people.opera.com/howcome/2005/ala/sample.html
[5] http://www.alistapart.com/articles/boom
Cheers,
-hkon
Håkon Wium Lie
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
-hkon
Håkon Wium Lie
[EMAIL PROTECTED
Håkon Wium Lie CTO °þe®ª
[EMAIL PROTECTED] http://people.opera.com/howcome
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.
Cheers,
-hkon
Håkon Wium Lie
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,
-hkon
Håkon Wium Lie CTO °þe®ª
[EMAIL PROTECTED] http
to HTML the simple
way. Personally, I'm open to adding it to HTML5. How much would it add
to the specification?
-hkon
Håkon Wium Lie CTO °þe®ª
[EMAIL PROTECTED] http://people.opera.com/howcome
agree with your other points, though -- nice list.
-hkon
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 backwards
into rich HTML forms. There are
some nice opportunities in this space.
-hkon
Håkon Wium Lie CTO °þe®ª
[EMAIL PROTECTED] http://people.opera.com/howcome
-- this is good news for both.
Overall it seems like a good thing though.
Indeed.
-hkon
Håkon Wium Lie CTO °þe®ª
[EMAIL PROTECTED] http://people.opera.com/howcome
the same organization. There has been some
friction along the way, but the friction has generally been
productive.
[1] http://www.w3.org/Submission/1997/13/
[2] http://www.w3.org/Submission/1997/13/Comment.html
[3] http://www.w3.org/TR/REC-CSS1-961217
-hkon
Håkon Wium Lie
49 matches
Mail list logo
