[03:09] <humphreybc> hey daker, you around?
[03:10] <daker> yep
[03:10] <humphreybc> how's the quickshot going? And have you got around to fixing the planet?
[03:10] <humphreybc> quickshot site*
[03:12] <daker> yes for this week
[03:12] <humphreybc> wicked
[03:12] <humphreybc> almost finished the UMP site, just waiting to sort out some pictograms and I need to fix photoshop.
[03:12] <daker> https://wiki.ubuntu.com/UbuntuDeveloperWeek#The timetable
[03:13] <humphreybc> yes, developer week is on
[03:14] <daker> there is no django session ?
[03:14] <humphreybc> no idea
[03:22] <daker> youpi there is a session on Friday
[03:33]  * daker doesn't know if he is ready to apply for a membership
=== Zeike is now known as brandonj
[09:39] <jenkins> hey
[09:39] <dpm> hey :)
[09:39] <jenkins> have you looked at the draft?
[09:40] <dpm> jenkins, sorry for not having responded earlier, I've been away for a week and I've just come back today. I had a quick look at it and it looked great to me. Let me have another look now, I've also got some questions to you
[09:40] <jenkins> no worries,
[09:40] <jenkins> lp:~ubuntu-manual/ubuntu-translations-quickstart/booklet  is the branch with it in
[09:41] <vish> dpm: hi , which is the channel for ubuntu translations?
[09:41] <dpm> vish, #ubuntu-translators
[09:41] <vish> dpm: cool , thanks
[09:41] <dpm> np :)
[09:45] <humphreybc> oh look!
[09:45] <humphreybc> it's David Planella!
[10:05] <dpm> hey humphreybc :)
[10:06] <humphreybc> hello!
[10:06] <humphreybc> haven't talked since UDS
[10:06] <nisshh> humphreybc: hey
[10:06] <dpm> yeah, time flies :)
[10:07] <nisshh> my sis just got a lovebird and its sitting on my shoulder
[10:07] <humphreybc> nisshh: a lovebird??
[10:08] <nisshh> yea
[10:08] <nisshh> like a budgy
[10:08] <nisshh> a real bird
[10:08] <humphreybc> good times
[10:08] <nisshh> its good because its really quiet
[10:08] <nisshh> doesnt swuak at all
[10:09] <nisshh> skwark
[10:09] <nisshh> oh whatever
[10:09] <humphreybc> lol
[10:09] <humphreybc> right
[10:09] <humphreybc> be back soon
[10:12] <dpm> jenkins, I've had another look at the draft, it look fantastic to me. That, plus some styling, was exactly what I was looking for. What would be the next step to basically make it look awesome?
[10:13] <jenkins> dpm basically its what do you want changed and where
[10:14] <dpm> jenkins, so shall I just make a list and add it as a reply to your e-mail?
[10:15] <jenkins> that woul dbe great
[10:15] <nisshh> dpm: who are you?
[10:16] <jenkins> translations cordinator iirc
[10:16] <dpm> nisshh, and you? :)
[10:16] <vish> nisshh: https://launchpad.net/~dpm
[10:16] <dpm> https://launchpad.net/~dpm
[10:16] <vish> :)
[10:16] <dpm> ah, vish beat me to it :)
[10:16] <nisshh> ah
[10:16] <nisshh> cool
[10:16] <nisshh> i was like "who the hell is this guy he knows everyone!
[10:17] <nisshh> "
[10:17] <dpm> hahaha
[10:17] <nisshh> dpm: https://launchpad.net/~nisshh
[10:18] <dpm> nice to meet you then, nisshh :)
[10:18] <nisshh> you too dpm :)
[10:45] <dpm> jenkins, while I'm preparing that list of what I'd like changed in the booklet and where, I've got a couple of questions. I've got limited experience with docbook stylesheets, but I did try creating the PDF from the original docbook article. I tried the nwalsh stylesheet and also docbook2pdf. They were ok, but the images were scaled and looked just wrong with the nwalsh stylesheet and they just didn't appear on the docbook2pdf output. I'd like to play
[10:45] <dpm> with the resulting PDF to understand what can be changed - what did you use to generate your draft PDF?
[10:46] <jenkins> I converted the docbook to latex, then played with the scaling
[10:49] <jenkins> dpm: if you look in the branch there is a *.tex file which has all the styles etc in
[10:50] <dpm> jenkins, yeah, I saw the file, but I wasn't too sure how it was exactly used. So how do you do the conversion to latex and then to PDF?
[10:53] <jenkins> I used dblatex but did a lot of minor tweeks, you need to install latex from the manual team ppa as per http://freakaboutlinux.wordpress.com/2010/06/15/tip-using-the-ubuntu-manual-projects-ppa/ . you then need to run two commands which i will look up
[10:53] <jenkins> xindy -C utf8 -M texindy -L english ubuntu-translations-quickstart.idx
[10:54] <jenkins> xelatex ubuntu-translations-quickstart.tex
[10:54] <jenkins> that will build the pdf file
[10:54] <dpm> awesome, I'll try that, thanks.
[10:55] <jenkins> no worries shout if you need some help
[10:57] <dpm> jenkins, so why does latex need to be installed from the PPA? is that a post-Lucid upstream version with bug fixes or new features, or modified by the manual team?
[10:58] <jenkins> dpm: it is a version newer than lucid, I have not tried but you could try just installing the xindy, xindy-rules and cciocns  packages from the ppa and stick with the lucid stuff.
[10:58] <dpm> ok, thanks, I'll try to play with it
[14:33] <daker> hello
=== daker_ is now known as daker
[19:19] <trijntje> Hi, I recently noticed that the ubuntu-manual can be translated to dutch with open permissions. The ubuntu dutch translation team has been working on the manual for quite some time, so we were wondering if the permissions could be changed to "structured" to make sure our work is preserved
[19:28] <jenkins> trijntje: I don't see why you can not change it there was a discussion on the mailing list about 6 months back, about it i will see if i can find it
[19:32] <jenkins> trijntje: I checked the e-mail and feel free we decided people could change to structured if they wished
[19:34] <trijntje> jenkins, thanks a lot for the information, ill send a mail to our team leader
=== topo is now known as Guest37376
=== Zeike is now known as brandonj