[20:56]  * hyperair wonders if MacSlow is free to talk about notify-osd's newline-to-space behaviour
[20:56] <MacSlow> hyperair, you're refereing to the issue with banshee?!
[20:57] <hyperair> there were multiple issues =\
[20:57] <hyperair> which issue are you thinking about?
[20:58] <MacSlow> hyperair, apart from the newline-to-space fixing bugs... I only know about the regression with notifications coming from banshee (assuming formatting is preserved)
[20:58] <hyperair> heh?
[20:58] <hyperair> formatting preserved?
[20:58] <hyperair> i thought notify-osd's supposed to drop all formatting and keep the newlines
[20:59] <MacSlow> "The body should be 0.9 × the standard application font size, of color #eaeaea, standard weight, and should not contain any extra formatting."
[20:59] <hyperair> at least, so says the wiki page
[20:59] <MacSlow> newline is also part of formatting
[20:59] <hyperair> Body text
[20:59] <hyperair> The body should be 0.9 × the standard application font size, of color #eaeaea, standard weight, and should not contain any extra formatting.
[20:59] <hyperair> In the body text, any string of one or more consecutive whitespace characters that contains at least one newline (U+000D CARRIAGE RETURN (CR), U+000A LINE FEED (LF), or U+000D CARRIAGE RETURN (CR) immediately followed by U+000A LINE FEED (LF)), even if a mixture of those, should be treated as a single newline. Then for each line in the text, any string of one or more consecutive (non-newline) whitespace characters, even if a mixture of them, sh
[21:00] <hyperair> snippet from http://wiki.ubuntu.com/NotifyOSD
[21:00] <MacSlow> yeah, yeah... I'm getting to that... part of the need for the newline-to-space fix, is that I cannot calculate the size of the layout on a per-line-basis
[21:00] <hyperair> eh?
[21:00] <hyperair> what's wrong with the size calculation?
[21:01] <hyperair> notification-daemon does it just fine, doesn't it? just lift some code from there to figure out the size?
[21:01] <MacSlow> and since notify-osd needs to enforce a 10-line limit to avoid infintely growing bubbles...
[21:01] <hyperair> then keep the limit
[21:01] <hyperair> i only want my one newline character
[21:02] <hyperair> and as i quoted above, the wiki page specified that the newlines shouldn't be removed, but rather consecutive ones squashed into a single newline.
[21:03] <hyperair> unless you're supposed to make these changes without any consideration for what the original spec says?
[21:04] <MacSlow> hyperair, no
[21:04] <hyperair> no?
[21:05] <MacSlow> hyperair, no as in... of course I don't want to diverge from the spec
[21:05] <MacSlow> briefly forgot about the dedicated section about the newline-handling
[21:05] <hyperair> so the behaviour will be reverted then?
[21:05] <MacSlow> hyperair, if that would be the only bug to fix
[21:06] <MacSlow> when I can figure out how to get the line-limits correctly enforced
[21:06] <hyperair> okay then
[21:19] <MacSlow> hyperair, fixed
[21:19] <hyperair> thanks
[21:19] <MacSlow> hyperair, do you happen to have the bug-number to the banshee bug handy?
[21:19] <hyperair> there isn't one, regarding the newline-to-space issue.
[21:20] <hyperair> at least, not that i know of
[21:21] <hyperair> regarding the one with non-square album-art, i filed it against notify-osd
[21:22] <hyperair> MacSlow: looks like you assigned it to yourself already.. bug #443979
[21:22] <ubot4> Launchpad bug 443979 in notify-osd "Notify OSD ignores Banshee's non-square album art" [Medium,Confirmed] https://launchpad.net/bugs/443979
[21:23] <MacSlow> hyperair, that's different... I'm not sure what's causing this... non-square passed via icon_data fails while passed as normal filename does not
[21:23] <hyperair> mmhmm
[21:24] <hyperair> well other than that bug, i don't think there are any more filed regarding banshee and notifications 
[22:26] <djsiegel> DanRabbit1: ping
[22:27] <DanRabbit1> pong
[22:27] <djsiegel> DanRabbit1 mac_v: hopefully they can "indicator-system-shutdown"
[22:28] <djsiegel> DanRabbit1: think you can try the elementary shutdown icon there, and send me a screenshot?
[22:28] <DanRabbit1> where?
[22:30] <djsiegel> FUSA, when it is disconnected (no IM client running)
[22:31] <DanRabbit1> I'm on jaunty
[22:31] <DanRabbit1> will that matter?
[22:31] <djsiegel> I do not think so
[22:32] <DanRabbit1> mmkay hold on
[22:32] <djsiegel> what does your FUSA icon look like?
[22:32] <djsiegel> when disconnected?
[22:33] <DanRabbit1> I don't know, hold on :)
[22:39] <DanRabbit> djsiegel: it's kind of ugly right now
[22:39] <DanRabbit> because it's using a 16px icon, and there doesn't exist a 16px icon ;)
[22:41] <DanRabbit> djsiegel: http://www.elementary-project.com/abuse/Screenshot.png
[22:41] <djsiegel> ahhh
[22:44] <djsiegel> DanRabbit: you're killing me with this not-running-karmic business :)
[22:44] <DanRabbit> Karmic is killing me with it's not-supporting-Intel-graphics-cards business :)
[22:45] <DanRabbit> Unless you wanna buy me a swanky new computer, I'm stuck on Jaunty for now ;)
[22:51] <djsiegel> DanRabbit: so, can you try making that power symbol stand along?
[22:51] <djsiegel> alone*
[22:51] <djsiegel> without the button around it?
[22:51] <djsiegel> just the circle with line intersecting at top?
[22:51] <DanRabbit> yea, I actually mocked something like that up before
[22:52] <DanRabbit> you want it monochrome like the other panel icons?
[22:56] <djsiegel> DanRabbit: yeah
[22:56] <djsiegel> there is some unicode char for that I thinkk