Options:
- # Session Start: Wed May 20 00:00:00 2009
- # Session Ident: #css
- # [00:09] * Joins: dbaron (dbaron@12.130.118.19)
- # [00:10] <dbaron> Do caption margins collapse with table margins?
- # [00:10] <dbaron> There's a figure caption in CSS 2.1 that says they do.
- # [00:10] <dbaron> But I can't find anything else saying so.
- # [00:11] <dbaron> Hmmm, we changed the figure but not its caption.
- # [00:27] <fantasai> we made a decision on that recently
- # [00:27] * fantasai has to run, but it should be in the errata
- # [00:56] * Quits: plinss (plinss@98.112.93.63) (Ping timeout)
- # [01:59] * Quits: dbaron (dbaron@12.130.118.19) (Quit: 8403864 bytes have been tenured, next gc will be global.)
- # [02:43] * Joins: dsinger_ (dsinger@17.244.11.113)
- # [02:45] * Quits: dsinger (dsinger@17.202.35.52) (Ping timeout)
- # [02:49] * Joins: dsinger (dsinger@17.202.35.52)
- # [02:52] * Quits: dsinger_ (dsinger@17.244.11.113) (Ping timeout)
- # [02:52] * Joins: dsinger_ (dsinger@17.244.11.113)
- # [02:53] * Joins: dsinger__ (dsinger@17.202.35.52)
- # [02:54] * Quits: dsinger (dsinger@17.202.35.52) (Ping timeout)
- # [02:55] * Quits: dsinger_ (dsinger@17.244.11.113) (Ping timeout)
- # [03:02] * Joins: dsinger (dsinger@17.244.11.113)
- # [03:02] * Joins: dsinger_ (dsinger@17.202.35.52)
- # [03:03] * Quits: dsinger__ (dsinger@17.202.35.52) (Connection reset by peer)
- # [03:05] * Quits: dsinger (dsinger@17.244.11.113) (Ping timeout)
- # [03:34] * Joins: gabriele (gabriele@87.20.182.72)
- # [03:35] <gabriele> hi there
- # [03:36] <gabriele> anybody here?
- # [03:37] <gabriele> worldwide wait?
- # [03:44] * Parts: gabriele (gabriele@87.20.182.72)
- # [04:10] * Joins: plinss (plinss@98.112.93.63)
- # [04:28] * Joins: jdaggett (jdaggett@202.221.217.78)
- # [04:33] * Quits: plinss (plinss@98.112.93.63) (Ping timeout)
- # [04:41] * Joins: plinss (plinss@98.112.93.63)
- # [04:46] * Quits: plinss (plinss@98.112.93.63) (Ping timeout)
- # [04:53] * Joins: plinss (plinss@98.112.93.63)
- # [05:49] * Quits: Lachy (Lachlan@124.171.255.145) (Quit: Leaving)
- # [11:45] * Joins: MoZ (chatzilla@82.230.92.154)
- # [13:06] * Joins: jdaggett_ (jdaggett@125.203.114.81)
- # [13:09] * Joins: dbaron (dbaron@69.140.1.234)
- # [13:15] * Quits: MoZ (chatzilla@82.230.92.154) (Ping timeout)
- # [13:30] * Joins: myakura (myakura@114.150.90.87)
- # [13:41] * Parts: annevk (opera@94.210.210.44)
- # [13:41] * Joins: annevk (opera@94.210.210.44)
- # [14:54] * Quits: annevk (opera@94.210.210.44) (Ping timeout)
- # [15:02] * Joins: annevk (opera@94.210.210.44)
- # [15:03] * Joins: anne (annevk@94.210.210.44)
- # [15:36] * Joins: MoZ (chatzilla@82.230.92.154)
- # [16:07] * Quits: MoZ (chatzilla@82.230.92.154) (Client exited)
- # [16:12] * Joins: MoZ (chatzilla@82.230.92.154)
- # [16:46] * Quits: Bert (bbos@mcclure.w3.org) (Client exited)
- # [16:47] * Joins: Bert (bbos@mcclure.w3.org)
- # [16:48] * Quits: MoZ (chatzilla@82.230.92.154) (Quit: ChatZilla 0.9.84 [Firefox 3.0.10/2009042315])
- # [17:48] * Joins: glazou (glazou@82.247.96.19)
- # [17:49] * jdaggett_ is now known as jdaggett_sleepy
- # [17:53] * Joins: Zakim (rrs-bridgg@128.30.52.30)
- # [17:53] * Joins: RRSAgent (rrs-loggee@128.30.52.30)
- # [17:53] <RRSAgent> logging to http://www.w3.org/2009/05/20-CSS-irc
- # [17:53] <glazou> Zakim, this will be Style
- # [17:53] <Zakim> ok, glazou; I see Style_CSS FP()12:00PM scheduled to start in 10 minutes
- # [17:55] <Zakim> Style_CSS FP()12:00PM has now started
- # [17:55] <Zakim> + +1.415.738.aaaa
- # [17:56] <jdaggett_sleepy> jdaggett is +1.415
- # [17:56] <jdaggett_sleepy> zakim jdaggett is +1.415.738
- # [17:58] * Joins: szilles (chatzilla@192.150.10.200)
- # [17:58] <Zakim> +glazou
- # [17:58] <jdaggett_sleepy> Zakim, +1.415.738.aaaa has jdaggett
- # [17:58] <Zakim> +jdaggett; got it
- # [18:00] * Joins: arronei (arronei@131.107.0.75)
- # [18:01] <Zakim> +plinss
- # [18:02] <Zakim> +David_Baron
- # [18:03] <Zakim> +[Microsoft]
- # [18:03] <annevk> Zakim, passcode?
- # [18:03] <Zakim> the conference code is 78953 (tel:+1.617.761.6200 tel:+33.4.89.06.34.99 tel:+44.117.370.6152), annevk
- # [18:04] <Zakim> +??P27
- # [18:04] <annevk> Zakim, ??P27 is me
- # [18:04] <Zakim> +annevk; got it
- # [18:04] * Joins: sylvaing (sylvaing@131.107.0.113)
- # [18:06] <dbaron> Zakim, who is on the phone?
- # [18:06] <Zakim> On the phone I see +1.415.738.aaaa, glazou, plinss, David_Baron, [Microsoft], annevk
- # [18:06] <Zakim> +1.415.738.aaaa has jdaggett
- # [18:06] <dbaron> Zakim, aaaa is jdaggett
- # [18:06] <Zakim> +jdaggett; got it
- # [18:06] <dbaron> Zakim, who is on the phone?
- # [18:06] <Zakim> On the phone I see jdaggett, glazou, plinss, David_Baron, [Microsoft], annevk
- # [18:06] <Zakim> jdaggett has jdaggett
- # [18:08] <sylvaing> Zakim, [Microsoft] has sylvaing, alexmog, arronei
- # [18:08] <Zakim> +sylvaing, alexmog, arronei; got it
- # [18:08] <dbaron> ScribeNick: dbaron
- # [18:08] <Zakim> +fantasai
- # [18:09] <dbaron> Meeting: CSS Working Group Teleconference
- # [18:09] <dbaron> Chair: Peter Linss
- # [18:09] <dbaron> Scribe: David Baron
- # [18:09] <dbaron> Topic: Agenda
- # [18:09] * Joins: alexmog (alexmog@131.107.0.113)
- # [18:09] <dbaron> Peter: Anything to add?
- # [18:09] <dbaron> [silence]
- # [18:09] <Zakim> +??P30
- # [18:09] <dbaron> Topic: Issue 111: bolder/lighter
- # [18:09] <Zakim> +dsinger
- # [18:09] <jdaggett_sleepy> http://lists.w3.org/Archives/Public/www-style/2009May/0145.html
- # [18:10] * Joins: howcome (howcome@213.236.208.22)
- # [18:10] <dbaron> jdaggett: I posted http://lists.w3.org/Archives/Public/www-style/2009May/0145.html as a proposal for how to get around the problems we've discussed for a long time with bolder/lighter.
- # [18:10] <Zakim> +Bert
- # [18:10] <dbaron> jdaggett: Avoids having to carry around a lot of information when bolder inherits, etc.
- # [18:11] <dbaron> jdaggett: Instead, have a table that says, given an inherited weight and bolder/lighter, what the resulting computed weight is.
- # [18:11] <dbaron> jdaggett, Essentially it mimics a font family with four weights, which lets you capture some of the cases where there's a heavier or lighter weight than normal/bold.
- # [18:11] <dbaron> s/jdaggett,/jdaggett:/
- # [18:12] <dbaron> jdaggett: Would skip weights if there are a lot of weights in the family.
- # [18:12] <dbaron> dbaron: I like it.
- # [18:12] <dbaron> Bert: I'm not comfortable with it.
- # [18:13] <dbaron> Bert: But it's attractive because it's so simple.
- # [18:13] <dbaron> Bert: But the spec has said for a long time that it should look at the available fonts. Can we change that now?
- # [18:14] <dbaron> jdaggett: An alternative would be to ignore the text contained within the element and figure the weights using the first available font family, so you'd always inherit a specific weight and not need to inherit the 'bolder'.
- # [18:14] <dbaron> jdaggett: It would also mean that the computed weight is a valid numerical weight.
- # [18:15] <dbaron> Bert: I'd say let's put it in for a few months before PR and see what other people think of it.
- # [18:15] <dbaron> Bert: Another thing I just saw: Thomas Phinney wasn't happy with the 9 weights and wants more in-between.
- # [18:16] <dbaron> jdaggett: That's an orthogonal problem. He's also concerned about limitations of GDI that have caused font vendors to put data in the font that ... . So I think some of what he's talking about are problems font vendors have had with GDI, which is something that a user agent can do things to get around, and I don't think it affects this issue so much.
- # [18:17] <dbaron> Bert: I don't want to change the number of weights allowed.
- # [18:17] <dbaron> jdaggett: I'm not sure he was saying we needed more weights, rather that we need a defined way of dealing with these things out there.
- # [18:17] <dbaron> Sylvain: Is there an implementation of your proposal?
- # [18:17] <dbaron> jdaggett: I could probably do that.
- # [18:18] <dbaron> jdaggett: So the takeaway is to leave it (?) in the spec for now, and experiment over the next few months?
- # [18:18] <dbaron> jdaggett: table proposal is already in css3-fonts editor's draft
- # [18:19] <dbaron> Peter: I'm not hearing any objection to that.
- # [18:19] <dbaron> Elika: What does this mean for 2.1?
- # [18:19] <Zakim> +SteveZ
- # [18:20] <dbaron> jdaggett: If people seem comfortable with this, I would want to change 2.1 to correspond.
- # [18:23] <dbaron> Steve: Pushing to 2.1 would probably force people who use multiple-weight fonts to use the numbers, and font guys (?) think people aren't going to use those.
- # [18:23] <dbaron> Steve: But the complexity of doing something that does the right thing (taking the current font into account) that I weakly support what you're proposing. But it means fonts with a lot of weights won't really work well.
- # [18:23] <sylvaing> alexmog says "as long as it's not normative" :)
- # [18:24] <Zakim> -dsinger
- # [18:24] <Zakim> +[Apple]
- # [18:24] <dsinger_> zakim, [apple] has dsinger
- # [18:24] <Zakim> +dsinger; got it
- # [18:25] <dbaron> Elika: If you have all of the weights, the difference between weights can be very subtle. So with this proposal 'bolder' will actually cause a noticeable difference in boldness, whereas the current spec doesn't.
- # [18:25] <dbaron> jdaggett: Agreed.
- # [18:26] <dbaron> Elika: What if you combined the table with checking first available font?
- # [18:26] <dbaron> jdaggett: There's already a way of mapping when the fonts don't have weights.
- # [18:27] <dbaron> Steve: I think what John is proposing is a better computed value.
- # [18:28] <dbaron> ?: How much is 'bolder' used?
- # [18:28] <dbaron> various: not that much?
- # [18:29] <dbaron> jdaggett: On Windows, you generally only have two weights available anyway.
- # [18:29] <dbaron> jdaggett: But with @font-face that will change.
- # [18:30] <dbaron> Peter: If somebody really needs all the different weights, and they use @font-face, they'll probably use the numeric control.
- # [18:30] <dbaron> Peter: The danger of bolder/lighter was that it's fragile. I like this proposal; it does the right thing more often than not.
- # [18:31] <dbaron> Steve: It will still have the phenomenon that with only two weights, normal->bolder->bolder->lighter gives no change for a font with only 400 and 700.
- # [18:31] <jdaggett_sleepy> http://people.mozilla.org/~jdaggett/weightdistinctions.png
- # [18:32] <dbaron> jdaggett But that's going to be true with existing implementations anyway.
- # [18:32] <dbaron> s/tt/tt:/
- # [18:32] <Bert> (I'm using bolder quite often, but knowing that for 99% of the readers it will not actually be bolder, so I don't use it when a weight change is essential for readability.)
- # [18:33] <dbaron> jdaggett: So I will post suggested edits for 2.1 on www-style and we can collect more comments based on that.
- # [18:33] <dbaron> ?: sounds good
- # [18:34] <dbaron> Elika: I have an example: in font with 400,700, 900: normal -> bolder, then in descendant element with font with 400,700, do lighter, what happens?
- # [18:34] <fantasai> s/400,700, 900/400,900/
- # [18:35] <dbaron> jdaggett: I think new way is clear to figure out what happens, but can be hard to compare to existing proposals.
- # [18:36] <Bert> <span style="font-family: normal-and-black; font-weight: bolder">foo <span style="font-family: normal-and-bold; font-weight: lighter">bar</></>
- # [18:37] <dbaron> jdaggett: I think the situations with multiple levels of nesting aren't cases that authors would easily understand.
- # [18:38] <dbaron> Steve: Bert's example shows problem with jdaggett's "alternative proposal": why you shouldn't use the font.
- # [18:38] <dbaron> Sylvain: Hard to find a solution that works in every case here.
- # [18:39] <dbaron> jdaggett: Strong case for making things simple, so you can at least figure out what will happen.
- # [18:39] <dbaron> Sylvain: [???] Hard to get what you want every time.
- # [18:39] <dbaron> Steve: Main reason I like John's proposal.
- # [18:39] <dbaron> jdaggett: I'll try to include examples with the proposal.
- # [18:40] <dbaron> Topic: Media Queries Test Suite
- # [18:40] <sylvaing> (not sure we should concern ourselves with authors changing font family in descendant *and* using relative font-weight.)
- # [18:40] <dbaron> Peter: Opera won't have the resources to lead the effort for this test suite.
- # [18:41] <dbaron> s/Peter/Peter+Daniel/
- # [18:41] <dbaron> Daniel: We have 3 implementations, mostly interoperable.
- # [18:41] <dbaron> Daniel: Most features in spec are testable.
- # [18:41] <dbaron> Daniel: All we need for PR is test suite + impl. reports.
- # [18:41] <dbaron> Daniel: I started writing a few tests; David Baron posted a large number from Mozilla.
- # [18:42] <dbaron> Daniel: I'm not sure we can use David's as-is.
- # [18:42] <dbaron> Daniel: It's one of the candidates for a quick PR.
- # [18:42] <dbaron> Elika: Someone needs to take ownership of that test suite.
- # [18:42] <dbaron> David: Why can't the tests I posted be used pretty much as-is?
- # [18:43] <dbaron> Elika: Maybe they can; somebody needs to put together an index of all tests submitted.
- # [18:43] <dbaron> Anne: We can't go directly to PR; we have to wait at least 150 days.
- # [18:43] <dbaron> Daniel: Yes, but after that, I'd want us to go as soon as possible.
- # [18:44] <fantasai> where are these tests?
- # [18:45] * fantasai can't find any posts by dbaron to public-css-testsuite wrt media queries
- # [18:45] <dbaron> Daniel: Do tests work in browsers other than Mozilla?
- # [18:45] <glazou> http://lists.w3.org/Archives/Public/www-archive/2009Apr/att-0063/test_media_queries.html
- # [18:45] <dbaron> David: Yes, the tests function, except a lot of the parsing tests depend on recent changes to spec that Opera and WebKit don't implement yet, I think.
- # [18:46] <fantasai> dbaron, can you send your message to public-css-testsuite ?
- # [18:46] <fantasai> www-archive is not the right mailing list
- # [18:46] <fantasai> ...
- # [18:46] <fantasai> David: The reason I didn't send to public-css-testsuite is because the discussion started on w3c-css-wg
- # [18:47] <fantasai> David: Didn't get a change to send to public-css-testsuite yet
- # [18:47] <fantasai> Daniel: Who wants to take ownership of this test suite?
- # [18:47] <annevk> Anne: Yes, we fail similar tests in Bert's test suite.
- # [18:48] <fantasai> fantasai: I'm happy to provide guidance to whoever takes over
- # [18:48] <fantasai> fantasai: Basically we want a directory of files that we can put on www.w3.org
- # [18:48] <fantasai> fantasai: That are coherent and have enough instructions that it is understandable how to use the test suite and what the requirements are
- # [18:49] <dbaron> Anne: I disagree that it needs to be coherent.
- # [18:50] <dbaron> Elika: They can be inconsistent in their format, that's fine, but coherent means they don't make sense.
- # [18:50] <fantasai> s/coherent/incoherent/
- # [18:51] <dbaron> Anne: I didn't quite understand what Elika meant by coherent. I think it's fine to have some automated tests and other non-automated tests, and have requirement for all of them to pass.
- # [18:51] <dbaron> Elika: I think that's fine, just need index page that explains this.
- # [18:52] <dbaron> Peter: Still leaves question of who will own this.
- # [18:52] * sylvaing is hearing <anne test-weight:lighter><elika test-weight:bolder><glazou test-weight:normal></glazou></elika></anne>
- # [18:52] * sylvaing confused
- # [18:52] <dbaron> Anne: Lachlan has some tests that require PHP on the server.
- # [18:52] * annevk gets a well-formedness error :p
- # [18:53] <dbaron> Daniel: I can take ownership, but availablity in next 2 months is uncertain.
- # [18:53] <dbaron> Elika: Can probably copy index page from namespaces.
- # [18:54] <dbaron> Topic: text-overflow and vertical overflow
- # [18:54] <dbaron> Elika: Should defer to F2F, if Anne's ok with that.
- # [18:54] <annevk> (I haven't quite discussed this with Charles by the way, but I was planning on doing something with the Media Queries Test Suite in due course. I think I said the same to glazou.)
- # [18:55] <dbaron> Anne: I'm ok with deferring to F2F, but we would like to have some kind of answer soonish.
- # [18:55] <dbaron> Peter: Ok, at F2F then.
- # [18:55] <alexmog> f2f is fine. I do have an opinion though. I think IE7 behavior is correct.
- # [18:55] <dbaron> Topic: Other CSS 2.1 issues?
- # [18:55] <dbaron> Peter: Anything that takes 5 minutes discussion?
- # [18:55] <dbaron> Elika: Issue 89
- # [18:55] <fantasai> http://wiki.csswg.org/spec/css2.1#issue-89
- # [18:56] <fantasai> http://dev.w3.org/csswg/css3-page/#allowed-pg-brk
- # [18:56] <fantasai> http://www.w3.org/TR/CSS21/page.html#allowed-page-breaks
- # [18:57] <dbaron> I'd note that it would be helpful to have the list of CSS 2.1 issues we plan to discuss on the agenda so that we can think about them beforehand.
- # [18:58] <dbaron> Bert: I think we can allow a page break there: with more than one line, we allow a page break, so why forbid it when it drops to one line.
- # [18:58] <Zakim> -glazou
- # [18:58] <dbaron> Elika: Implementations already do this with a fixed height block; some just truncate the box.
- # [18:58] * glazou lost sound...
- # [18:58] <Zakim> +glazou
- # [18:58] <dbaron> Elika: I think IE8 and Firefox will split the block over multiple pages.
- # [18:59] <sylvaing> testcases http://fantasai.inkedblade.net/style/tests/ad-hoc/pagination/allowed-breaks-000
- # [18:59] <dbaron> Elika: I think Opera truncates.
- # [18:59] <dbaron> Steve: Without the extra space you wouldn't have allowed break, so why with it?
- # [19:00] <dbaron> Elika: Makes more sense with a fixed height block, rather than an auto height block.
- # [19:00] <dbaron> Elika: This is different from padding, conceptually.
- # [19:02] <dbaron> Steve: In this case I'd shove the whole block to the next page.
- # [19:02] <Zakim> -jdaggett
- # [19:02] <dbaron> Elika: That's not the distinction here: it's a question of whether you have to pull the last line to the next page along with the bottom padding/border.
- # [19:03] * Quits: jdaggett_sleepy (jdaggett@125.203.114.81) (Quit: jdaggett_sleepy)
- # [19:03] <dbaron> Steve: I think "can't break when there's only one line box" is a good thing.
- # [19:03] <dbaron> Peter: I don't see why not breaking is good when the container is much larger than the line.
- # [19:04] <dbaron> Steve: I sort of see that as a fallback.
- # [19:04] <dbaron> Steve: OK, I can live with it, but I think it's encouraging something that shouldn't be encouraged.
- # [19:04] <dbaron> Elika: I'd rather break there than truncate ther.
- # [19:04] <dbaron> s/ther./there./
- # [19:04] <alexmog> I don't think this break as an "allowed" break. It is a forced break.
- # [19:04] <dbaron> Peter: Any objections?
- # [19:05] <dbaron> Bert: How does this work with 'widows' and 'orphans'?
- # [19:06] <dbaron> RESOLVED: Accept proposal for issue 89
- # [19:06] <dbaron> Peter: see you next week
- # [19:06] <dsinger_> thx, cheers everyone
- # [19:06] <Zakim> -annevk
- # [19:06] <Zakim> -glazou
- # [19:06] <Bert> Orphans cannot be 0, doesn't that exclude Fantasai's solution?
- # [19:06] <Zakim> -plinss
- # [19:06] <Zakim> -[Microsoft]
- # [19:06] <Zakim> -David_Baron
- # [19:06] <Zakim> -fantasai
- # [19:07] <Zakim> -SteveZ
- # [19:07] <Zakim> -[Apple]
- # [19:07] * Quits: glazou (glazou@82.247.96.19) (Quit: glazou)
- # [19:07] <Zakim> -Bert
- # [19:07] * Parts: dsinger_ (dsinger@17.202.35.52)
- # [19:07] <Zakim> -??P30
- # [19:07] <Zakim> Style_CSS FP()12:00PM has ended
- # [19:07] <Zakim> Attendees were glazou, jdaggett, plinss, David_Baron, annevk, sylvaing, alexmog, arronei, fantasai, dsinger, Bert, SteveZ
- # [19:08] * Quits: alexmog (alexmog@131.107.0.113) (Quit: alexmog)
- # [19:08] <fantasai> Bert: That's an interesting take :)
- # [19:08] * fantasai didn't think of it that way
- # [19:09] * Quits: anne (annevk@94.210.210.44) (Client exited)
- # [19:10] * Joins: anne (annevk@94.210.210.44)
- # [19:10] * Quits: anne (annevk@94.210.210.44) (Client exited)
- # [19:10] * Joins: anne (annevk@94.210.210.44)
- # [19:10] * Quits: anne (annevk@94.210.210.44) (Client exited)
- # [19:10] * Quits: howcome (howcome@213.236.208.22) (Ping timeout)
- # [19:10] * Joins: anne (annevk@94.210.210.44)
- # [19:12] * Quits: sylvaing (sylvaing@131.107.0.113) (Ping timeout)
- # [19:44] * Quits: dbaron (dbaron@69.140.1.234) (Ping timeout)
- # [19:44] * Joins: dbaron (dbaron@69.140.1.234)
- # [19:53] * Joins: sylvaing (sylvaing@131.107.0.111)
- # [20:03] * Quits: dbaron (dbaron@69.140.1.234) (Ping timeout)
- # [20:30] * Zakim excuses himself; his presence no longer seems to be needed
- # [20:30] * Parts: Zakim (rrs-bridgg@128.30.52.30)
- # [20:35] * Joins: dbaron (dbaron@69.140.1.234)
- # [20:41] * Quits: dbaron (dbaron@69.140.1.234) (Ping timeout)
- # [20:45] * Joins: dbaron (dbaron@69.140.1.234)
- # [20:50] * Quits: dbaron (dbaron@69.140.1.234) (Ping timeout)
- # [20:52] * Joins: dbaron (dbaron@69.140.1.234)
- # [21:08] * Quits: shepazu (schepers@128.30.52.30) (Ping timeout)
- # [21:13] * Joins: shepazu (schepers@128.30.52.30)
- # [21:47] * Quits: sylvaing (sylvaing@131.107.0.111) (Connection reset by peer)
- # [22:05] * Joins: sylvaing (sylvaing@131.107.0.112)
- # [22:24] * Quits: karl (karlcow@128.30.54.58) (Quit: O public road, I say back I am not afraid to leave you, yet I love you, you express me better than I can express myself.)
- # [22:24] * Joins: karl (karlcow@128.30.54.58)
- # [23:48] * Quits: annevk (opera@94.210.210.44) (Client exited)
- # [23:55] * Quits: dbaron (dbaron@69.140.1.234) (Quit: 8403864 bytes have been tenured, next gc will be global.)
- # Session Close: Thu May 21 00:00:00 2009
The end :)