[12:13] <theCore> oh, one from my town :)
[12:14] <LaserJock> yep
[12:22] <theCore> hmm ... the membership process does something pretty good, it motivate peoples by giving them a clear objective
[12:23] <LaserJock> yeah, and it also builds community spirit
[03:06] <LaserJock> hi theCore and Unfrgiven 
[03:07] <LaserJock> you guys might be interested to know that I got a print copy of the Packaging Guide
[03:09] <theCore> LaserJock: a printed copy? 
[03:10] <LaserJock> theCore: yeah. we are making the doc team guides available from lulu.com
[03:10] <LaserJock> theCore: and I got the first test copy a couple days ago
[03:17] <theCore> LaserJock: are they selling it yet?
[03:17] <LaserJock> theCore: not yet, we are still getting the cover and tweaking done
[03:18] <theCore> LaserJock: do they have artists for the cover design? or we doing it?
[03:19] <LaserJock> well Madpilot did a good one but the artwork team is also working on something I think
[03:24] <theCore> LaserJock: ok, then I'm on it :)
[03:25] <theCore> A4, 300dpi?
[03:27] <LaserJock> well, I think we probably have it nailed down now, but it is crown quarto in size
[03:28] <theCore> crown quarto?
[03:30] <LaserJock> yeah, I can't remember what it is exactly
[03:31] <LaserJock> theCore: there is quite a discussion on the ML
[03:38] <theCore> oh, crown quarto is C4
[03:38] <theCore> which is 7" x 10"
[03:41] <theCore> LaserJock: what is the thread name?
[03:41] <LaserJock> lulu book or something like that
[03:44] <LaserJock> heah, there's Madpilot now
[03:44] <Madpilot> hi all
[03:45] <Madpilot> was my name being taken in vain? ;)
[03:48] <LaserJock> no
[03:48] <LaserJock> theCore was just wondering about the book cover
[06:08] <hybrid> howdy
[06:10] <LaserJock> hi hybrid 
[06:10] <hybrid> i am interested in joining the team.
[06:11] <hybrid> is there a process i need to follow?
[06:11] <hybrid> (im still riding through the wiki )
[06:11] <LaserJock> just a sec
[06:13] <LaserJock> hybrid: ok, so what are you interested in?
[06:13] <hybrid> LaserJock: i am willing to go with about anything, but i am a PPC user if that helps any
[06:14] <hybrid> and I like Xubuntu or Ubuntu over Kubuntu :)
[06:14] <LaserJock> well, are you interested in wiki pages or online documentation? wiki.ubuntu.com/DocumentationTeam/Projects has a list of some projects the doc team is working on
[06:15] <LaserJock> wiki.ubuntu.com/DocumenationTeam/GettingStarted might help
[06:16] <hybrid> ok ty
[06:17] <LaserJock> if you are more into wiki work then https://wiki.ubuntu.com/WikiTeam and https://wiki.ubuntu.com/WikiToDo should help
[06:18] <hybrid> yeah i think i like the wiki team
[06:19] <LaserJock> it is a little easier to get started working on. The official docs are written in XML and are stored in a svn repo
[06:19] <hybrid> yeah i will go with the Wiki, i havent used XML in much time
[06:22] <hybrid> ty LaserJock anything else i need to do?
[06:27] <LaserJock> hybrid: not particularly, just work and make sure you keep the ubuntu-doc mailing list fairly informed about what your doing
[06:28] <LaserJock> if you have questions ask here or on the list
[06:29] <hybrid> ok ty much Laser_away 
[07:59] <LaserJock> mdke: checkout http://www.chem.unr.edu/~mantha/ubuntu/lulu/
[09:31] <mdke> Laser_away: I can't see the latter 3 files, but the first two look exactly as they do on the electronic pdf, which is good news. Thanks for doing that
[09:31] <Madpilot> hi mdke 
[09:31] <mdke> hiya Madpilot 
[09:31] <mdke> sorry I can't stay long, am late for work
[09:32] <Madpilot> ouch, those admon graphics really are pixelated, aren't they?
[09:33] <Madpilot> I'll redo them later this week for proper 300+dpi
[09:42] <mdke> Madpilot: I'm not convinced its related to their resolution.
[09:42] <mdke> but it might be, I suppose
[09:43] <Madpilot> mdke, could well be - although even 90dpit web-resolution images should be a bit cleaner than those ones when printed
[09:44] <mdke> i think they are getting resized
[09:44] <mdke> not sure tho
[09:44] <mdke> gtg
[09:44] <Madpilot> later
[03:41] <jjesse> mgalvin: are you creating a flight7 page?
[03:41] <jsgotangco> he might not be aware of a flight 7 being cooked even
[03:42] <mgalvin> jjesse: flight7!? is there such a thing?
[03:42] <jsgotangco> see :)
[03:42] <mgalvin> uh :-/
[03:42] <mgalvin> :)
[03:42] <jsgotangco> mgalvin: yeah probably later or tomorrow
[03:42] <mgalvin> ok, um...
[03:42] <jjesse> [09:40]  <Lure> jjesse: Flight 7 will be tommorow's daily if everything goes well
[03:42] <jjesse> [09:42]  <Riddell> jjesse: yes, tomorrow
[03:42] <jsgotangco> there was a huge zope upload too
[03:42] <jsgotangco> as well as some kde deps
[03:42] <mgalvin> i can try and whip something together
[03:43] <mgalvin> i will start on it shortly
[03:43] <jjesse> looks like i got a task for today :)
[03:43] <LaserJock> mgalvin: did you do the website page for the Beta release?
[03:43] <mgalvin> man, i am off on other things for a day or two and so many things happen
[03:43] <mgalvin> LaserJock: yea
[03:44] <mgalvin> and all the other flights
[03:44] <LaserJock> mgalvin: what is the URL, somebody mentioned a typo on the forums
[03:44] <jjesse> and i rushed KubuntuDapperBeta
[03:44] <mgalvin> (although many other people help too)
[03:44] <jjesse> for ubuntu its no longer a wiki page
[03:44] <mgalvin> LaserJock: is at http://www.ubuntu.com/testing/dapperbeta
[03:45] <mgalvin> what is the typo, i will have to fix it
[03:46] <mgalvin> do you guys feel there is enough desktop related changes to warrent a full page... it seems to be mostly just bug fixes as far as i can tell (still need to look at the upload logs)
[03:47] <LaserJock> on the Note on the the top it should be "a Beta release" instead of "an Beta release"
[03:47] <jjesse> just bug fixes, not a full page
[03:47] <jsgotangco> mgalvin: you can just put 1 sentence for the flight 7 page
[03:47] <jsgotangco> "Surprise!"
[03:47] <mgalvin> :)
[03:48] <mgalvin> with a picture of squashed bugs :)
[03:48] <mgalvin> that would be gross
[03:48] <LaserJock> yeah, but it would get to the point
[03:50] <mgalvin> LaserJock: the beta page is fixed
[03:53] <LaserJock> darn it, that blows the whole point to my post
[03:57] <LaserJock> I was trying to tell the poster that they shouldn't put typo fixes on the forums as people won't see them
[03:57] <mgalvin> LaserJock: which post is that?
[03:57] <LaserJock> http://www.ubuntuforums.org/showthread.php?t=169485
[03:57] <LaserJock> oh well ;-)
[04:00] <mgalvin> LaserJock: well, i didn't find it on the forum so you are still right :)
[04:01] <LaserJock> yeah, but I was enabling bad behavior
[04:31] <trappist> what do you guys think of a 'troubleshooting guide' dedicated to when things don't go off as planned/documented?
[04:32] <LaserJock> trappist: I think many people would find it helpful, but I think it would extrodinarly hard to do write well
[04:33] <trappist> LaserJock: I'm not sure I agree with the last part.  we could produce a doc that covers some of the biggies, like X won't start, I can't login, I can't sudo, etc., then respond to users who want to see this or that added.
[04:33] <LaserJock> yeah, it would depend on how you do it
[04:33] <LaserJock> I would think it would be very hard to cover enough ground
[04:33] <jsgotangco> it would be pretty advanced for most users though
[04:33] <jsgotangco> or something like a troubleshooting guide included with appliances? :)
[04:34] <LaserJock> many, many things can go wrong with X
[04:34] <jsgotangco> yeah
[04:34] <jsgotangco> it can either be kernel or x
[04:34] <jsgotangco> most of the time
[04:34] <trappist> LaserJock: it wouldn't have to cover how to fix every situation - its goal would be to enable the user to find out what went wrong.  how to use strace, gdb, log files, increasing log verbosity in various apps, things like that.
[04:34] <LaserJock> But in the sense of having a guide to debugging and bug reporting, I think that is a cool idea
[04:35] <trappist> once a user knows what went wrong, he may or may not be able to fix it, but he's definitely better equipped to ask for support
[04:35] <LaserJock> I talked to sfflaw (the new Canonical QA guy) about that a bit yesterday
[04:35] <trappist> or to file a bug report :)
[04:36] <LaserJock> I was thinking of expanding the Packaging Guides treatment of bugs to include more of what you are talking about
[04:36] <LaserJock> but maybe splitting it out into a seperate doc would be better
[04:36] <jsgotangco> LaserJock: sure but don't expect majority of people to do a backtrace on an app that doesn't work for them heh
[04:36] <jeffsch> trappist: maybe you can mine the forums to see what troubles people are having
[04:37] <trappist> I do think troubleshooting deserves its own guide, but maybe it should be generic?  like, it should provide some overall strategies for approaching various problems and cover the use of some tools, locations of logs, etc., and leave individual apps to their respective guides?
[04:37] <LaserJock> jsgotangco: no, this is under my push for getting docs for people more towards the advanced side
[04:37] <trappist> jeffsch: that's a great idea.  I spend a lot of time on #(k)ubuntu too, so I see a lot of what breaks.  mostly sound :)
[04:39] <jeffsch> jsgotangco: yeah, i filed a bug about a year ago on some app in ubuntu (i forget which one), and the response was "please recompile with debug switches, or I'll cancel the bug"
[04:40] <jeffsch> the bug eventually got cancelled
[04:41] <trappist> it's been brought up that it would be helpful to have more -dbg packages in the repos.  I was actually thinking of a dbg repo.
[04:41] <trappist> bandwidth was cited as a problem.
[04:42] <trappist> and packaging time.
[04:42] <LaserJock> trappist: more -dbg packages are being added
[04:42] <trappist> ossum
[04:43] <LaserJock> dholbach and seb128 have been adding them for the most frequently bugged gnome packages
[04:43] <trappist> that rocks.  I'd sure love to see the same on the kde side, especially with kontact, kmail and konqueror
[04:43] <trappist> (some of those may have dbg packages, I'm not sure)
[04:44] <trappist> looks like no.
[04:46] <LaserJock> well, we just have sooo many bugs to triage and work on that it is difficult to have to chase down every little thing
[04:46] <LaserJock> that said, reporting a bug should be a fairly straightfoward and easy task for users
[04:53] <LaserJock> trappist: anyway, I'd recommend talking with sfflaw about that doc
[04:54] <Hoobly> hi.  anyone here?
[04:54] <LaserJock> sure
[04:55] <Hoobly> I was just in the Kubuntu channel and just found this one
[04:55] <jsgotangco> hi
[04:55] <LaserJock> Hoobly: heh, there are a lot of channels
[04:55] <Hoobly> I would like to print the Kubuntu Quick Guide for distro with machines our Non-Profit gives to families without computers.  Is there a PDF available so I don't have to print every page one at a time?
[04:56] <Hoobly> Or how can I get the documentation on CD?
[05:00] <jsgotangco> Hoobly: do you mean the one for Kubuntu 5.10?
[05:02] <trappist> LaserJock: who's that and where would I find him?
[05:03] <LaserJock> sfflaw is the new QA guy that Canonical hired, he is in #ubuntu-bugs
[05:04] <trappist> ah cool
[05:07] <Hoobly> jsgotangco: yes
[05:08] <mdke> we can make you one. That sounds like a really cool initiative
[05:10] <mdke> Hoobly: can you email ubuntu-doc@lists.ubuntu.com about it, and I'll make sure I send you a pdf.
[05:13] <jsgotangco> the one in trunk has changed compared to the one in the distro so you'll have to dig for past revisions i guess
[05:14] <jsgotangco> (for 5.10)
[05:15] <mdke> well, it's in the distro.
[05:15] <mdke> hopefully making the pdf will work
[05:15] <Hoobly> mdke: sent
[05:16] <jsgotangco> mdke: kubuntu has the xml too? i thought it was already processed as khtml
[05:17] <jsgotangco> it should work, i did that thing and tested in yelp heh
[05:18] <mdke> jsgotangco: it's in the source for kubuntu-docs
[05:18] <mdke> Hoobly: got it.
[05:23] <jsgotangco> Hoobly: interesting place your work for
[05:27] <mdke> Hoobly: size A4 pages?
[05:34] <Hoobly> no.  Letter
[05:35] <Hoobly> mdke: Letter
[05:36] <mdke> Hoobly: how big is that (cm or inches)
[05:37] <Hoobly> 8.5 inches by 11 inches
[05:39] <LaserJock> mdke: lol
[05:39] <mdke> Hoobly: Ive tried a preliminary build of a pdf but havent got it to work, there is some kind of a crash due to low memory. I think it might be due to the high quantity of images in the quickguide, so I will investigate and let you know by email.
[05:40] <jsgotangco> mdke: can you do me a favor and pngcrush those images they're quite big and that is probably causing the choking if ever
[05:42] <mdke> good idea
[05:44] <mdke> how does it work?
[05:44] <Hoobly> thank you.  let me know
[05:45] <LaserJock> yeah, that thread on -devel about the recompressing .pngs might be useful for the repo
[05:45] <mdke> http://pastebin.com/696316
[05:46] <jsgotangco> mdke: its basically pngcrush original.name new.name but i guess you can do regex on it to do it in one shot (i didnt really test it)
[05:47] <jsgotangco> hmmm
[05:47] <jsgotangco> its borked
[05:47] <jsgotangco> dapper?
[05:47] <mdke> y
[05:47] <jsgotangco> i thought this was fixed already
[05:50] <jsgotangco> try pngnq
[05:51] <jsgotangco> i got to reduce it 50%
[05:56] <mdke> k
[06:15] <jsgotangco> later guys
[06:16] <jsgotangco> good night
[07:39] <LaserJock> mdke: around?
[08:02] <mdke> LaserJock: hi
[08:03] <LaserJock> mdke: you couldn't see some of the pics?
[08:05] <mdke> LaserJock: I saw the first two, not the other 3. It's strange that recently in epiphany I haven't been able to download some files
[08:06] <LaserJock> mdke: hmm, I don't know why you couldn't see them
[08:06] <LaserJock> they show up fine for me
[08:06] <mdke> a bug my side, I guess.
[08:06] <mdke> in epiphany
[08:08] <LaserJock> no firefox? :-)
[08:09] <LaserJock> mdke: one thing that was interesting to me was how variable lists are displayed
[08:09] <mdke> lemme fire up firefox. what was the url?
[08:10] <LaserJock> http://chem.unr.edu/~mantha/ubuntu/lulu/
[08:16] <mdke> LaserJock: you don't like variable lists, or you do?
[08:19] <LaserJock> mdke: I don't like the way it is done on the pdf, I like the html though
[08:19] <mdke> LaserJock: ok, I'm sure we can tweak that
[08:20] <LaserJock> I don't know how much other people use them
[08:21] <LaserJock> I use them only 1 or 2 times
[09:30] <LaserJock> mdke: really? is that mgalvin ?
[09:30] <mdke> Surak: ping mgalvin about it. Although I think that it's intentional
[09:30] <Burgwork> LaserJock, congrats on your edubuntu council election
[09:30] <mdke> LaserJock: wow, dude.
[09:31] <LaserJock> Burgwork: where did you see that?
[09:31] <mgalvin> LaserJock: indeed, congrats!!!
[09:31] <Surak> mdke: intentional? as far as i recall, beta 1 has the bad habit of wiping partitions
[09:31] <LaserJock> mgalvin: thanks, I hope I can be of service to Edubuntu
[09:32] <Burgwork> LaserJock, ubuntu-annouce, I think
[09:32] <Surak> mgalvin, the http://www.ubuntu.com/testing page says nothing about dapper beta 2. Shouldn't it be there?
[09:32] <LaserJock> Burgwork: yikes, first time I've ever made u-a :-)
[09:32] <mdke> it wasn't on -announce, I don't think
[09:32] <mdke> I didn't see anything about it
[09:33] <mdke> good news LaserJock 
[09:33] <mgalvin> Surak: beta 2 was released rather quickly after beta 1... i did not have a chance to make a new page for it... 
[09:33] <mdke> i didn't even know you worked on edubuntu 
[09:33] <mgalvin> Surak: u.c/testing just list link to the releases there are tours for
[09:33] <mdke> mgalvin: i would think one page is good enough to apply to both beta releases
[09:34] <mgalvin> although, i guess we could add a link and just point it at beta1 (with a note of course)
[09:34] <mgalvin> mkde: me too
[09:34] <LaserJock> mdke: I don't much, but I'm working on it ;-) they wanted somebody with university experience that was already an Ubuntu member
[09:34] <mdke> who else is on the council? highvoltage, presumably?
[09:35] <Burgwork>  Oliver Garwert - ogra  * Jane Weideman - JaneW * Jerome Jotangco - jsgotangco  * Jonathan Cater - highvoltage  Jordan Mantha - LaserJock
[09:35] <LaserJock> jsgotangco
[09:35] <highvoltage> http://www.edubuntu.org/news/3
[09:35] <mdke> cool
[09:35] <LaserJock> hehe, highvoltage you are everywhere
[09:36] <highvoltage> :)
[09:36] <highvoltage> and i've got irssi set up with nice highlighting too :)
[09:36] <crimsun> ah, congrats, you guys. :)
[09:36] <LaserJock> highvoltage: hmm, where do you put that, I was trying to figure that out the other day
[09:37] <highvoltage> /hilight edubuntu highvoltage whateveriwanttohighlight etc
[09:37] <LaserJock> crimsun: thanks
[09:37] <LaserJock> highvoltage: hmm, ok. that is certainly easy enough
[09:37] <highvoltage> yep :)
[09:38] <LaserJock> mdke: so lots of doc team showing on the Edubuntu Council ;-)
[09:38] <highvoltage> you can modify it later too, in the irssi text file if you want, by editing ~/.irrsi/config
[09:38] <highvoltage> edubuntu needs lots of docwork, so that's a good thing.
[09:39] <Surak> mgalvin: a link to cdimage.ubuntu.com/daily-live (or daily) could be provided there, what do you think?
[09:40] <mgalvin> Surak: good point... actually there was no tour for flight one and that is a link to the announcement... it would probably be best to do the same for beta 2 and flight 7 to be consistent
[09:41] <pygi> oki, people, I would have simple question 
[09:41] <pygi> what's the most desirable format for help/documentation thingy?
[09:41] <mgalvin> Surak: the annoucements have the download links in them anyway
[09:42] <mgalvin> pygi: it depends ;)
[09:42] <mgalvin> there is the wiki
[09:42] <mgalvin> or...
[09:42] <mgalvin> all the docs in the repo are in docbook
[09:42] <pygi> mgalvin: well, for the application help/documentation system
[09:42] <mgalvin> docbook
[09:42] <pygi> mgalvin: MonoDoc viewer seems very nice considering people can contribute, and upload contribution to server with a single click
[09:44] <pygi> mgalvin: thoughts? 
[09:44] <mgalvin> pygi: haven't used it... will install it and take a peek in a min
[09:44] <pygi> mgalvin: oki, thanks
[09:44] <mdke> pygi: I'm watching you >_<
[09:44] <pygi> mdke: ok, I am removing it this sec
[09:45] <LaserJock> pygi: some people are working on making GUI doc editing, jeffsch I think, is that right mdke?
[09:45] <mdke> pygi: for gnome apps, docbook xml is the format used
[09:45] <mgalvin> there are also some efforts among doc team members to make a similar tool
[09:45] <Surak> An employee of mine just found that page and was complaining about old stuff. I directed him to the cdimage link.
[09:45] <pygi> LaserJock: why don't we just SoC it?
[09:45] <LaserJock> pygi: you have to have a mentor ;-)
[09:45] <pygi> LaserJock: well, we'll find a mentor
[09:46] <LaserJock> I think it would make a good SoC project though
[09:46] <mdke> what's the project?
[09:46] <pygi> agreed 
[09:46] <pygi> mdke: something simmilar to MonoDoc
[09:46] <mdke> what is that?
[09:46] <crimsun> someone should just clone protg
[09:46] <mdke> or rather, explain the project without comparing it to an existing one
[09:47] <jeffsch> LaserJock: nope, not me. it's rob.
[09:47] <pygi> mdke: hm, well, the documentation viewer/editor where people can actually contribute, and they can upload stuff to server with a single click
[09:47] <LaserJock> jeffsch: oh yeah, for some reason I get you guys mixed some times
[09:47] <pygi> that's really nice
[09:47] <mdke> pygi: so a WYSIWYH editor for docbook xml?
[09:47] <mdke> s/H/G
[09:47] <pygi> basicly, yes.
[09:48] <LaserJock> What You See Is What You Hope for? ;-)
[09:48] <pygi> "F" is missing 
[09:48] <Surak> mgalvin: thanks, it was just to point it out for the correct person. let me go back to bugs channel :-)
[09:48] <pygi> omg, why it's still here
[09:48] <mdke> pygi: it has a life of its own, told you so
[09:48] <pygi> there :)
[09:50] <highvoltage> goodnight docteam!
[09:51] <mdke> nighty night
[09:51] <pygi> LaserJock, mdke: ok, nice...will go with docbook for now
[09:51] <pygi> also, someone please put idea for that project to wiki page?
[09:52] <LaserJock> pygi: sounds like you are volunteering :-)
[09:52] <mdke> i can think of two good potential mentors
[09:52] <pygi> LaserJock: no, I am not :)
[09:52] <mdke> neither on the ubuntu project though
[09:53] <pygi> LaserJock: I am currently looking over SoC applications
[09:53] <LaserJock> mdke: Gnome?
[09:53] <mdke> yes, shaun or danilo from gnome
[09:53] <LaserJock> are they sponsoring SoC projects?
[09:53] <pygi> Gnome? yup
[09:54] <LaserJock> that sure would be nice
[09:54] <pygi> mdke: well, could you talk with them? :)
[09:54] <mdke> pygi: sure, if the project materialises
[09:55] <pygi> mdke: oki, then someone please add it to the wiki =P
[09:56] <mdke> pygi: go ahead!
[09:56] <pygi> no, not me =P
[09:57] <mgalvin> jjesse_: i don't think i am going to create a flight 7 page... no time, not enought to cover... i will just link to the announcement
[09:57] <mdke> pygi: you suggested it!
[09:58] <pygi> mdke: yes, yes, put it in my face =P
[09:58] <Burgwork> mgalvin, when is flight7?
[09:58] <mgalvin> Burgwork: rumored to be today or tomorrow
[09:58] <Burgwork> ah
[09:58] <pygi> mdke: oki, I'll do it right away
[09:58] <mdke> good man
[10:04] <pygi> mdke: oki, done
[10:18] <pygi> mdke, mgalvin: I just saw gnome has SoC idea for creating new doc format???
[10:18] <mgalvin> pygi: link?
[10:19] <pygi> mgalvin: sec pls
[10:20] <pygi> http://live.gnome.org/SummerOfCode2006/Ideas
[10:20] <pygi> here somewhere :-/
[10:20] <Burgwork> that would be project mallard, no?
[10:20] <pygi> mallard? :) meaning of that word is? :P
[10:21] <mgalvin> Topic-Oriented Help?
[10:21] <mgalvin> library.gnome.org seems like a neat idea too
[10:22] <mgalvin> is our h.u.c automatic?
[10:22] <mgalvin> and d.u.c for that matter
[10:22] <mgalvin> Burgwork: it seems to be mallard, there is a link to it
[10:23] <pygi> yea, it's topic-oriented help
[10:23] <rob> hi guys
[10:24] <mgalvin> hi rob
[10:24] <pygi> mgalvin: I just saw it's mallard ;P
[10:24] <pygi> whatever that would be :)
[10:25] <mgalvin> its been being talked about for a while iirc
[10:29] <rob> hmm MonoDoc looks like its mainly meant for documenting applications done in Mono
[10:30] <rob> http://people.mosaix.net/chris/tutorials/monodoc/monodoc-tutorial.html
[10:30] <pygi> rob: yup, that's true 
[10:31] <pygi> but it's nice
[10:32] <rob> I'm going to go for a Sarma style editor (I'll probably try to reuse as much as possible)
[10:32] <Burgwork> rob, have you seen docudo?
[10:32] <pygi> rob: hm, you'll apply for SoC for that project?
[10:32] <rob> Burgwork, yes, but it doesn't support Docbook at all
[10:33] <rob> pygi, I wasn't planning on (didn't cross my mind), but maybe I could?
[10:33] <Burgwork> no, but it is saner, afaics, to add docbook to an existing editor than write a new one
[10:33] <pygi> rob: well, sure :) But I still suggest you follow the MonoDoc
[10:33] <pygi> it's quite nice actually
[10:33] <pygi> make a clone of it for docbook :)
[10:33] <rob> docudo uses a third party editor
[10:34] <rob> I'd have to replace that anyway, the rest of the framework isn't all that great (plus Docudo is part of a bigger non-documentation project anyway)
[10:35] <rob> pygi, MonoDoc does look good from the few screenshots I just saw
[10:35] <pygi> rob: and works nice :)
[10:35] <rob> I'll have to check it out later :)
[10:36] <pygi> rob: oki, nice :)
[10:36] <rob> ok, I'm off to work, bye!
[10:37] <Burgwork> rob, cya
[10:37] <pygi> bye rob