=== Guest97054 is now known as MichealH === daker_ is now known as daker === daker is now known as daker_ [19:59] Evening rickfosb [20:03] Ahhh, the soothing music... [20:06] Good evening Chris... was in the other room [20:06] hello [20:06] (technically, still doing the 'day job') [20:06] Ahh. What was the day job again? [20:07] AT&T.. Data analysis - productivity, headcount and volumes [20:07] counting widgets [20:08] Aren't widgets those things that go in beer cans [20:08] :) those too! [20:10] incidentally the bzr-stats package is what can give a list of contributors. [20:11] Would that get a minimal list of contributors, then? [20:11] for inclusion, i mean [20:12] maybe. i need to play to see what it gives me [20:12] i am not sure if it deals with translators [20:13] ok; I'll be interested in what you get. I was looking at running 'spell' on the tex files in a batch... that proved to be not so helpful :) [20:14] Its real good at ignoring the non alpha stuff in the latex tags, but then finds a latex tag and thinks its misspelled. [20:15] are you trying to spell check [20:15] Though I might run a real quick look and get the easy spelling stuff out of the .tex files [20:15] yes [20:15] i usually use vim as my editor. It has a spell check option [20:15] :set spell [20:15] I bounce back and forth; vi to gedit [20:16] it highlights incorrect spellings [20:16] I'll try vim; I'm more of an old time unix user when it comes to that.... love the global search and replace, etc. [20:17] ok; stepping away for a while. Have a great evening. check you later [20:17] ok [20:17] laters [20:17] :) [20:24] There's a spellcheck.py script in the lucid-e1 repository that may be helpful. [20:25] Also try "aspell -t blah.tex" [20:25] It'll filter out the TeX commands and spell-check only the content. [20:30] Thanks! [20:32] evening godbyk [20:36] Hey, ChrisWoollard. How was your holiday? [20:36] i mean lovely thanks [20:40] Hey, rickfosb. How are things going? [20:41] godbyk; going well. just working... :) i just came back in here to restart empathy.. I lost the contact list and was not sure how to raise it (natty) [20:42] Ah, well, I'll let you get back to it then. :) [20:43] seeing the talk about different versions (kindle, etc) Sounds like some fun... using the tex files to build lots of usable output! [20:44] Yeah, I'd love to get some different output formats going (for e-readers, HTML, etc.). [20:44] Unfortunately, LaTeX seems to not be the best source format for all of those. [20:44] (ipad) hehe [20:44] Motorola Xoom ;) [20:44] I've not had much luck with the LaTeX-to-HTML tools. [20:45] I like latex so far; I'm just thinking with the right additions to our makefile, we might get some real leverage .. [20:45] I've been meaning to play with Docbook → LaTeX → PDF and Docbook → HTML chains, but haven't had the time yet. [20:46] would also like to be able to build by chapter... for ease of editing, etc., I'm reviewing my old Make books...brushing up... [20:46] (in my spare time) ha [20:46] Kevin, should i mention what Kyle did ;) [20:47] rickfosb: To build an individual chapter, you could edit the main.tex file, and add \includeonly{x,y,z} before \begin{document} [20:48] where x,y,z is a list of documents to include. all other \include's will be ignored. [20:48] ChrisWoollard: [20:48] ahhh. ok [20:48] ChrisWollard: dotell [20:49] rickfosb: He wrote a huge set of shell scripts that convert docbook documents to PDF using Apache's FOP. [20:49] rickfosb: Each chapter is its own standalone document. [20:49] rickfosb: But then they get mashed together to form a book (of sorts). [20:49] each chapter in its own branch [20:50] godbyk; indexing, page numbering??? must have been a btch [20:50] Oh, yeah, and that. Their project has an order of magnitude fewer contributors than ours, but he thought it'd be best if they went with one chapter per bzr branch. [20:50] So you have to check out over half a dozen branches to build the complete book. [20:50] I have not heard anything from them in weeks [20:50] no thanks [20:51] rickfosb: I don't think they have any indexing yet. Not sure how page numbering is handled. [20:51] Also, it has not been updated in 6/7 weeks [20:51] ChrisWoollard: I haven't heard from them in eons either. They seemed pretty content to go their own way. I don't have time to learn Apache FOP, so I can't be of much help. [20:52] godbyk: what's the project name? [20:52] rickfosb: The Ubuntu Developers' Manual. [20:52] geeez [20:53] rickfosb: https://wiki.ubuntu.com/DesktopTeam/10.10/DeveloperManual/ [20:53] They used our toolchain first [20:53] ok, my meeting minder's going off... I'll be back in an hour.. See you two. (thanks for the link godbyk) [20:53] Then converted the whole lot to docbook [20:57] I think that the "translation-credits" text in the credits.tex file should automatically be replaced by Launchpad during the translation process with a list of translators who contributed. [20:57] But I've never tried it before. [20:58] I was about to have a look at that [20:59] I also want to look into using the Ubuntu font as the sans serif font in the new edition. I have to check the language support and whatnot first, though, and probably adjust some font sizes. [21:01] nice [22:36] \quit