[02:58]  * micahg is almost done testing Seamonkey :-/
[03:01] <LLStarks> people still use that?
[03:02] <micahg> yes
[03:02] <LLStarks> why?
[03:02] <micahg> all in one?  they like the compozer?
[03:02]  * micahg wants to use Seamonkey 2.1 once it's released
[03:02] <LLStarks> it's like using windows nt on a brand new laptop
[03:03] <micahg> hmm, it's the same engine as FF3.5 and TB3.0, not that old
[03:04] <LLStarks> but it still feels like it
[03:04] <LLStarks> interface too
[03:04] <LLStarks> it's a relic of the netscape days that's been  prettied up like a corpse in a funeral home
[03:05] <micahg> LLStarks: I get complaints when it's not updated, people must like it
[03:18] <LLStarks> i remember when people had to decide between mozilla and the pre-1.0 (but no firebird/phoenix) firefox.
[03:18] <LLStarks> it was a very easy decision
[06:17] <micahg> jdstrand: seamonkey seems fine on Karmic and Lucid, I'd like to discuss with you at some point what didn't quite work, but what didn't work wasn't a regression
[10:04] <fta2> dpm, Hi, did you read my post about my new dashboard?
[10:06] <dpm> hi fta2, not yet, I've been offline most of the holidays and I'm just catching up. Let me do this now...
[10:06] <dpm> and happy new year! ;)
[10:06] <fta2> dpm, happy new year to you too
[10:07] <fta2> dpm, ok, no rush. it's on planet ubuntu, you'll get to it eventually
[10:08] <dpm> fta2, ah, cool, so I see you started your new blog
[10:08] <fta2> dpm, yep
[13:21] <jdstrand> micahg: ack
[16:26] <fta> dpm, did you catch up?
[16:28]  * micahg just realized he now has a Lucid VM to test the backport of lightning :)
[16:30] <nardev> is there any way to make custom font appear right in firefox as it is in chrome http://www.data.ba/stipendije.png
[16:31] <micahg> nardev: have you tried it in 4.0?
[16:32] <nardev> no, but this is production site
[16:32] <nardev> shoud work with 3.6
[16:36] <dpm> hey fta, yeah, I did. I think the dashboard will be very useful for tracking down the translation errors that need to be fixed, but I do have one concern with people getting confused with two places showing statistics, and the discoverability of that page. Apart from that, it looks good to me - I saw on the blog post comments that someone had already found it useful to detect things to fix
[16:37] <fta> dpm, well, i don't think the new way lp exposes translation status makes sense, at least for chromium
[16:37] <fta> dpm, i don't really understand what they are trying to achieve, it was clear before, now, it seems bogus to me, everything green
[16:38] <fta> dpm, i had to do that to at least know what i should land upstream
[16:39] <fta> dpm, if you disagree, feel free to add a comment
[16:39] <dpm> fta, as I said before holidays, I don't debate the need you had for the statistics were shown before the change. It did make sense for Chromium. But for most of the projects in LP, those stats did not make much sense and did not represent the reality in many cases
[16:40] <dpm> sorry, I meant "for the way the statistics were shown before the change"
[16:40] <fta> but it's not opt-in/opt-out, it has been imposed on everyone
[16:41] <fta> so for me it was a loss
[16:44] <dpm> fta, that's true, but as Danilo said on the thread, if anyone has got any concerns, the best way to go forward is to raise them on that thread, or directly with the Launchpad Translations developers on #launchpad. Note that I'm not trying to give excuses here, as I'm not involved with LP development myself, I'm just trying to help, even if it's just directing the concerns to the right people
[16:57] <fta> ok ok.