[01:51] jbicha / godbyk : I am going to build the ubuntu docs package now and have someone sponsor its upload [01:52] I have a few people I can nag for sponsorship :P [02:23] bkerensa: Great! [02:23] bkerensa: Let me know if I can do anything to help. [02:23] godbyk: did he tell you what version for the changelog [02:23] bkerensa: And please try to document the procedure as you go along. [02:23] godbyk: I assume 13.04.1? [02:23] bkerensa: That's what I assumed, as well. [02:24] bkerensa: I used the following three lines for the changelog entry: [02:24] * Merged updated gnome-docs [02:24] * Capitalized Dash and Launcher consistently [02:24] * Bumped version numbers on the "What's new in Ubuntu 13.04?" page [02:29] yeah [02:32] jbicha: oh this is slower than normal package building [02:32] heh [02:32] * bkerensa might just leave this and go have a snack or something [02:32] :) [02:32] godbyk: building the package now [02:32] \o/ [02:37] bkerensa: Excellent! [02:38] bkerensa: Don't forget to bump those version numbers in the html dir. [02:38] build complete without errors [02:38] oh? [02:38] damn [02:38] :( [02:40] bkerensa: Yeah, I just stumbled across those tonight. Also, you'll need to take all the screenshots for the html/ stuff to build properly. [02:40] bkerensa: I'm not sure that the html/ dir is required for the system docs package, however. That might be solely for the website. [02:40] bkerensa: you should wait until at least Monday evening for the actual upload to give the translators as much time as possible [02:42] jbicha, bkerensa: which means you'll want to download the latest translations from launchpad a the last moment. [02:44] jbicha: make: Nothing to be done for `html'. [02:44] jbicha: ok well I will grab the tarball again tomorrow and rebuild again tomorrow [02:45] but the build was clean anyways [02:45] bkerensa: cd html; make [02:45] bkerensa: it has its own Makefile. [02:56] hi guys, I have been trying to figure out how to get our documentation for vinuxproject.org into .md files and authored as malard so that we can include on our images to work with Yelp. If anyone may have blogged about this how to achieve I would love to read as my current efforts are not being very successful :D thanks [03:01] jbicha: Were you expecting the build to fail btw? Because I got a successful build ;o [03:05] bkerensa: Since there haven't been many changes this cycle, I would expect the build to succeed since it presumably succeeded for 12.10. [03:06] bkerensa: There may be some failures in the translations, though. (Though again, there haven't been too many changes there either.) [03:16] bkerensa: if you didn't include updated translations then the build shouldn't have failed; it's the translations that cause the problems [03:17] jbicha: i introduced the current tarball into the branch.... Maybe no changes were made? I havent really looked at translations [03:17] jbicha: there were some warnings during the build for some translations saying they couldn't be merged (not sute what thats about) but the build succeeded [03:18] did you rename the .po files? [03:18] jbicha: yeah :) [03:19] yes the translations tend to have lots of warnings, it's the errors that stop the build that are of high priority [03:19] maybe yelp-xsl and the other tools are more resilient to broken translations these days too [03:19] hmm [03:19] well thats good :) [03:19] jbicha: you must be busy with a gnomebuntu [03:19] ;) [12:21] Fudge: you author in markdown and want to convert to mallard? [12:22] bkerensa: regarding the warnings you get when merging translations for documents, those kinds of warnings happen when translators write something that isn't a well-formed xml fragment [12:23] itstool parses when merging. if it can't parse, it can't merge. [12:45] shaunm thanks so much for replying, yes I am hopeful. Am using this p [12:45] h [12:46] whoops url didnt paste: http://www.jpfleury.net/en/software/gedit-markdown.php [12:47] shaunm it's very possible I am screwing something simple up, I feel like I need some hand holding at this stage loL [12:51] Fudge: markdown and mallard are both syntaxes. to write in one and distribute another, you need a converter [12:51] and now I wish I'd stuck with my work on getting mallard support into pandoc [12:52] I just don't know of a markdown->mallard converter right now. I'd like to know of one, if somebody has one [12:56] Oh right, sounds like it would be useful. May I clarify what you ahve said? If I write our stuff in Malard then I can call it with Yelp for our specific documentation to ship on images? [13:14] correct. Yelp has native support for Mallard, DocBook, HTML, man pages, and info pages. For anything else, you have to convert it into a format Yelp supports. [13:23] that is very cool mate [16:31] jbicha: Hey so slangasek will sponsor my build but I could just push the final stuff to a branch and MP it right? [16:31] like do the make html and make sure the latest translations are imported and then just push that to a branch? [16:40] there's several different branches, if you're talking about sponsorship I'd just ask slangasek what format he'd prefer to sponsor [16:41] for the lp:ubuntu-docs branch, yes we need a merge proposal with the updated translations and changelog (and he could possibly just use that to sponsor from) [18:14] jbicha: ok [23:19] preparing final MP for raring docs [23:19] sponsorship will occur tonight [23:21] bkerensa: Great! Thanks for your help!