[02:02] <ArneGoetje> kenvandine: FYI, language-selector always sets .utf8 as encoding for any locale as it should be. Even if the locale information leaves away the .utf8, because there is only one locale for that language-country combination, it doesn't mean that that it wouldn't be possible to add another encoding in future. And if that happens, the encoding must be specified. Therefor to be sure, always set the encoding.
[02:14] <ArneGoetje> jbache: The problem you describe is, because gnome store its font settings in it's own registry, while KDE uses fontconfig. Ideally, Gnome should just switch to use fontconfig to store the rendering settings. Then the discrepancy would be gone. What Riddell mentions with qtcurve is probably the same thing. The application stores it's rendering settings somewhere else instead of just using fontconfig like KDE does.
[03:11] <kenvandine> hey ArneGoetje
[03:11] <kenvandine> thx
[03:12] <kenvandine> so yeah, my install has en_US.UTF-8 in /etc/default/locale
[03:12] <kenvandine> but vish's has en_IN
[03:12] <kenvandine> which breaks locale.setlocale in python
[03:12] <kenvandine> at least in gwibber
[03:13] <kenvandine> there is a place where gwibber sets the locale to C before parsing a time string then tries to restore the old locale
[03:13] <ArneGoetje> kenvandine: correct. A lot of software expects the encoding to be specified. Therefor the installer really should append .utf8 to any locale which doesn't have it.
[03:13] <kenvandine> ok, so that is a bug in the installer
[03:13] <kenvandine> however, gwibber didn't really need to do that
[03:14] <ArneGoetje> kenvandine: seems so, since gdm and language-selector behave correctly.
[03:14] <kenvandine> setting the locale to C then setting it to '' does the right thing
[03:14] <kenvandine> locale.setlocale(locale.LC_TIME, '')
[03:14] <kenvandine> sets it back to whatever is in the env
[03:14] <kenvandine> at least afaict
[03:14] <ArneGoetje> that's strange... maybe also a bug in gwibber then?
[03:15] <kenvandine> yeah
[03:15] <kenvandine> gwibber just was doing something it didn't need to do
[03:15] <kenvandine> so i removed that, and all is good again
[03:15] <ArneGoetje> okay
[03:15] <kenvandine> but it worries me that it is effecting lots of users
[03:15] <kenvandine> since apparently this was happening in lucid too
[03:15] <kenvandine> so i guess i need to SRU that
[03:16] <ArneGoetje> yep
[03:16] <kenvandine> what i was really trying to figure out was if the installer really needs to be fixed too
[03:16] <kenvandine> ArneGoetje, could you please comment on bug 653259 ?
[03:16] <ubot2> Launchpad bug 653259 in ubiquity (Ubuntu) "Choosing India as location sets locale as en_IN and not en_IN.utf8 (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/653259
[03:17] <ArneGoetje> kenvandine: yep
[03:17] <kenvandine> thx
[03:20] <ArneGoetje> kenvandine: done
[03:21] <kenvandine> thx ArneGoetje
[03:24] <ArneGoetje> kenvandine: btw, who i running the langpack generation right now?
[03:24] <kenvandine> ArneGoetje, i don't know... maybe dpm?
[03:24] <ArneGoetje> okay... will send him a mesage
[03:25] <kenvandine> if he isn't doing it, he surely knows who is
[15:56] <devildante> is the ubuntu font default as of now or simply included in the CD?
[15:57] <nigelb> Needs FFE, I mot sure what happeneed of that.
[15:59] <devildante> hmm...
[16:46] <kklimonda> it is default
[16:46] <kklimonda> it got FFe
[16:47] <kklimonda> or rather - it's installed by the default and the idea has been to enable it for interface but I'm not sure if it's done yet.
[16:47] <kklimonda> it should be
[20:47] <sense> Are the Jockey maintainers aware that when you disable the proprietary Nvidia drivers, Jockey wrongly sets the driver to 'nv' in /etc/X11/xorg.conf? The driver 'nv' isn't available anymore and Jockey should change the driver to 'nouveau' or remove the xorg.conf file altogether.
[21:49] <Riddell> sense: best to report a bug
[21:50] <sense> Riddell: Just did that after I didn't find a bug reporting the issue.
[21:50] <Riddell> groovy
[21:50] <sense> I was just curious if it was already known here.
[21:50] <sense> but it wasn't!