[12:19] <mdke> jdub: eia
[01:06] <setuid> Why does Ubuntu's kernel only support 32-bit AES? 
[01:07] <Burgwork> setuid, I have no idea, and you are unlikely to get an answer, as it is friday afternoon and all the kernel monkey are either in the eastern us or europe
[01:07] <setuid> Fri May  5 19:07:56 EDT 2006
[01:08] <setuid> I'm trying to figure out how to encrypt this volume... encfs is kind of lame, and requires a loopback file
[01:08] <setuid> losetup/cryptsetup don't handle more than 32-bit keys
[01:08] <setuid> Both are definitely sub-optimal
[01:10] <mjg59> setuid: It's not likely to be deliberate. Can you file a wishlist bug against linux-source-2.6.15?
[01:11] <setuid> I'll see what I can do 
[01:12] <setuid> Right now, losetup needs patching to support proper encryption
[01:12] <setuid> Try this: 
[01:12] <setuid> dd if=/dev/zero of=mycryptofs bs=1k count=5000
[01:12] <setuid> losetup -e AES256 /dev/loop0 mycryptofs
[01:12] <setuid> ... use a password of at least 20 chars
[01:12] <setuid> It'll die with some bogus: ioctl: LOOP_SET_STATUS: Invalid argument
[01:12] <mjg59> setuid: I'm quite happy to believe you :)
[01:13] <mjg59> Can you file a bug against util-linux as well?
[01:13] <setuid> ;) 
[01:13] <setuid> How many do you want me to file tonight? ;) 
[01:13] <setuid> # losetup -e AES256 /dev/loop/0 mycryptofs
[01:13] <setuid> Password: 
[01:13] <setuid> ioctl: LOOP_SET_STATUS: Invalid argument, requested cipher or key length (256 bits) not supported by kernel
[01:13] <setuid> niiiice
[01:14] <mjg59> Oh, right. That error is from the kernel.
[01:14] <mjg59> What patches does losetup need?
[01:14] <setuid> http://clemens.endorphin.org/Cryptoloop_Migration_Guide
[01:14] <setuid> Second para down
[01:15] <mjg59> Ok
[01:15] <mjg59> If you file a bug against util-linux and include that, that'd be great
[01:15] <setuid> I'm testing the patch now
[01:15] <mjg59> I can't promise that it'll make dapper, but there's a chance
[01:15] <setuid> Dapper deprecated already?! 
[01:15] <setuid> What're we at now? 
[01:15] <mjg59> No, feature frozen
[01:16] <setuid> I would call this 'grave', not a feature
[01:16] <mjg59> Which? The lack of losetup support, or the kernel encryption?
[01:16] <mjg59> If you want functionality that isn't upstream, then that's a feature
[01:16] <setuid> Lack of support for aes256
[01:17] <mjg59> It may be a highly desirable feature, but, well
[01:17] <setuid> The kernel has it, but util-linux doesn't let me use it 
[01:17] <setuid> because util-linux truncates the key
[01:17] <mjg59> If it's a plain bug, then it can be fixed
[01:17] <setuid> Sure
[01:22] <setuid> mjg59: where is $PREFIX defined in $PACKAGE/debian, if I have the source for a package? 
[01:27] <setuid> Something's wrong here
[01:28] <setuid> Wha'ts the command to see what args a package was built with again? 
[02:12] <jmg> bhey all hows it going?
[02:12] <vdepizzol> will ubuntu 6.06 come with flash player?
[02:13] <crimsun> vdepizzol: no.
[02:13] <vdepizzol> crimsun: why not?
[02:14] <crimsun> vdepizzol: are you referring to Macromedia/Adobe's?
[02:14] <vdepizzol> crimsun: yes, the flash plugin for web
[02:14] <crimsun> vdepizzol: it's in multiverse: 'flashplugin-nonfree'.
[02:54] <bddebian> Howdy peoples
[03:08] <bddebian> Do we need to do a UVF / sync request on LP to bring in something NEW?
[03:13] <bddebian> sfllaw: You there or just a reconnect?
[04:16] <bddebian> Damn it's quiet tonight
[04:26] <zul> heylo
[04:27] <bddebian> Heya zul
[04:27] <zul> hey bddebian 
[06:59] <myleftfoot> hi guys... in dapper is gdm compiled with the --enable-secureremote option?
[09:18] <bluetoad> Fabbione? 
[09:19] <fabbione> hey bluetoad 
[09:19] <bluetoad> How's it going?
[09:19] <fabbione> bluetoad: pretty good i would say
[09:19] <fabbione> you?
[09:19] <bluetoad> Pretty good.  Off to the movies soon.
[09:19] <bluetoad> I've been looking through the bugs.  Don't know where I can help.
[09:20] <bluetoad> Might be 1 bug  #42354
[09:20] <Ubugtu> Malone bug 42354 in xorg "Screen configuration misses horizontal/virtical refresh rates" [Normal,Unconfirmed]  http://launchpad.net/bugs/42354
[09:20] <bluetoad> Still waiting on others
[09:23] <fabbione> i saw that one coming in yesterday.. but it's like weekend :)
[09:23] <bluetoad> I'll leave you alone.
[09:24] <sfllaw> No rest for the weary.  :)
[09:24] <bluetoad> Reckon.
[09:25] <fabbione> ehhe
[09:25] <fabbione> bluetoad: nah it's ok
[09:25] <fabbione> i am not going to kill you if you want to talk
[09:26] <bluetoad> No worries.  Just though I'd check in.
[09:26] <fabbione> ehe thanks a lot dude
[09:27] <bluetoad> Enjoy the day.  I'm off.  Let me know if there is any small things to look out for.  Knowledge is a sketchy on all this.
[09:29] <fabbione> bluetoad: have fun
[09:30] <bluetoad> You too.
[11:58] <hunger> ~.~.
[11:58] <hunger> ~.
[11:59] <hunger> Sorry for that...
[12:02] <_ion> hunger: Trying to kill the ssh session? :-)
[12:03] <_ion> hunger: And then remembered the IRC client is running on the local machine? ;-)
[12:21] <mdke> Znarl: around?
[12:34] <mwright1nigh1> Hi,  I don't know if any developers here have  HP server to test with but a DL380 G4 running latest iLO (Integrated Lights Out) won't display ubuntu as it boots
[12:34] <mwright1nigh1> you see grub, and the loading kernel thing, then you lose the console
[12:34] <mwright1nigh1> I can give a web ilo login (needs java 1.4.2+) tomorrow to a developer BUT, I will be building the server after tomorrow so won't be able to give it out after then if anyone wants to test
[12:35] <HrdwrBoB> do you have advanced iLO?
[12:36] <HrdwrBoB> not sure if it would be a licensing issue
[12:39] <mwright1nigh1> iLO advanced
[12:39] <mwright1nigh1> I work for HP
[12:39] <mwright1nigh1> Fedora and Rhel works ,except when I type linux rescue
[12:39] <mwright1nigh1> then they fail cause they don't handle the virtual scsi cdrom
[12:59] <Kaloz> morning. who's in charge of xubuntu stuff?
[01:00] <tseng> janimo, crimsun. but if you have a bug you are better of putting it in launchpad
[01:00] <tseng> irc gets lost, esp when people arent here
[01:02] <Kaloz> well, i've asked because dunno who to contact, as the wavelan plugin is in the universe
[01:02] <Kaloz> the sources is right, just the binary package is wrong
[01:02] <Kaloz> seem slike someone forgot to update it
[01:03] <Kaloz> the .deb is an older version with (now) broken dependencies
[01:03] <mdke> sounds like a bug would be helpful
[01:05] <Kaloz> i've udnerstood that, just dunno if that one will get into main or not with the move of xfce into main, so i was wondering what against should i fill the bug
[01:07] <Gloubiboulga> Kaloz, it's a known bug
[01:07] <Gloubiboulga> Kaloz, some plugins have not been ported to the new panel yet
[01:08] <Kaloz> Gloubiboulga: it's ported, just the .deb was not updated :)
[01:09] <Gloubiboulga> Kaloz, you're upstream?
[01:10] <Kaloz> Gloubiboulga: nope, but i can read the changelog :P 0.5.0 has "* New upstream release, ported to the 4.4 panel API" in the changelog, but the binary .deb is at 0.4.3 still
[01:10] <Gloubiboulga> Kaloz, ok, I'll update the package then
[01:10] <Omeg> Hey guys.
[01:11] <Kaloz> Gloubiboulga: yay :)
[01:27] <Gloubiboulga> Kaloz, I can install the package from the repos
[01:58] <Kamion> Kaloz: xfce4-wavelan-plugin | 0.5.0-0ubuntu1 | dapper/universe | source, amd64, i386, ia64, powerpc, sparc
[01:58] <Kamion> Kaloz: .debs look up-to-date to me
[01:59] <Kamion> Kaloz: but they're only timestamped yesterday, so perhaps your mirror is just a bit out of date; try archive.ubuntu.com
[02:09] <slomo_> hmm... what happened to the buildds? nothing is built since many hours it seems
[02:10] <seb128> slomo_: ah, nothing ... reply to my question about gst-plugins-good0.10 on #launchpad so, thank you ;)
[02:33] <mdke> seb128: hiya. I still get asked for my ssh key or keyring password when I try to open (e.g.) epiphany/gnome-terminal preferences, did that fix you mentioned recently land? or was that for another bug?
[02:34] <seb128> mdke: it was for the fileselector itself (ie: the open or save dialog), but the same should probably be done for the widget that lists a path
[02:34] <mdke> seb128: ah right. Do you need a bug for it?
[02:35] <seb128> mdke: btw keyring "always" option work between sessions now, so if you store it once to your keyring it should be better
[02:35] <seb128> mdke: no, thank you, I'll use the other bug for that too
[02:35] <mdke> cool.
[03:06] <slomo_> seb128: what question? i'm not in #launchpad ;)
[03:06] <seb128> slomo_: <seb128> does anybody know why gst-plugins-good0.10 0.10.3-0ubuntu1 build has not been tried?
[03:06] <seb128> slomo_: they are debugging it
[03:06] <slomo_> seb128: cool... so let's wait and i'll get some food now :)
[03:07] <seb128> enjoy your lunch ;)
[03:23] <bddebian> Heya peoples
[04:01] <mdke> seb128: if you want, you can change the url for "Online Support" from help.ubuntu.com to help.ubuntu.com/6.06 
[04:01] <seb128> mdke: ah, thank you
[04:15] <sits> why would gdm start two Xs?
[04:16] <HrdwrBoB> if it was told to
[04:22] <bddebian> If I have -I/usr/include/foo   and the package does #include "foo.h"  Does that work?  Or does "foo.h" only look in the current dir?
[04:43] <klepas> anyone seen Daniel Holbach of late?
[04:47] <zul_> nope...
[04:47] <sits> HrdwrBoB: would that only happen in /etc/gdm/gdm.conf
[04:48] <mdke> klepas: he doesn't work at weekends. But if you email him, he'll see it
[04:48] <klepas> cheers
[04:48] <klepas> shall drop him a mail :)
[04:49] <HiddenWolf> he doesn't work weekends? Since when? :P
[04:49] <mdke> HiddenWolf: I've never known him to use irc at weekends, anyway
[04:49] <mdke> maybe occasionally.
[04:53] <bddebian> Folks.  What is the proper procedure for bringing in something new from Debian that cannot be synced? (swt-gtk in this case) ?
[04:53] <bddebian> It's a depends for swingwt
[05:00] <seb128> klepas: dholbach is at linuxtag today
[05:03] <klepas> ah, cool
[05:03] <klepas> seb128: if you're there, say hi ;)
[05:04] <seb128> nop, I'm not :)
[05:11] <HiddenWolf> seb128: man, how many hours do you make?
[05:11] <seb128> ?
[05:11] <bddebian> Thx HiddenWolf :-)
[05:12] <HiddenWolf> seb128: you're _always_ here. :)
[05:12] <zul_> i think he means you never sleep seb128
[05:12] <seb128> HiddenWolf: I try to not IRC on saturday usually, I just started it to ask to the buildd admin why gst-plugins-good0.10 was not building :p
[05:13] <HiddenWolf> seb128: do you ever leave the work behind? 
[05:13] <seb128> HiddenWolf: when I'm uptodate with my work ;)
[05:13] <seb128> why is not often with the bug flood we get :/
[05:13] <bddebian> Amen to that
[05:13] <HiddenWolf> uhuh, massive amount of bugs. :/
[05:26] <ivoks> ho ho ho
[05:26] <ivoks> ups... sorry :)
[05:35] <Evaso2> hi guys somebody knows the status of freepascal in debian?
[05:43] <slomo_> seb128: and -good is still not built *sigh* do they make some progress? *builds it himself now*
[05:43] <seb128> slomo_: no idea of what they are doing
[05:43] <seb128> are you in a hurry?
[05:44] <slomo_> well... i won't have time to play with gst or anything else later today, tomorrow, on monday and on tuesday because of too much other work ;)
[05:47] <HiddenWolf> seb128: I was wondering, in the flood of bugs/packages that you get, how do you decide what to do / fix ?
[05:47] <bddebian> Everything ;-)
[05:47] <seb128> HiddenWolf: I just decide
[05:48] <seb128> I mean, what sort of question is that
[05:49] <HiddenWolf> seb128: like, how do you prioritise?
[05:49] <seb128> good sense?
[05:49] <seb128> if that's "nautilus just crash for everybody" we have to fix it no?
[05:49] <seb128> and if that's "gconf-editor icon is blurry on a 48 pixel panel" that's not a priority
[05:50] <mdke> haha, nice example
[05:50] <seb128> there is no magical way ...
[06:01] <bddebian> OK, I'm getting really confused with this libswt crap.  Many of the binarys apparently come from eclipse now but what replaces libswt-gtk-dev?  Just eclipse?
[06:06] <bddebian> eclipse-sdk?
[06:07] <jpatrick> improves confidence
[06:07] <slomo_> bddebian: ask doko 
[06:26] <sebest> seb128: hello
[06:26] <zyga> hey everyone
[06:29] <kagou> hi
[07:06] <mdke> who knows lots about asian fonts on Ubuntu?
[07:09] <HiddenWolf> mdke: check the scim maintainer field?
[07:09] <mdke> thanks
[07:10] <crimsun> mdke: ping freeflying-ibook, for instance
[07:11] <freeflying-ibook> mdke: 
[07:11] <mdke> hiya
[07:11] <freeflying-ibook> mdke: I know a few about Chinese fonts :)
[07:12] <mdke> freeflying-ibook: does the "serif" font on Ubuntu contain all necessary asian fonts?
[07:12] <mdke> (i know nothing about fonts at all)
[07:12] <freeflying-ibook> mdke: almost
[07:13] <mdke> so I've been trying to build some pdfs using the "serif" font, but all asian characters come out as #
[07:14] <mdke> I've described the problem here http://news.gmane.org/gmane.text.xml.fop.user, and had one reply, which suggested that serif might not provide asian characters. But I have to say, viewing asian characters in a serif font on my system looks absolutely fine.
[07:14] <freeflying-ibook> mdke: do you have language-selector in your /etc/fonts/
[07:14] <mdke> language-selector.conf
[07:16] <freeflying-ibook> this file configure the CJK fonts , alias CJK to serif
[07:16] <mdke> freeflying-ibook: the file is basically empty.
[07:17] <freeflying-ibook> mdke: it's a symlink , it will be linked when you use CJK locales
[07:18] <freeflying-ibook> mdke: maybe I can have a try with your pdf files
[07:19] <mdke> freeflying-ibook: the problem is not in viewing the pdf files, it is in creating them. Have a look at my post at the above url.
[07:23] <freeflying-ibook> mdke: give us a while
[07:24] <mdke> freeflying-ibook: ok, I'm hoping for some more replies on that mailing list anyway.
[07:35] <freeflying-ibook> mdke: fop-0.20-5, which u r using now can not support CJK fonts 
[08:46] <mgalvin> Mithrandir: just a heads up, i am creating a flight 7 page (just now getting time to do it :-/)
[08:46] <mgalvin> better late then never i guess :)
[08:55] <nix4me> is there anyone that can point me to a definative answer on why cups in dapper is not accepting connections from windows machines?  I know this is a devel channel but im going crazy trying to get this to work
[08:56] <infinity> nix4me: bug #39484
[08:56] <Ubugtu> Malone bug 39484 in samba "cups smb printing backend no longer works" [Major,In progress]  http://launchpad.net/bugs/39484
[08:57] <infinity> nix4me: A user has posted some temporary wotkaround packages there while I work on fixing the actual bug properly.
[08:57] <infinity> nix4me: His packages should solve your problem for now.
[08:58] <nix4me> ok, i will have a look.  thank you
[08:58] <nix4me> ive beat google and the forums to death
[08:58] <infinity> nix4me: If you have a bug, it seems sane to search for it in our bug trackers. :)
[08:59] <nix4me> yes i agree, at first i though it was my config.  then i started realizing it might be a bug
[08:59] <infinity> (google indexes Malone eventually, but never fast enough to be of any use for bugs that aren't months old)
[08:59] <nix4me> that bug is the reverse of what i have
[09:00] <nix4me> i cant print from windows to ubuntu
[09:00] <infinity> Oh.... Could you ever?
[09:01] <infinity> (And I suspect, then, that you're using IPP, not SMB...)
[09:02] <infinity> And I also suspect that this is a support question, then, not an issue dealing with a bug at all.
[09:02] <nix4me> hmmm
[09:02] <infinity> If it is via SMB, though, and not IPP, try those packages.  It can't hurt.
[09:02] <nix4me> ipp is what im using
[09:03] <infinity> Then A) I have no clue, and B) Please take this to #ubuntu.
[09:03] <nix4me> ive tried that, help was useless
[09:03] <nix4me> thanks anyway
[09:03] <nix4me> ill keep banging away
[09:03] <infinity> Well, is this a regression for you?
[09:04] <infinity> ie: Did it once work, and now doesn't?
[09:04] <nix4me> it worked in breezy
[09:04] <nix4me> there are howtos and all
[09:05] <infinity> You may want to read this:
[09:05] <infinity> https://lists.ubuntu.com/archives/ubuntu-devel/2006-April/017211.html
[09:05] <infinity> And perhaps give feedback directly to Martin.
[09:06] <nix4me> ok
[09:30] <Mithrandir> mgalvin: thanks
[09:31] <mgalvin> np
[09:31] <tseng> Mithrandir: is there anyway of knowing the kernel version from flight5?
[09:31] <Mithrandir> tseng: short of downloading and looking?
[09:32] <desrt> -18 ish?
[09:32] <desrt> tseng; figure out the release date of flight5 and look at the linux-source changelog
[09:32] <tseng> good idea
[09:55] <mgalvin> Mithrandir: are there any known bugs and caveats worth noting on the flight 7 tour?
[09:56] <Mithrandir> mgalvin: there are a couple listed in the announcement.  Apart from that, espresso isn't too happy about installing to drives which currently have LVM on, but nothing more that I know of.
[09:56] <mgalvin> Mithrandir: ok thanks
[09:57] <mgalvin> Mithrandir: was the announcment made yet? i didn't see it
[09:58] <Mithrandir> mgalvin: it might not have made it to u-a, but I know I sent it.
[10:22] <Fjodor> Can it be considered a bug that I should notify you guys of, that Xlib doesn't like my locale (en_DK.UTF-8)? locale -a reports locales ending in .utf8, and en_DK is there
[10:29] <sits> ok I'm stuck trying to turn on CUPS debug output
[10:30] <sits> can anyone tell me what to tweak so the library outputs more detail?
[10:30] <Coyctecm> hmmm gvim doesn't appear in gnome menu
[10:33] <sits> Coyctecm: which version of gvim
[10:33] <sits> and which version of Ubuntu
[10:34] <sits> (gtk-vim is in Accessories for me)
[10:34] <Coyctecm> sits: dapper and 6.4.6
[10:34] <Coyctecm> gtk-vim
[10:34] <sits> er
[10:34] <sits> sorry that should have been
[10:35] <sits> gnome-vim
[10:35] <sits> or vim-gnome even
[10:35] <Coyctecm> what's the difference between gtk-vim ang gnome-vim, i haven't noticed anything..
[10:36] <sits> try checking the description
[10:51] <omeg> Absolutely gigantic message regarding usplash sent to mailing list :)
[11:09] <omeg> Ah, it just managed to reach the latest digest.
[11:11] <Coyctecm> hmm weird
[11:12] <Coyctecm> fglrx says my card has only 64mb memory
[11:12] <Coyctecm> radeon x600 pci express
[11:13] <Coyctecm> this card have 256mb memory
[11:13] <Coyctecm> dri works fine thought
[11:13] <Coyctecm> weird
[11:17] <infinity> omeg: The reason the default usplash image appears "squished" on 4x3 aspect ratio screens is because it's designed for 640x400, not 640x480, since 640x400 is the default we give people.
[11:21] <infinity> omeg: And, while I don't want to be a jerk about it, the odds of us changing anything this much this late in the game are slim.  I do want to do a "text free usplash" for edgy, though.  I agree that it's the friendlier way to go.
[11:25] <omeg> infinity: wait, how does that work? Why squish the logo vertically when using a more wide resolution? Wouldn't that mean that you'd need a more tall version of the logo?
[11:26] <omeg> And it's too bad if something cool like that can't be changed for Dapper anymore. But I think that it would be kind of neat to see that last mock-up I linked to in a future release of Ubuntu beyond Dapper.
[11:26] <fabbione> omeg: dude learn to format your emails at 80 chars..
[11:26] <omeg> fabbione: I expect that people's e-mail readers trim e-mails at 80 characters when viewing it in text-only mode.
[11:26] <fabbione> omeg: wrong, you don't expect.. you write them properly. that emails is unreadable..
[11:27] <infinity> omeg: No, think of the math.. If the resolution is 10x8, but your screen is 10x10, then the image needs ot be "squished", since it will get "stretched" when displayed.
[11:28] <omeg> infinity: would it be possible to remove the text from usplash and then just add a "System is starting up..." message above the progress bar (and also position the elements on the screen differently like seen in that other mockup I sent?)
[11:28] <infinity> fabbione: Content-Type: format=flowed is pretty common these days.
[11:28] <infinity> fabbione: If mutt still isn't handling it, perhaps it should be taught to.
[11:28] <fabbione> infinity: than fix bugs in your t-bird pkgs dude :P
[11:28] <infinity> fabbione: I'm reading his mail in Tbird, works fine...
[11:28] <fabbione> because that's what i am using..
[11:28] <fabbione> not here
[11:29] <fabbione> it looks like all without rewrapping..
[11:29] <fabbione> veeeery llooooong liiineeeesssssss
[11:29] <omeg> Above suggestion assumes the new font, same one that's used on the CD splash screen, by the way, since that was supposed to be the change in the first place.
[11:30] <infinity> fabbione: Bizarre.  Screenshot?
[11:30] <fabbione> infinity: sure.. in a sec..
[11:30] <infinity> omeg: Yeah, I'll see if the font change is possible.  usplash/bogl is picky about what sorts of fonts it likes.
[11:31] <omeg> It's too bad that it's not a monospace font, which was reported earlier to be easier to implement.
[11:31] <infinity> omeg: The "remove all the text" change is simple enough to do, but simple isn't the point, the point is that we're way too late for drastic interface changes.
[11:31] <omeg> It's still a pretty easy font, though. Just letters with two pixels space between them.
[11:31] <infinity> omeg: To be fair, the current font isn't monospace either, I just WISH it was.
[11:31] <omeg> Yeah, that's right.
[11:31] <omeg> Still, what about just removing the font and not adding a "System is starting up..." message?
[11:31] <infinity> omeg: monospace tends to be much more readable and easy to line up and parse for "repetitive text" of the sort that boot messages are.
[11:32] <fabbione> infinity: on people..
[11:32] <omeg> To be honest, my first interest is just getting that awful font out of the screen I see daily. :P The fact that many people don't want or need to see the startup logging is a second issue to me.
[11:32] <omeg> infinity: I agree about the monospace issue.
[11:32] <omeg> I have made a monospace font which I offered earlier, but people thought it was a little too small.
[11:34] <infinity> omeg: My biggest issue isn't necessarily with vertical font height, but with "spindly" versus "partial bold".
[11:34] <infinity> The latter would be prefereable to me, since the screen as it stands has very rich colours, and a spindly font looks out of place.
[11:34] <infinity> OTOH, fixing the screen to be less saturated would fix that problem too.
[11:34] <infinity> (We were supposed to have new artwork for usplash for dapper, but that didn't seem to pan out..)
[11:36] <omeg> http://omega.avalanchestudios.net/personal/dropbox/usplash/zeta.png <-- here's that font I was talking about.
[11:36] <omeg> I'll make a bold version if you're interested.
[11:36] <Amaranth> wow that's tiny
[11:36] <omeg> It was originally designed for a home-made RPG that I was working on. It was to be in 320x240. So yeah, it's a tad tiny. :)
[11:37] <omeg> I'm going to try and make it one pixel higher and bold...
[11:38] <infinity> Bolding it will probably make the whole thing about 2px wider (if you want it to still be readable), so another 2 or 3 px higher should round it out nicely.
[11:38] <infinity> But I'm not font design expert, or I would have made my own ages ago.
[11:38] <fabbione> infinity: you are a GENIUS!
[11:38] <fabbione> thanks
[11:40] <omeg> infinity: yeah, just about that. I'll experiment around a little.
[11:40] <omeg> Capitals are done...
[11:43] <infinity> omeg: The other unfortunate thing is that bogl only tends to like fonts of the BDF variety (which is why I didn't just switch to one of the many TTF fonts out there that could have worked fine)
[11:45] <omeg> http://omega.avalanchestudios.net/personal/dropbox/usplash/zeta_8x5.png <-- 8x5 version of Zeta. Now making a bold version.
[11:45] <omeg> BDF?
[11:46] <infinity> BDF is an X font format.
[11:46] <omeg> I don't really know how to make font files. I only created this font in Windows FON format because there was a simple editor that I could use.
[11:46] <omeg> I don't know how to make a TTF, let alone a BDF. Maybe the FON file can be converted somehow?
[11:47] <infinity> FON is Adobe Type1, right?
[11:47] <infinity> I might be able to work something out.
[11:49] <omeg> I'm not sure. As far as I know, it's a very old font file type that's been around in early Windows versions.
[11:49] <infinity> omeg: xmbdfed is a (ugly, but functional) BDF bitmap editor.
[11:50] <infinity> omeg: Since your font is pure unhinted, unaliased bitmaps, it might be fairly simple to slap it in there...
[11:50] <infinity> Maybe.
[11:51] <omeg> I'll try it. Can't be worse than Pushy, which I think was the name of the font editor I used for Windows.
[11:51] <omeg> No, Softy was the name.
[11:52] <omeg> I just opened it while having the picture in the background and copied it manually, which takes some time, but seems like the only real way to do it. :P
[11:53] <omeg> The M is so difficult...
[11:57] <omeg> By the way, isn't there a different way of showing the logo in usplash? It's kind of too bad that you're distorting a logo like that. I like the way it looks on black.
[11:57] <infinity> -EPARSE
[11:58] <infinity> I don't like the current artwork, but if by "distorting", you mean the height change between aspect ratios, the only fix for that is including two sets of artwork, one for 640x400, and one for 4x3 screens.
[11:59] <omeg> Aren't most screens still 4:3?
[12:01] <infinity> omeg: Pretty much all (but widescreen) screens are 4:3, but not all resolutions are 4:3.
[12:01] <infinity> omeg: So, 640x400 on a 4:3 screen, means the original art has to be "squished", so it "stretches" again and looks right on a 4:3 screen.
[12:02] <infinity> omeg: Think of your BIOS logo (which is at 640x400 on a 4:3 screen)... It's the same as usplash.