[07:40] <thorwil> godbyk: i initially though of generating half-title SVGs via regex. but as PDFs are the actual goal, i will check now if inkscape on the cli can do that
[07:40] <godbyk> inkscape can convert from svg to pdf on the command-line.
[07:41] <godbyk> thorwil: inkscape --export-text-to-path --export-pdf=output.pdf input.svg
[07:41] <thorwil> yes, and it has an only-this-layer flag, which i only used for PNG export, s far
[07:41] <godbyk> ooh, nice. I didn't know about that flag.
[07:43] <thorwil> yesterday, i had to learn that regex matching on a multi-line pattern sucks, be it sed or awk. and a last quick attempt with perl didn't work out, either
[07:43] <godbyk> thorwil: That's true. Though most regex systems have a flag you can set to allow . to match end-of-line characters.
[07:43] <godbyk> If SVG is true XML, then we could also use a real XML parser to make the modifications.
[07:44] <thorwil> godbyk: i think i got sed to handle that, but than stumbled over its greedy matching :)
[07:44] <godbyk> thorwil: Ha! There's that, too. Another flag can let you work around that sometimes.
[07:45] <thorwil> godbyk: i considered that, but i doubt we want a dependency on xsltproc or
[07:46] <thorwil> saxon
[07:47] <godbyk> Well, it'd really only be a dependency for you or me or whoever generates the title pages and covers.
[07:49] <benonsoftware> Sorry to bother all but whats the bzr command to get the lastest branch?
[07:50] <thorwil> godbyk: inkscape --export-pdf=half-title_en.pdf --export-id=title --export-area-page titlepage-en.svg
[07:50] <godbyk> benonsoftware: bzr pull
[07:51] <godbyk> benonsoftware: Or if you don't have the precise branch checked out yet: bzr branch lp:ubuntu-manual/precise ubuntu-manual-precise
[07:51] <godbyk> thorwil: Cool. So the --export-id will snag just the one element we care about?
[07:52] <thorwil> godbyk: yes. and without --export-area-page, it would use the bounding box of the content
[07:52] <benonsoftware> Thanks godbyk
[07:53] <thorwil> godbyk: now, a bash script to generate half-title PDFs for all titlepage_*.svg in the dir, or a script that takes an argument?
[07:53] <godbyk> thorwil: Probably takes an argument.
[07:54] <godbyk> thorwil: My inkscape takes so long to start up right now because it has to load my huge font collection.
[07:54] <godbyk> I wish there were a 'ignore all the fonts but those required for this svg' command-line option. :)
[07:54] <thorwil> godbyk: here it's instant on the shell, while the gui does take time
[07:55] <godbyk> I'll give it a shot here.
[07:56] <godbyk> thorwil: Ah, you're right. It is fast on the command line.
[07:56] <thorwil> godbyk: i'll write a script that takes an svg as arg and add it to the repo
[07:57] <godbyk> thorwil: Cool. Thanks!
[08:24] <thorwil> now how do i combine ${f##titlepage} with ${f%.*}?
[08:25] <thorwil> to get "-en" out of "titlepage-en.svg", for example
[08:29] <godbyk> thorwil: In a Makefile or bash script?
[08:30] <thorwil> bash
[08:30] <godbyk> thorwil: You could run it through sed: LANG=$(echo $FILENAME | sed -e 's/titlepage-//' -e 's/.svg')
[08:31] <godbyk> Or you could use bash's substring stuff since the titlepage- prefix is constant.
[08:32] <godbyk> LANG=$(basename ${FILENAME:10} .svg)
[08:32] <godbyk> (where 10 is the starting position)
[08:34] <godbyk> Instead of using the ## and % operators, you could use sed or basename. They're pretty standard.
[08:34] <godbyk> (I've never actually used the ## and % stuff in bash. Didn't realize they existed. I'll have to try to remember them.)
[08:37] <thorwil> so far the only way i found to combine them is by using a variable in between
[08:40] <godbyk> thorwil: I think you may be right.
[08:41] <godbyk> thorwil: Btw, when I replaced the header.png (UM logo) on our website, I noticed that there's also a header_rtl.png file: http://ubuntu-manual.org/images/header_rtl.png
[08:41] <godbyk> I'm not sure if it's actually used or not.
[08:42] <thorwil> godbyk: http://ubuntu-manual.org/?lang=ar
[08:44] <godbyk> Ah, snazzy!
[08:45] <godbyk> Do you have an updated RTL logo, then?
[08:46] <thorwil> godbyk: no, one moment and i create one in that size
[08:46] <godbyk> thorwil: 'kay. Thanks. No rush!
[08:52] <thorwil> godbyk: half-title script pushed (rev 93)
[08:52] <manualbot> http://bazaar.launchpad.net/ubuntu-manual/revision/93 | http://bazaar.launchpad.net/ubuntu-manual -r 93
[08:52] <godbyk> thorwil: I'll pull it and take a look at it. Thanks!
[08:52] <thorwil> np
[08:54] <thorwil> it's pretty nice how handling args as array also makes it work for wildcard expansion
[08:55] <godbyk> yeah.  well, bash expands the stuff before it passes it in as arguments to the script.
[08:56] <thorwil> well aware of that, as i wrote enough for-loops for commands that can't handle lists of filenames :)
[08:57] <godbyk> me too. :)
[09:04] <thorwil> godbyk: thanks for taking care of replacing the logo
[09:04] <thorwil> godbyk: rtl version: http://bazaar.launchpad.net/~t-w-/+junk/ubuntu_manual_cover/download/t_w_%40freenet.de-20120609090229-0t4ne2fs4yjl8hyg/ump_logo_h64_rtl.png-20120609090145-8z4980qs6mj5eay8-1/ump_logo_h64_rtl.png
[09:04] <godbyk> thorwil: No problem.
[09:06] <godbyk> thorwil: Updated: http://ubuntu-manual.org/?lang=ar
[09:20] <thorwil> bloddy caching, shift-f5 to the rescue. excellent!
[09:21] <smjms> hi, anyone here?
[09:21] <thorwil> hi smjms, yes
[09:21] <godbyk> Hey, thorwil. I fancied up your half-title page script. Now with colors! (Making errors unreadable. ;-))
[09:22] <godbyk> Hello, smjms.
[09:23] <thorwil> godbyk: heh, you don't like short scripts, eh?
[09:24] <godbyk> thorwil: They're too boring. ;-)
[09:24] <godbyk> Actually, I figured I'd add in some error-checking to help catch my stupid mistakes later.
[09:24] <godbyk> Otherwise I end up having to read through the script code to figure out how to run the thing each time.
[09:40] <smjms> so the manual is made with LaTeX?
[09:41] <godbyk> smjms: Yes.
[09:41] <smjms> Why is there no justification?
[09:42] <godbyk> smjms: Because justifying text can make it difficult to read. Also, having the text set ragged right makes it appear a bit friendlier.  (In short, it was a design decision.)
[09:42] <smjms> do you know 'microtype' package?
[09:42] <godbyk> smjms: Yes. Unfortunately, it doesn't work quite as nicely with XeLaTeX.
[09:43] <smjms> :I oh
[09:48] <godbyk> thorwil, smjms: Which times symbol do you like better? http://kevin.godby.org/temp/times.png
[09:48] <smjms> the first one seems a bit too high
[09:49] <thorwil> yes, too high
[09:49] <smjms> or the numbers too low
[09:49] <godbyk> smjms: It's centered vertically (I think), but we're using old-style figures.
[09:49] <godbyk> We're currently using the second symbol, but I think it's a bit large.
[09:49] <thorwil> the second doesn't sit quite right, either, but still better
[09:50] <godbyk> The first × is the one that comes with the text face.
[09:50] <godbyk> I wish I could split the difference. :)
[09:58] <godbyk> I'm off to bed. i'll see you guys at the meeting later. G'night!
[09:59] <thorwil> good night!
[10:02] <smjms> great night!
[10:02] <smjms> meeting?
[10:03] <benonsoftware> What time is the meeting at?
[10:03] <thorwil> benonsoftware, smjms: see http://www.doodle.com/ywrkhi3pa5d6s4kh#
[10:04] <benonsoftware> Ohm, yes. It's at 3AM for me L.
[10:04] <benonsoftware> :/*
[10:04] <thorwil> agenda: http://typewith.me/p/UMP-12-04-5thMeeting
[16:50] <vibhav> Has the meeting started?
[17:12] <jconnett_> Greetings!
[18:01] <hannie> Hello everyone
[18:01] <PaddyLandau> Hello Hannie
[18:01] <jimc> Greetings from the Pacific Northwest in USA
[18:01] <carsten> Hello together
[18:01] <hannie> hey PaddyLandau glad you join us
[18:01] <PaddyLandau> Thank you.
[18:02]  * godbyk is getting a glass of water.. will be right back.
[18:02] <thorwil> hi everyone
[18:02] <TonyP> Hi Hannie
[18:02] <ajmontag> hello all
[18:02] <hannie> welcome jimc carsten thorwil TonyP
[18:02] <jimc> ...glad to be here
[18:02] <kereltis> Hi guys
[18:02] <hannie> jimc, are you overworked yet? ;)
[18:03] <hannie> hi kereltis
[18:03] <godbyk> Hello, everyone.
[18:03] <jimc> ...funny you should ask...will email the group on a followup to my editing of "getting online" (my head hurts)
[18:03] <hannie> hey godbyk
[18:03] <godbyk> c7p said he may be a bit late to today's meeting and that we shouldn't wait on him.
[18:03] <hannie> jimc, ow
[18:04] <hannie> ok, then we are complete I suppose
[18:04] <jimc> Let's go!
[18:04] <godbyk> All right, we'll get started.
[18:04] <godbyk> #startmeeting
[18:04] <meetingology> Meeting started Sat Jun  9 18:04:51 2012 UTC.  The chair is godbyk. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[18:04] <meetingology> Available commands: #accept #accepted #action #agree #agreed #chair #commands #endmeeting #endvote #halp #help #idea #info #link #lurk #meetingname #meetingtopic #nick #progress #rejected #replay #restrictlogs #save #startmeeting #subtopic #topic #unchair #undo #unlurk #vote #voters #votesrequired
[18:05] <hannie> http://typewith.me/p/UMP-12-04-5thMeeting
[18:05] <godbyk> The meeting agenda is at <http://typewith.me/p/UMP-12-04-5thMeeting>
[18:05] <godbyk> #topic Attendance
[18:05] <godbyk> First off, we'll take attendance.
[18:05] <godbyk> If everyone present could just say 'hello'.
[18:05]  * c7p waves
[18:05] <hannie> hey c7p
[18:05] <godbyk> Hey, c7p.
[18:05] <PaddyLandau> hello
[18:05] <c7p> hello
[18:05] <thorwil> hello
[18:05] <kereltis> hello
[18:05] <TonyP> hello
[18:05] <jimc> hello
[18:05] <ajmontag> hello
[18:05] <carsten> hello
[18:05] <hannie> hello
[18:06] <godbyk> Thanks.
[18:06] <godbyk> #topic New member introductions
[18:06] <godbyk> Do we have any new members here today?
[18:06] <PaddyLandau> Yes, I am a new member.
[18:06] <TonyP> I am Tony Pursell.  I live in the UK.  You can see me at https://launchpad.net/~ajpursell and http://wiki.ubuntu.com/TonyPursell. I have volunteered to do editing on this project
[18:06] <jimc> I am. Glad to be here.  Have been contributing for about three weeks now. Great project. An honor to be a part of this work in progress.
[18:07] <PaddyLandau> I see I need to say more. I also live in the UK, in Oxford. I volunteered for proof-reading after being asked to. I am not familiar with IRC, so please forgive me if I make etiquette mistakes.
[18:07] <godbyk> Awesome! Thanks a lot for your help, guys.  Feel free to pester us with questions on IRC or the mailing list.
[18:07] <hannie> jimc, PaddyLandau TonyP carsten all new and eager
[18:07] <PaddyLandau> LOL
[18:08] <godbyk> #topic Editing and proofreading process / status reports
[18:08] <godbyk> Our original schedule has 15 June as the deadline for editing.
[18:09] <godbyk> I wanted to check in with our editors to see how things are going.
[18:09] <godbyk> Have you hit any snags or encountered any problems?
[18:09] <godbyk> Are things going fairly smoothly?
[18:09] <godbyk> Do you think you'll be able to complete your assigned sections/chapters on time?
[18:10] <hannie> First we want to hear from the editors if they are ok, then I will say something about the status
[18:10] <jimc> From my vantage, things are going well. Challenges include getting up to speed on tex tags and my obsessive editing.
[18:10] <ajmontag> Have all the sections been converted from Libre Office to LaTeX that needed to be?
[18:11] <TonyP> I should be OK with Ubuntu One section. I have done some and will review it again.
[18:11] <hannie> ajmontag, yes
[18:11] <jimc> Using the Desktop is pretty much done (will want to do one more pass through in a few days)
[18:11] <jimc> I just finished editing the Advanced Topics section this morning...will commit and push later today.
[18:12] <hannie> jimc, that was the chapter that needed a lot of work, so thanks for what you did
[18:12] <jimc> hannie, no problem...sort of jumped directly into the fire with that one.
[18:12] <hannie> good!
[18:13] <jimc> I 'accidentally' edited the Burining CD section last night as well...still needs screenshots.
[18:13] <hannie> jimc, ok, I will put it on the sheet
[18:14] <jimc> The GettingOnline section needs more work and I'm taking care of that at this time.
[18:14] <jimc> Anyone else?
[18:14] <hannie> If editors have no questions or remarks, shall I proceed with the details?
[18:15] <PaddyLandau> I have a question as a proof-reader. Is this the right time?
[18:15] <godbyk> PaddyLandau: Sure, fire away!
[18:15] <hannie> go ahead
[18:15] <PaddyLandau> OK...
[18:16] <PaddyLandau> I have been using gedit and Meld to edit the files. However, they do not show the finished product, which means it is easy to slip in syntax errors, e.g. with tags.
[18:16] <PaddyLandau> I found that Gummi is a brilliant Latex editor, showing the results as you type.
[18:16] <PaddyLandau> However...
[18:16] <PaddyLandau> Gummi does not recognise many of the Ubuntu tags, such as \keystroke.
[18:17] <PaddyLandau> Does anyone know if it is possible to add the Ubuntu style files (well, I'm presuming they are style files -- I may wrong) to Gummi?
[18:17] <PaddyLandau> If not, don't worry, I'll just continue with gedit and Meld.
[18:17] <TonyP> I just keep re-making the PDF
[18:17] <PaddyLandau> That's quite tiresome, isn't it?
[18:17] <godbyk> PaddyLandau: I haven't used Gummi. I'm not sure if it's possible to teach it the Ubuntu Manual tags or not. Sorry.
[18:17] <jimc> WineFish is a great editor, especially with regards to tags (open close brackets)...parallels what you'd see in an IDE environment.  Worth a try.
[18:18] <PaddyLandau> WineFish. I'll try it, thanks.
[18:18] <hannie> PaddyLandau, you have installed TeX Live, so you can make the pdf file any time you want
[18:18] <c7p> from what is see Gummi has  		Customizable compilation/typesetting options , is that what we need ?
[18:18] <PaddyLandau> Hannie: I'll learn how to do that and see. It's not quite the same as seeing it immediately, but it would help.
[18:19] <hannie> no wysiwyg
[18:19] <PaddyLandau> c7p: Where did you see those options?
[18:19] <jimc> I think getting everyone on the same editing environment would definitely advance the editing process...common environment, common configuration. May be a good thing to pursue for 12.10.
[18:19] <c7p> http://dev.midnightcoding.org/projects/gummi/wiki/Index
[18:19] <godbyk> PaddyLandau: Can gummi not compile the manual?
[18:19] <PaddyLandau> c7p: Thanks, I'll look into it.
[18:19] <jimc> I've tried Gummi, too...no compilation.
[18:20] <PaddyLandau> godbyl: No, it cannot, because it does not recognise the Ubuntu tags.
[18:20] <hannie> jimc, I think it does not matter what editor you use, as long as you put in the right code
[18:20] <godbyk> Strange.
[18:20] <PaddyLandau> Well, I'll have a look into it, and if I find an answer, I'll let you all know. Thanks for all the replies.
[18:20] <godbyk> PaddyLandau: Make sure you have gummi compile using XeLaTeX instead of pdfLaTeX.
[18:21] <godbyk> PaddyLandau: Otherwise, it should find the Ubuntu Manual–specific stuff in the same directory as the main .tex file.
[18:21] <PaddyLandau> Hmm, these are things I don't quite understand. Is that in the Gummi options?
[18:21] <jimc> hannie, but a lack of uniformity in how we implement tags could be easily resolved with an importable xml file into any editor
[18:21] <godbyk> PaddyLandau: Looking at the screenshots, it's under preferences > compilation tab > texlive with xetex
[18:21] <jimc> PaddyLandau, I'll give this a try!  Thanks.  Would be nice to see edits live.
[18:22]  * c7p it looks interesting 
[18:22] <hannie> I suggest we exchange experiences with Gummi on the mailing list
[18:22] <PaddyLandau> Ah, I see that. I do not have the option to change it. It is set at TexLive with PdfTex, and the other options are greyed out.
[18:22] <jimc> I also have a question (seems a little pithy with the previous discussion)...
[18:22] <godbyk> There are other editors that can do some live compiling, too.  I believe TeXworks can do that.
[18:22] <jimc> Can we agree on one space after a period or two?  I think the accepted standard is ONE, but I'm seeing both.
[18:23] <hannie> jimc, one
[18:23] <PaddyLandau> godbyk: I'll have a look at TeXworks, thanks.
[18:23] <godbyk> jimc: It doesn't matter in the source. LaTeX will use the proper spacing when it typesets it.
[18:23] <hannie> two is one too much
[18:23] <jimc> godbyk, AWESOME...thanks.
[18:23] <PaddyLandau> jimc: Two spaces came from the old days of manual and electronic typewriters; one space is handled correctly with modern automated typesetting.
[18:23] <PaddyLandau> So, one space is the standard these days.
[18:24] <jimc> PaddyLandau, beauty!  No more looking for spaces.
[18:24] <jimc> I have no more questions.
[18:24] <hannie> thanks for the tip, godbyk didn't know that
[18:24] <godbyk> Okay, hannie. Did you want to talk about editing a bit?
[18:25] <hannie> ok, I will talk about some details (agenda)
[18:25] <hannie> 1. Allow authors to write in LO
[18:25] <hannie> I think it is too much work converting odt files, so I am against it
[18:26] <godbyk> We'll put these under their own topics to make the minutes easier to read.
[18:26] <godbyk> #topic Editing with LibreOffice
[18:26] <hannie> right
[18:26] <hannie> What do other think about this?
[18:26] <hannie> *others
[18:27] <PaddyLandau> I personally would find editing in LO a distraction, because it would all have to be converted to LaTex.
[18:27] <godbyk> I tend to agree with hannie: I think it's easier if we get edited .tex files (even if they have syntax errors or other issues).
[18:27] <carsten> Sorry, I lost internet connection...
[18:27] <jimc> I agree, too, Hannie.  Our previous discussion about editing applications prove that there is really no advantage to using LO.
[18:27] <thorwil> it could be handled, if there was automatic conversion
[18:27] <carsten> What did I miss?
[18:27] <thorwil> but i guess we have no one deep enough in LO/ODF to take care of that
[18:27] <c7p> i agree too
[18:27] <hannie> carsten, we currently talk about odt file conversion
[18:27] <PaddyLandau> carsten: Is it possible to cut-and-paste and send it to you?
[18:27] <kereltis> I think it's a good idea, it will attract more authors/editors to the project and then we can say the manual was created using stock Ubuntu.
[18:27] <jimc> Most tex editors are simply TEXT editors at heart (can you say Windows NotePad?)...with added features if desired.
[18:28] <c7p> we should take that into consideration too kereltis
[18:28] <hannie> I agree here. Authors do not necessarily have to add latex code. others can do it for them
[18:29] <ajmontag> regarding odt conversion: I found that things like marginnotes, screenshot marginnotes, and menu -> traills did not get written properly in LO
[18:29] <PaddyLandau> One problem with using LO is that you may be tempted to use features that LaTex does not support. That would hinder the process of converting.
[18:29] <godbyk> Has anyone here been using LibreOffice to write/edit sections or chapters?
[18:29] <jimc> IF we go this path, we may need a little more organization at the odt integration level...seems we got a few "late" submissions this time around.
[18:29] <carsten> PaddyLandau: You mean an odf file? Sure send it.
[18:29] <jimc> godbyk, not I.
[18:29] <hannie> carsten, is the specialist here ;)
[18:29] <carsten> Best would be to the list
[18:30] <carsten> Well, specialist is good^^
[18:30] <godbyk> Okay.
[18:31] <carsten> Most of this work is handmade :-)
[18:31] <hannie> PaddyLandau, you can save an odt file as a text file and then add the code
[18:31] <godbyk> When I've converted from LibreOffice files to .tex files, I found that it took a lot of work to add the markup by hand after the fact.
[18:31] <godbyk> I had to read through everything carefully and decide myself how to tag everything. (And to figure out when the author wanted something to be a margin note, for instance.)
[18:31] <jimc> godbyk, haven't done this, but EASILY agree based on my new experiences.
[18:31] <hannie> So, may we conclude that it is better NOT to write in LO?
[18:31] <PaddyLandau> Hannie: I suppose I could, but gedit colours the tags and other code to make it easier to follow. LO does not do that.
[18:32] <ajmontag> I think it would be better to force people to write in LaTeX, but then have designated LaTeX proofreaders for those who are not confident
[18:32] <PaddyLandau> ajmontag: That makes sense to me.
[18:32] <godbyk> I propose the following:
[18:32] <hannie> ajmontag, no, they can write in a normal text editor
[18:32] <ajmontag> godbyk: i agree
[18:32] <jimc> ajmontag, and by doing this (specific LaTeX editors), you will bring uniformity to the tags...brilliant!
[18:33] <godbyk> We'll disallow LibreOffice. For those who don't want to or aren't able to compile the .tex files, they can submit their .tex files to an editor and have one of them check the syntax and commit it to bzr.
[18:33] <PaddyLandau> jimc, etc.: Surely the person can use whichever *text* editor he prefers?
[18:33] <hannie> +1
[18:33] <ajmontag> hannie, jimc: I think people can use any editor (i use Sublime Text 2)
[18:33] <godbyk> PaddyLandau: I think you can use whichever text editor you like.
[18:34] <PaddyLandau> godbyk: Cool. If we can find a LaTex editor that recognises Ubuntu tags, that would help things, but it wouldn't be mandatory.
[18:34] <ajmontag> text editors are a personal preference
[18:34] <jimc> ...I meant specific PEOPLE who would be designated as LaTeX editors.
[18:34] <godbyk> PaddyLandau: Right. You can also run 'make' from the command line to build the PDF.
[18:34] <jimc> ...the small group of LaTeX editors could agree on tags to use, when, etc.
[18:35] <ajmontag> jimc, good idea
[18:35] <hannie> jimc, that is how it mainly works at this moment (latex editors who check/add code where necessary)
[18:35] <PaddyLandau> We have the style-sheet guide already, to which I have been referring quite often.
[18:35] <TonyP> Can you just compile small sections to PDF?
[18:36] <godbyk> TonyP: There's no easy way to do that at the moment, I'm afraid.
[18:36] <jimc> hannie, PaddyLandau, true.
[18:36] <TonyP> Pity
[18:36] <godbyk> Speaking of the style guide, if anyone has any questions / suggestions / comments / concerns / etc. about it please email me.
[18:36] <PaddyLandau> godbyk: That would be a problem for me, as I only get short sections to proof-read. That's why I wanted something like Gummi (sorry to mention it again).
[18:36] <carsten> TonyP, yes. Just comment all sections which you don't want to see in the main.tex
[18:36] <jimc> TonyP, agreed.  That would be NICE!
[18:37] <jimc> carsten, UGH!  That would take forever, wouldn't it?
[18:37] <hannie> PaddyLandau, you can easily navigate to "your" section in the pdf file
[18:37] <godbyk> My only concern with modifying main.tex to only show your chapter is that it might accidentally get committed to bzr.
[18:38] <PaddyLandau> Hannie: Yes, I have been doing that. But I would not be able to "make" the PDF file from the section that you have given me, so I have no way to check my editing for syntax or other errors, apart from spelling mistakes.
[18:38] <godbyk> PaddyLandau: Ah, right. You'll need all the .tex files to build the PDF.
[18:39] <hannie> PaddyLandau, why don't you just navigate to the section you are working on to check it?
[18:39] <jimc> Me thinks it would be MUCH faster to re-make everytime than to comment out sections.
[18:39] <godbyk> jimc: Probably.
[18:40] <TonyP> Is it possible to have a make option to use a mymain.tex
[18:40] <jimc> hannie, I think PaddyLandau is trying to find a way to ONLY compile the section being edited rather than the 150 page manual each time a change is made.
[18:40] <PaddyLandau> godbyk: That's right. That's why I'd love a text editor that shows changes on-the-fly. I will take today's suggestions to try to find out how to fix Gummi or an equivalent to recognise Ubuntu's tags, and let you all know if I succeed.
[18:40] <PaddyLandau> Hannie: I can't do that, because I can't make the PDF.
[18:40] <hannie> I see no need for making separate sections/chapters. Make only takes less than a minute
[18:40] <godbyk> It does take a little time to learn to trust your abilities in editing the .tex files. But after a while, you find that you don't need to rebuild the PDF as frequently to check formatting, etc.
[18:40] <hannie> It is done in a jiffy
[18:41] <jimc> godbyk, experience speaking, I agree.
[18:41] <ajmontag> godbyk, agreed. Once you are comfortable with the tags its not a big deal
[18:41] <PaddyLandau> Maybe I'm missing something. Is it possible to make the PDF when I have just the one section that I am proof-reading?
[18:41] <hannie> godbyk, enough said on LO?
[18:41] <jimc> PaddyLandau, NO.
[18:41] <ajmontag> If you are unsure you can always check the style guide :)
[18:41] <godbyk> PaddyLandau: No. You need the entire bzr repository to build the PDF
[18:41] <PaddyLandau> godbyk: Yes, that's what I was thinking.
[18:41] <jimc> godbyk, yes
[18:41] <godbyk> hannie: I think so.
[18:41] <godbyk> Let's move on to our next agenda item.
[18:42] <jimc> GO
[18:42] <godbyk> #topic Authors and editors working as a team
[18:42] <godbyk> Hannie?
[18:42] <hannie> https://docs.google.com/spreadsheet/ccc?key=0Ar0Z6vOO38EydEdaSnhSX2M2WDdSZ3VGQk1qMDZBbHc#gid=1
[18:42] <carsten> Well jimc, I yust tried the \begin{comment   \end{comment} in main.tex to compile only the installation section. It took the only 15 sec compared to the whole document with 1 minute.
[18:42] <hannie> Status draft
[18:43] <hannie> godbyk, I pasted a link to our spreadsheet where everyone can see the current status
[18:43] <jimc> carsten, AHHHH, my bad...forgot about the main.tex file.  I was thinking all sub- .tex files would need editing!  My apologies.
[18:43] <godbyk> carsten: You might also look into the \includeonly macro. But be careful that you never commit your main.tex changes to bzr. It'll confuse everyone else. :-)
[18:44] <carsten> Yes of course godbyk.
[18:44] <c7p> gj hannie
[18:44] <hannie> Have a look at the sheet 12.04 finished
[18:44] <godbyk> hannie: Thanks. Are there sections that still need editors or do we have everything covered now?
[18:44] <carsten> I use Bazaar Explorer, who is showing very well which files are modified.
[18:45] <hannie> I think we can cover it with the team of editors we have
[18:45] <hannie> Thanks to all their hard work!
[18:45] <jimc> ....not to throw us off topic, but one quick question...
[18:46] <hannie> jimc, ?
[18:46] <jimc> will we have a debrief after 12.04 is released? I have a few suggestions on the editing process (structurally).
[18:46] <godbyk> jimc: Absolutely.
[18:46] <hannie> good suggestion
[18:46] <jimc> Great.  Thanks.
[18:46] <PaddyLandau> Another off-topic: May I ask why the deadline for the manual is *after* the release of the distribution? It seems the wrong way around to me.
[18:46] <godbyk> jimc: We'd definitely like to gather suggestions and ideas for improving the process for 12.10.
[18:46] <jimc> godbyk, count me in!
[18:47] <hannie> PaddyLandau, not everyone installs the beta version in VM
[18:47] <godbyk> PaddyLandau: Well, we got a late start.
[18:47] <jimc> PaddyLandau, the software has to be released in it's final version before a manual can be written.
[18:47] <PaddyLandau> Hannie, godbyk, jimc: OK.
[18:47] <godbyk> PaddyLandau: Also, we do have to wait to take screenshots until after UI freeze, for instance.
[18:47] <PaddyLandau> Right, makes sense.
[18:47] <hannie> I think the difference between precise and quantal will be even smaller
[18:48] <kereltis> PaddyLandau, we're working on ways to improve this and we have created a guide for installing the beta in a vm for new authors
[18:48] <godbyk> We could write a lot of the manual earlier -- as long as they don't change things at the last minute. :)
[18:48] <jimc> LTS vs minor!  Wohoo!
[18:48] <PaddyLandau> LOL, godbyk, yes, I know exactly what you mean! It has been done with Precise.
[18:48] <hannie> Next time we'll do it in one month :)
[18:49] <c7p> hell yeah !
[18:49] <godbyk> hannie: Shall we move on to the next topic or did you have more to say on this one?
[18:49] <jimc> hannie, you a taskmaster!
[18:49] <hannie> godbyk, ok
[18:49] <godbyk> #topic Style guide
[18:49] <hannie> godbyk, you forgot teams
[18:50] <godbyk> This deals with when you use \menu vs. \application. The capitalization and spelling of words. Etc.
[18:50] <godbyk> hannie: That's what we were just discussing. :)
[18:50] <godbyk> Do you want to go back to that?
[18:50] <hannie> godbyk, the previous item was "Status draft"
[18:51] <godbyk> hannie: The previous topic was "Authors and editors working as a team"
[18:51] <godbyk> #topic Authors and editors working as a team (redux)
[18:51] <hannie> Well, I just wanted to know from authors/editors if they want to use a shared document
[18:51] <godbyk> hannie: Ah, go ahead.
[18:52] <hannie> In the previous meeting Bryan explained how we worked with Learning More
[18:52] <hannie> We use a shared document (just publish the .tex file in UbuntuOne)
[18:52] <PaddyLandau> A shared document would be a problem if there was not strict locking on sections that were being worked on. I don't know, however, how it would affect your (Hannie's) workflow as a controller.
[18:52] <hannie> So author and editor can see what is changed and they can discuss it if necessary
[18:53] <hannie> PaddyLandau, you share it only with your editor
[18:53] <godbyk> PaddyLandau: I think the document is shared only between the author and their section/chapter editor.
[18:53] <PaddyLandau> Oh, I see. How would it work exactly?
[18:53] <hannie> The author publishes his .tex file, the editor adds changes which the author can see
[18:54] <PaddyLandau> OK. That would do away with your current method of working with Meld, I suppose?
[18:54] <jimc> PaddyLandau, if there were locking controls in shared environment where only "assigned" editors would have access to authored sections, then I would be in agreement with this approach.
[18:54] <hannie> if there is a disagreement or a special point they can discuss it in the comment section
[18:55] <PaddyLandau> I don't have a problem with that, as long as the editor in question highlights the syntax (as gedit does at the moment).
[18:55] <hannie> It worked well for me, so if others want to do the same they can do so
[18:55] <PaddyLandau> Without that highlighting, it becomes hard to find one's way around.
[18:55] <godbyk> PaddyLandau: You could use whichever text editor you like. It'll be a .tex file on your computer.
[18:55] <jimc> Maybe try this approach with 12.10 since we've already established it would be minor at best?
[18:56] <jimc> hannie, would this create another layer of management and logistics for you?
[18:56] <hannie> ok, I can describe this in an email to the m/list
[18:56] <hannie> jimc, it would need less emails from my side
[18:57] <carsten> hannie: this would be good
[18:57] <jimc> hannie, good that it's a win for you, then.
[18:57] <PaddyLandau> I have no objection if it helps your workflow.
[18:57] <hannie> Now I function as an intermediate
[18:57] <hannie> ok, I will send an email on this
[18:57] <hannie> for the next version
[18:58] <jimc> I think this is a great idea!
[18:58] <hannie> godbyk, before you get confused, next item is create wiki page ;)
[18:58] <jimc> Could we get U1 to comp us a 10GB space? (*grin*)
[18:58] <godbyk> hannie: I like to reword them to confuse you. :-P
[18:58] <ajmontag> I have to leave, its nice to have such a good turn out! Thanks for all your work, editors!
[18:58] <godbyk> #topic Style guide
[18:58] <hannie> lol
[18:58] <godbyk> Thanks for coming, ajmontag.
[18:59] <hannie> bye ajmontag thank you for being with us
[18:59] <PaddyLandau> Bye ajmontag
[18:59] <jimc> Style guide...GO
[18:59] <kereltis> cya ajmontag
[18:59] <carsten> Bye ajmontag
[18:59] <c7p> cya
[18:59] <hannie> https://wiki.ubuntu.com/ubuntu-manual
[19:00] <kereltis> very nice!
[19:00] <hannie> I am thinking of using a wiki page where everyone can add remarks, rules etc. See my link
[19:00]  * godbyk is scared to look at the ancient wiki. 
[19:00] <c7p> :P
[19:01] <hannie> we can wipe out what's there and use it for other things
[19:01] <godbyk> I think that the good part of using a wiki for the style guide stuff is that it's easy for everyone to access.  (Easier than downloading a PDF, at least.)
[19:01] <godbyk> A bad point is that anyone can change it so we may lose consistency.
[19:01] <hannie> Example: our translation team uses a wiki vocabulary where everyone can add words
[19:02] <PaddyLandau> hannie, what sort of remarks? I notice in the agenda that you mention things like tags, panels, and so forth. But aren't they all already in the style guide?
[19:02] <jimc> I agree with godbyk...more dynamic...seemingly less work in the end.
[19:02] <kereltis> sticking with the LTS latest LTS release is probably a good thing though so it's not really that old :)
[19:02] <hannie> PaddyLandau, I gave the \menu example because in the previous version we used \application{Dash}
[19:02] <jimc> I also agree with godbyk (again)...welcome to the world of WIKIs!
[19:03] <PaddyLandau> Right, so it would list things that you may not be aware of that have changed in the guide?
[19:03] <PaddyLandau> And other things, too, I realise.
[19:03] <hannie> Wiki's have advantages and disadvantages
[19:03] <godbyk> Our current style guide is at <http://files.ubuntu-manual.org/style-guide.pdf>
[19:03] <PaddyLandau> godbyk: Yes, I refer to that quite often.
[19:03] <godbyk> I update it occasionally, but haven't been keeping up with it as much as I'd like.
[19:04] <godbyk> I'm definitely open to suggestions with regard to the style guide.
[19:04] <hannie> I do not mean to put the style guide on a wiki. I talk about general rules (grammar, spelling, etc.)
[19:04] <PaddyLandau> And with a Wiki, it would take some of the pressure of you?
[19:04] <godbyk> I most recently added a Word List chapter that shows the proper spelling and formatting of some terms. I plan on expanding this greatly as I edit the 12.04 manual.
[19:04] <carsten> godbyk, one point for the pdf style guide: It doesnt
[19:04] <carsten> ... need so much empty pages. It is no book to print, or?
[19:05] <hannie> ok, my suggestion for a wiki page is not such a good one. NP:)
[19:05] <godbyk> carsten: Ah, you're probably right. I'm just using the same template as we're using for the manual itself.
[19:05] <godbyk> hannie: We could add some of that to the style guide, too.
[19:06] <jimc> Hmm...I'm leaning more toward the style guide being more "controlled" than what is offered in a wiki environment.
[19:06] <carsten> I think, its a working document, where you want to see a lot information with one view
[19:06] <godbyk> hannie: Though I think it may be easier to point to existing sources for general grammar rules.  (There are too many for us to cover alone.)
[19:06] <godbyk> The Ubuntu Docs wiki has a style guide with some grammar remarks (though not nearly exhaustive).
[19:06] <hannie> right. One more remark on this:
[19:06] <godbyk> jimc: I agree with you there.
[19:07] <hannie> we discussed on the list when to add the tag \application and when not. But I cannot find it in the archive
[19:07] <godbyk> Here's the docs team style guide: https://wiki.ubuntu.com/DocumentationTeam/StyleGuide
[19:07] <hannie> Therefore I was thinking of putting things we discussed on a wiki page
[19:07] <hannie> or in the style guide (even better)
[19:08] <TonyP> The style guide seems wrong about \application
[19:08] <hannie> TonyP, we discussed in on the mailing list
[19:08] <carsten> And for the wiki version of the style guide: You can get emails from the system, if the page is changed, so you can easily follow any modification.
[19:08] <hannie> but I forgot what we decided
[19:08] <godbyk> TonyP: In what way?
[19:09]  * godbyk pulls up his copy of the style guide.
[19:09] <hannie> godbyk, in Browsing the web I see a lot of \application{Dash}
[19:09] <hannie> and \aplication{Launcher}
[19:10] <hannie> *p
[19:10] <TonyP> What should it do?
[19:10] <hannie> \menu
[19:10] <godbyk> hannie: I noticed that the other day, too, but haven't fixed it yet. Since those aren't stand-alone applications, I don't think they should be tagged as such.
[19:10] <hannie> No, we discussed that on the mailing list like I said
[19:10] <godbyk> TonyP: At the moment, it doesn't do anything. It used to mark the text in bold and add an entry to the index automatically.
[19:11] <hannie> godbyk, is tag \application no longer an entry to the index?
[19:11] <godbyk> hannie: It isn't at the moment, though we can add that back easily enough.
[19:12] <hannie> the disadvantage is that if you use it all the time the index gets clogged
[19:12] <godbyk> hannie: Here's an old thread about \application: https://lists.launchpad.net/ubuntu-manual/msg02835.html
[19:12] <godbyk> We discussed it more recently, too. Lemme find the thread.
[19:13] <hannie> Yes, I remember we discussed \index with MarioB
[19:13] <godbyk> Okay, it looks like the more recent thread isn't in the archives yet.
[19:13] <hannie> Again, when we decide something via the list it should be noted somewhere
[19:14] <TonyP> The Style Guide says: The names of applications should be typeset with the
[19:14] <TonyP> \application command. is will add the application to the index auto-
[19:14] <TonyP> matically.
[19:14] <godbyk> It has the subject "Authors/editors chapter 2" and is dated May 23.
[19:14] <godbyk> We discussed \application and \menu with jimc.
[19:15] <hannie> Question: if the word Nautilus is used many times, should it always get the tag \applicatio?
[19:15] <hannie> *n
[19:15] <godbyk> TonyP: That used to be true. Now it's still true except for the index bit. (Though that may change soon, too. I'll have to try it and see what we didn't like about it.)
[19:15] <PaddyLandau> Here we are: https://lists.launchpad.net/ubuntu-manual/msg03085.html
[19:16] <godbyk> PaddyLandau: Thanks!
[19:16] <godbyk> So the message that I wrote in that thread was <https://lists.launchpad.net/ubuntu-manual/msg03093.html>
[19:17] <godbyk> Something else we need to decide on is when/how to capitalize dash, launcher, etc.
[19:17] <godbyk> The official Ubuntu docs seems to be inconsistent there, so we'll have to decide for ourselves how to handle this issue.
[19:17] <hannie> godbyk, you took the words right out of my mouth ;)
[19:18] <jimc> So...Dash, Launcher are /menu, Nautilus is /application, right?
[19:18] <hannie> Dash or dash, Launcher or launcher is what I wanted to ask
[19:18] <PaddyLandau> I agree that \application is only for what the general user would perceive as a program, and not for the dash or launcher.
[19:18] <jimc> ...sorry, slashes the other way.
[19:18] <PaddyLandau> I would always use capital letters for Dash and Launcher, as they are specific names for specific items quite unique to Ubuntu.
[19:18] <jimc> I agree with PaddyLandau
[19:18] <TonyP> Me too
[19:19] <godbyk> jimc: I would use \menu for dash and launcher.
[19:19] <hannie> +1
[19:19] <PaddyLandau> Agreed.
[19:19] <godbyk> jimc: \menu is only for pull-down menus like File, Edit, View.
[19:19] <godbyk> jimc: And menu items like Open..., Save, Print..., Copy, etc.
[19:19] <godbyk> jimc: You can also use \menu for menu items under the indicator menus.
[19:20] <c7p> i don't have strong opinion here
[19:20] <PaddyLandau> If not \menu for Dash or Launcher, then what?
[19:20] <hannie> godbyk, in the previous discussion I thought it was decided to use \menu{Dash}
[19:20] <godbyk> PaddyLandau: They don't necessarily need a tag.
[19:20] <PaddyLandau> OK
[19:20] <c7p> doesn't emph works ?
[19:21] <PaddyLandau> I would use \emph only when introducing the words Dash or Launcher, otherwise it becomes a visual distraction.
[19:21] <godbyk> c7p: \emph should only be used for \emph{adding emphesis} and not for formatting text (like names of things).
[19:21] <hannie> So, conclusion: no tag for Dash and Launcher?
[19:21] <c7p> ah ok
[19:21] <PaddyLandau> OK
[19:21] <godbyk> For now, I'd say no tag for Dash or Launcher.
[19:21] <godbyk> Next question: Should we capitalize Dash/dash and Launcher/launcher?
[19:22] <jimc> I'm good with no tags for Dash and Launcher, although it does require us to redit our sections.
[19:22] <hannie> ok. How do we let those who are not present know?
[19:22] <jimc> mailing-list
[19:22] <godbyk> jimc: I can fix those pretty quickly. It's not a big deal.
[19:22] <godbyk> I'll add it to the style guide and we can send a message to the mailing list as well.
[19:22] <hannie> problem with m/list is that it comes and goes
[19:22] <jimc> godbyk, ok.
[19:23] <hannie> godbyk, good idea
[19:23] <PaddyLandau> godbyk: "Should we capitalize Dash/dash and Launcher/launcher?" I am of the opinion that these are proper names, because they are specific items unique to Ubuntu.
[19:23] <godbyk> hannie: That's what the new Word List chapter is for in the style guide. To track these little details. :)
[19:23] <jimc> hannie, then do the mailing list, edit the style guide
[19:23] <hannie> I am totally happy with that solution ;)
[19:24] <jimc> I agree with PaddyLandau, it should be Dash and Launcher
[19:24] <carsten> +1
[19:24] <TonyP> +1
[19:24] <hannie> godbyk, I think we have said enough about editing
[19:24] <godbyk> Sounds good.  I'll add the capitalization note to the style guide, too, then.
[19:25] <hannie> please do
[19:25] <godbyk> As you're editing, if you encounter inconsistencies or have questions about how to format something, please email me and I'll help you out.
[19:25] <godbyk> That'll also prompt me to add a note about it to the style guide so we can keep track of these things.
[19:26] <godbyk> Are there any other questions at the moment about style, formatting, etc.?
[19:26] <jimc> Do we want to talk briefly about indexing?
[19:26] <godbyk> If not, we'll move to the next topic.
[19:26] <godbyk> #topic Indexing the manual
[19:27] <hannie> jimc, it is an item on the agenda
[19:27] <godbyk> TonyP: Are you our indexer?
[19:27] <TonyP> No, I just want to know about it
[19:27] <hannie> it says: benonsoftware
[19:27] <godbyk> Our manual's index hasn't been that great in the past and it'd be nice to make it useful.
[19:27] <godbyk> TonyP: Okay, thanks.
[19:28] <hannie> And didn't Mario do it the last time?
[19:28] <godbyk> The way indexing works in LaTeX is that you add \index macros in the text where you refer to something that should appear in the index.
[19:28] <c7p> he did a try at the last minute
[19:28] <godbyk> The syntax for the \index macro is a bit complicated when you first discover it.
[19:28] <jimc> I completely agree with godbyk.  This is a key area (from the user's perspective) that needs to be addressed.
[19:29] <hannie> c7p, do you know who benonsoftware is and if he is doing glossary and index?
[19:29] <godbyk> Since indexing requires that we edit each of the .tex files in the manual to add \index commands, I generally recommend waiting until the other editors have finished their work.
[19:29] <jimc> godbyk, there are enough examples that if people just tried it a few times, they'd see the results.  That's how I learned.
[19:29] <c7p> nope
[19:29] <c7p> but he is on channel !
[19:29] <godbyk> This means that the text shouldn't change any more and that the indexer won't cause bzr conflicts.
[19:29] <TonyP> I am editing the Ubuntu One section and there are no index entries for it
[19:29] <jimc> I've been adding index entries as I've been going along...
[19:30] <hannie> c7p grey
[19:30] <jimc> ...mostly based on the \subsection headings.
[19:30] <godbyk> I'll contact benonsoftware to see if he's still interested in indexing the manual and work with him on the \index syntax and how to go about indexing.
[19:30] <jimc> It's very easy to do as editors.
[19:30] <c7p> good
[19:30] <godbyk> If anyone else is interested in indexing their own sections/chapters, let me know and I'll help you out.
[19:30] <godbyk> I need to write up some notes on it and add them to the style guide.
[19:31] <PaddyLandau> godbyk: Please do write it up.
[19:31] <jimc> I still think there needs to be a point person on indexing and glossary to ensure document consistency.
[19:31] <godbyk> Indexing isn't too difficult. The biggest problems are: (1) figuring out the \index syntax, and (2) knowing what's good to add to the index and how to phrase it.
[19:31] <godbyk> jimc: I agree.
[19:32] <godbyk> Per hannie's spreadsheet, benonsoftware said he'd handle the index and glossary.
[19:32] <godbyk> So we'll ping him and see if he's still up for that.
[19:32] <jimc> godbyk, probably one of the last "steps" before publication.
[19:32] <c7p> anyone here interested in indexing ?
[19:32] <godbyk> jimc: Definitely.
[19:32] <jimc> I will.
[19:32] <jimc> When is the due date for the manual?
[19:33] <PaddyLandau> 15th.
[19:33] <jimc> the FINAL version
[19:33] <godbyk> jimc: 30 June is when we'll release the final PDF and printed editions.
[19:33] <hannie> June 30
[19:34] <jimc> My opinion only, the indexing and glossary work should be done at a time when the manual is "frozen"
[19:35] <kereltis> jimc, good point
[19:35] <TonyP> Can I suggest...
[19:35] <hannie> godbyk, I think we could be a week earlier since there should not be a week between end of editing and crocodoc
[19:35] <godbyk> hannie: True. We'll see how it goes.
[19:35] <jimc> crocodoc?
[19:35] <godbyk> jimc: crocodoc is a website that allows online annotation of PDFs.
[19:36] <godbyk> jimc: It's handy for having lots of people proofread your PDF.
[19:36] <TonyP> Anyone can put in \index entries subject to so overall edit/review
[19:36] <jimc> godbyk, ahh, ok.  Newbie here, remember!
[19:36] <godbyk> jimc: See <ubuntu-manual.org/proofread/gswu1110/en> for example.
[19:36] <hannie> I thought it very handy in the previous version (crocodoc)
[19:36] <godbyk> jimc: No problem!
[19:37] <godbyk> TonyP: Yes, I think that's fine. As long as people don't get *too* carried away with it. :)
[19:37] <godbyk> I sneaked in an agenda item:
[19:37] <jimc> Sorry to be anal about this, but users will more likely than not use the index to find how to do something...and will be less likely to read the manual cover to cover.  Therefore, the index (and glossary) is crucial to the success of the user and the utility of our work on this project.
[19:37] <godbyk> #topic Screenshot editors
[19:38] <godbyk> We've discussed this a bit previously and someone volunteered (I don't recall who). But I think we should have one or two screenshot editors to take/retake all the screenshots for the entire manual.
[19:38] <TonyP> jimc: I agree
[19:38] <godbyk> This will help ensure consistency.
[19:38] <c7p> me too
[19:38] <hannie> jimc, I agree on the need for a very good index
[19:38] <godbyk> jimc: I agree completely. That's why I'd like to see the index improved greatly.
[19:38] <jimc> I agree with the "screenshot" team
[19:39] <jimc> godbyk, count me in....however I can help, I will.
[19:39] <kereltis> agree with the "screenshot" team
[19:39] <c7p> +1
[19:39] <hannie> godbyk, I want to do screenshot editing as well
[19:40] <godbyk> Okay.
[19:40] <hannie> ah, 2 is enough: c7p and kereltis
[19:40] <c7p> many of the screenshots have to be recaptured
[19:40] <godbyk> Excellent.
[19:40] <godbyk> Can you two coordinate between yourselves and retake all of the screenshots for the manual?
[19:40] <c7p> i see that some of them have a red login button, others have been captured with a large resolutons etc
[19:40] <godbyk> There are some screenshots that are still missing, too.
[19:41] <c7p> that too
[19:41] <godbyk> c7p: Right. We need to make sure that all the screenshots are taken at the same resolution.
[19:41] <jimc> ...another Style Guide entry:  Screnshot resolution!
[19:41] <c7p> there are also some great screenshots, so i guess they dont have to retake all the screenshots
[19:41] <jimc> What defines great?
[19:42] <PaddyLandau> Also sizes of screen-shots; there would need to be a maximum size to fit in a readable way.
[19:42] <godbyk> With the default desktop and settings. Preferably with the same username, even.
[19:42] <c7p> captured according to instructions + good looking on the pdf
[19:42] <godbyk> c7p: Possibly. Though it's probably best to retake them anyway just in case.
[19:42] <c7p> ok
[19:42] <jimc> c7p, the first one requirement is subjective, the 2nd is objective
[19:42] <hannie> godbyk, can you put my screenshot instructions in the style guide too?
[19:42] <c7p> but in any case start from the problematic screenshots
[19:42] <godbyk> hannie: Yep!
[19:43] <hannie> thanks
[19:43] <c7p> jimc: nope, 2nd isn't objective, i mean how clear a screenshot is
[19:43] <jimc> c7p, I ask only to help the team determine what needs to be redone and what is acceptable...retaking ALL the screenshots seems to be a LOT of work.
[19:43] <carsten> Just for interest: What is with this quickshot program?
[19:43] <c7p> i agree with you
[19:43] <godbyk> carsten: It's dead in the water at the moment.
[19:44] <godbyk> carsten: We don't have anyone developing it.
[19:44] <carsten> I thought it was desinged for this purpose?
[19:44] <carsten> ah ok
[19:44] <c7p> guys i g2g
[19:44] <c7p> i'll check the logs later
[19:44] <hannie> cya c7p
[19:44] <carsten> bye c7p
[19:44] <PaddyLandau> Goodbye
[19:44] <godbyk> Okay, see you later, c7p!
[19:44] <TonyP> bye c7p
[19:44] <kereltis> cya c7p
[19:45] <godbyk> I think that settles the screenshot editors topic, then.
[19:45] <godbyk> #topic Any other questions or business?
[19:45] <godbyk> Does anyone have any other questions or issues to raise?
[19:45] <hannie> I have no questions
[19:45] <PaddyLandau> Not from me.
[19:45] <kereltis> not from me
[19:46] <jimc> Lots to digest, but I think I'm good (if not, you'll see me in the mailing-list!)
[19:46] <godbyk> Okay, sounds good guys.
[19:46] <godbyk> Keep up the great work!
[19:46] <carsten> One
[19:46] <TonyP> OK with me
[19:46] <jimc> Would it be good to quickly revie w the upcoming due dates>
[19:46] <godbyk> If you have any questions during the week, feel free to ping us here in the IRC channel or on the mailing list.
[19:46] <carsten> When starts translation the manual?
[19:46] <godbyk> jimc: Sure.
[19:46] <hannie> Thanks all for the work you do for our manual
[19:46] <godbyk> Upcoming milestones:
[19:46] <godbyk> June 15 – Editors have edited and proofread content.
[19:46] <godbyk> June 22 – Release a draft for public comment and proofreading for one week.  Incorporate changes as they are suggested.
[19:46] <godbyk> June 27 – Final draft is complete and all last-minute changes have been made.
[19:46] <godbyk> June 30 – The final PDF is released on our website and printed copies can be purchased via lulu.com.
[19:47] <godbyk> carsten: The translations won't start until after we've published the final PDF.
[19:47] <carsten> ok
[19:47] <godbyk> carsten: We have to wait until all the .tex files are finalized before we can upload the translation template file.
[19:47] <jimc> When should final indexing/glossary begin/end?
[19:48] <godbyk> hannie: We may use that June 15–22 week to update the screenshots, index, and glossary. We'll have to see how things go.
[19:48] <jimc> OK
[19:48] <hannie> godbyk, again a good idea
[19:49] <PaddyLandau> I have to go now. Have a good night or day wherever you are in the world :)
[19:49] <godbyk> G'night, PaddyLandau.
[19:49] <hannie> thanks for coming PaddyLandau see you
[19:49] <kereltis> cya PaddyLandau
[19:49] <carsten> bye Paddy
[19:49] <godbyk> If there are no other questions or issues, I'll wrap this up.
[19:49] <jimc> Cheers, PaddyLandau
[19:49] <godbyk> #endmeeting
[19:49] <meetingology> Meeting ended Sat Jun  9 19:49:34 2012 UTC.
[19:49] <meetingology> Minutes (wiki):        http://ubottu.com/meetingology/logs/ubuntu-manual/2012/ubuntu-manual.2012-06-09-18.04.moin.txt
[19:49] <meetingology> Minutes (html):        http://ubottu.com/meetingology/logs/ubuntu-manual/2012/ubuntu-manual.2012-06-09-18.04.html
[19:49] <hannie> godbyk, thank you for being chair
[19:49] <godbyk> I'm often on IRC, so feel free to ping me if you have questions.
[19:50] <godbyk> The mailing list also works well.
[19:50] <godbyk> hannie: np
[19:50] <hannie> Have a good weekend all of you
[19:50] <godbyk> I'll write up the meeting minutes and send them to the mailing list later today or tomorrow.
[19:50] <kereltis> Thanks for coming everyone and for the hard work! I'll be in the mailing list, have a great weekend all!
[19:50] <godbyk> I'll also update the style guide this weekend.
[19:50] <carsten> thanks, same to you
[19:50] <TonyP> bye all
[19:51] <jimc> Thanks everyone!  Looking forward to the final product!
[19:51] <carsten> bye all
[19:52] <godbyk> Goodbye, carsten.
[19:54] <godbyk> I'm going to head out, too. I'll be back in a few hours.