[09:06] <hannie> I have a question on string 254:
[09:07] <hannie> The \menu{Places} menu holds a list of commonly used folders (such as \menu{Documents}, \menu{Music}, \menu{Downloads}, and the \menu{Home Folder}).
[09:07] <nisshh> hannie: yep
[09:07] <nisshh> hannie: what about it?
[09:07] <hannie> It says \menu{Documents}, etc
[09:08] <nisshh> yea?
[09:08] <hannie> But they are folders, not menus
[09:08] <nisshh> ah
[09:08] <hannie> Do you understand what I mean?
[09:08] <nisshh> yea
[09:09] <hannie> Is there a command \folder{Documents}, etc
[09:09] <nisshh> i dont know
[09:09] <nisshh> if there isnt, i would just remove the commands, and leave it as normal text
[09:09] <nisshh> just keep the \menu{Places} one
[09:10] <nisshh> hannie: try the folder command first, i dont know if there is one but try it
[09:10] <nisshh> otherwise id just scrap it
[09:10] <hannie> I'm not sure if it is wise to make a bug report on this
[09:11] <nisshh> i dont think its needed
[09:12] <hannie> ok, thanks for your reaction
[09:12] <nisshh> np :)
[10:38] <jenkins> morning
[10:39] <nisshh> jenkins: hey
[10:39] <nisshh> except its evening for me
[10:39] <jenkins> hey nisshh
[10:39] <jenkins> morning/evening/afternoon
[10:39] <nisshh> hehe
[10:40] <jenkins> please delete as appropriate
[10:40] <nisshh> jenkins: iv been making good progress on the dev manual lately, there are nearly three chapters in the branch now
[10:40] <jenkins> wow, you have been busy
[10:41] <jenkins> i will get my chapters done soon, just been busy latly
[10:41] <jenkins> we have been writing in us english right?
[10:41] <nisshh> yes
[10:41] <nisshh> well i have
[10:41] <jenkins> cool, I will do as well
[10:42] <nisshh> i havent had time to go through, lonewaises chapter yet
[10:42] <nisshh> he is writing the indicators chapter
[10:48] <jenkins> I have no clue on the inicators and how they work/how to make them
[10:51] <nisshh> jenkins: yea, i know a little but not much more than you about them
[10:52] <jenkins> what about the windicators?
[10:54] <jenkins> are we doing those?
[10:59]  * vish thinks writing a chapter for a non-existent thing-a-ma-gij , might be a waste of time :)
[10:59] <vish> jig*
[11:00] <nisshh> jenkins: no, we are not doing windicators, they arent even in 10.10 yet
[11:00]  * nisshh agrees with vish 
[11:01] <jenkins> O right I did not know they were not in mavrick, my download limit at home means no testing
[12:16] <somethinginteres> hi all, I think I found a small mistake in the manual. Just a typo: Pg. 9 first sentence
[12:20] <jenkins>  somethinginteres can you file a bug here please https://bugs.edge.launchpad.net/ubuntu-manual , that way the editors can change it
[12:21] <jenkins> daker: on the quickshot website is it possible to see what rounding the bottom left and right corners would look like?
[12:21] <somethinginteres> jenkins: no problem
[12:21] <jenkins> thanks somethinginteres
[12:22] <daker> jenkins, i will show you something
[12:22] <jenkins> cool
[12:24] <somethinginteres> jenkins: is the manual included on the Ubuntu CD's by default? I think that would be a good idea - I wish I had've found this a few months ago :) I'd be happy to submit a brainstorm if you think that'd be a good idea
[12:25] <jenkins> somethinginteres: I am glad you find it useful, it is not by default we would like it to be but there is the difficult task of how to deal with translations, feel free to add it to brainstorm
[12:27] <somethinginteres> jenkins: OK, will do. Also, apparently the error I found is marked as "Fix Released" so no issue there :)
[12:27] <jenkins> there is the system docs already on the ubuntu cd incase you did not know
[12:27] <jenkins> thanks for looking though
[15:41] <jenkins> dpm: how is your latex playing going?
[15:44] <jenkins> what else needs doing to the guide?
[15:45] <dpm> hey jenkins, actually quite well, I've just pushed a new revision of the quickstart guide using dblatex - I'm still meaning to come back to you, but I want to understand the tools well first :)
[15:46] <dpm> here are my experiments:
[15:46] <dpm> http://bazaar.launchpad.net/~dpm/ubuntu-translations-quickstart/trunk/files/head:/output/
[15:46] <dpm> one is the one you generated
[15:46] <dpm> the other one generated from the docbook document with xsltproc + fop
[15:46] <dpm> and the other one with dblatex
[15:47] <dpm> I'd like to have only one source document, and I'd prefer it to be the docbook one, and the latex one just be an intermediate step
[15:48] <jenkins> they look good, I found dblatex was ok to convert the main bulk of the text but not very good after that it uses their own style. I am yet to work out how to make dblatex uses custom styles
[15:49] <dpm> jenkins, I'm using (very basic) custom styles with dblatex - have a look at the makefile and the stylesheet directories here:
[15:49] <dpm> http://bazaar.launchpad.net/~dpm/ubuntu-translations-quickstart/trunk/files
[15:49] <jenkins> how well do custom styles work?
[15:50] <dpm> I know how to use them now, but unfortunately my latex knowledge is limited :)
[15:51] <jenkins> I don't know loads of it as the manual uses many custom commads, what are you trying to achive in latex?
[15:51] <dpm> I'm just finding difficulties on the precedence of options set in the custom style file - some seem to be overriden
[15:52] <jenkins> hmm I will have a play with what you have done
[15:52] <dpm> I'm trying to achieve several things:
[15:53] <dpm> * To have a single source document - either the docbook xml or the latex one, but not both
[15:53] <dpm> I'd prefer the docbook one, as I want to make the guide translatable
[15:54] <jenkins> docbook is the most flexible at doing different formats
[15:54] <dpm> and the extracted strings from xml are more translator-friendly than latex
[15:54] <jenkins> I have not had any experince with that but I am sure it is
[15:55] <dpm> * the next objective is for the final pdf document to look good :)
[15:55] <jenkins> what colours font and style do you think we should use?
[15:56] <dpm> I'm not sure about the font type yet, but I think section titles would look good in Ubuntu orange
[15:58] <jenkins> yep that sounds good, it might be easier to make the custom dblatex style sheet by also generating the *.tex file. Then you can work out what is being done where and what needs changing
[16:01] <dpm> yeah, I'll keep looking at it in the next couple of days - I need to hop on a call, but I'll be back later on
[16:03] <dpm> I'll have more questions as well :)
[16:03] <jenkins> cool talk later
[17:33] <jenkins> dpm: I have to run, everyone will be back from work and wanting food soon. I am out tonight but you can drop me an e-mail or grab me tomorrow and I will answer your wuestions
[17:33] <jenkins> *questions
[17:34] <dpm> ok, thanks jenkins!
[17:34] <jenkins> talk soon o/
[17:34] <dpm> have a nice evening!
[17:34] <jenkins> and you
[20:05] <trijntje> Hi all, what must I do to get the permisions for translating the manual to dutch set to "structured"?
[22:23] <jenkins> godbyk: ping
[22:33] <jenkins> is it bad that I am writing my Scout news letter in latex?
[22:34] <jenkins> some how I find a text editor so nice
[22:58] <jenkins> I like doing this news letter in latex some how doing the layout seams so much easier
[23:05]  * jenkins tires not to put emotions in the news letter
[23:17] <jenkins> I am learning how to do tables in latex after this I may just do everything in latex
[23:47] <infosoft> jenkins: You should try David R. Wilkins - Getting Started with LATEX (http://www.maths.tcd.ie/~dwilkins/LaTeXPrimer/) :)
[23:50] <jenkins> hey infosoft, thanks I don't think we have met before o/ . Any suggestions on a good document class to use?