=== jgoguen is now known as LinuxFredBot === LinuxFredBot is now known as jgoguen [19:55] mdke: hi [21:10] adiroiban: hi [21:11] for hardy I have changed the ubuntu-doc folder organization to match the one from intrepid [21:12] and in this way I can use the same script for doing all the work [21:13] adiroiban: that's not something we can use I'm afraid - the changes to the directory structure are too invasive to upload to hardy [21:13] adiroiban: but, most tranlators are not focusing on hardy now anyy [21:13] s/anyy/anyway [21:14] ok [21:15] adiroiban: in your last email you asked if I can request the translations for intrepid, but I sent those to you already, you got them, right? [21:15] but the hardy POT files were not changed, so I can use my local folders to generate the report and other stuff [21:15] I got a set [21:15] but I don't know if they were for hardy or intrepid [21:16] I said in the covering email which release was applicable, hardy or intrepid [21:16] you should have got them both [21:16] Ah. my bad [21:17] I got both of them [21:17] great [21:17] Thanks! [21:17] do you think we need to create jaunty reports? [21:18] I've uploaded the intrepid translations to our ubuntu-intrepid branch [21:18] jaunty reports would be useful, but not yet - we haven't yet uploaded the pot files for jaunty [21:18] ok. [21:19] I will update the stats page using the new Intrepid po files [21:20] brb... about 15 minutes [21:21] hey mdke [21:21] fyi i was accepted for membership, thank you again for your testimonial! [21:23] Rocket2DMn: hiya. Yes, I saw that, good job! [21:23] :) [21:23] i also have a question for you: [21:23] why can't we set importance on bugs filed against Ubuntu Documentation? [21:35] Rocket2DMn: are you in the ubuntu-core-docs team? [21:35] ubuntu-core-doc, sorry [21:38] Rocket2DMn: looks like you're not; ubuntu-core-doc is the bug supervisor for the ubuntu-doc project so that's the team that can set importance for bugs [21:46] no, im not in that [21:47] i didnt notice that team was set as the maintainer [21:48] back [21:52] well, i have no intention of being a committer, i'm not familiar with bzr or the process [21:56] Rocket2DMn: it's really easy to learn if you're up for working on some of the system documents - we always need new contributors :) [21:56] Rocket2DMn: obviously, we can help you as you learn [21:58] if you or somebody else wants to teach me, then i'm willing to learn [21:58] sure, you'll always find help. The only skill you need is to be keen to contribute [21:58] i havent used bazaar at all, and dont actually know anything about the system documents and ubuntu-docs package [21:58] and having seen your work so far, I know you have that skill [21:58] ive done most of my work on the wiki [21:59] Rocket2DMn: have a read of the pages under https://wiki.ubuntu.com/DocumentationTeam/SystemDocumentation and see if things start to make sense or if you have other questions [22:00] alright, i'll have a look at that shortly, looks like there is a lot of info there [22:00] yeah [22:01] oh, and did you get my message a week or two ago about your forums howto [22:01] its a little outdated [22:02] http://ubuntuforums.org/showthread.php?t=81999 [22:04] Rocket2DMn: yeah, we should definitely update that, I'll put it on my mental todo list [22:04] thanks [22:14] mdke: the intrepid xml and html generation and status script is running and in a couple of hour we should have a result. you only need to put the achive form Launchpad in the docs root folder and the script will do the job :) [22:19] mdke, i had a look through those pages, they seem straightforward enough. I'll setup my local copy/branch later tonight when i'm back in Ubuntu. [22:23] Rocket2DMn: great [22:23] adiroiban: great as well :) [22:24] :) [22:57] mdke: what do you say about the idea of having the Glossary as a docbook? [23:04] adiroiban: the question is whether it would be useful for inclusion in the system documentation? I'm not sure really [23:05] I'm not sure whether people would use it, or how much work would be required to make it high quality [23:06] now we have the "windows" glossary [23:06] I find it useful for new computer users [23:06] that's part of the "Switching from Windows" document, yes [23:11] maybe we could adapt the wiki glossary page to be used in the system documentation. Quite a few irrelevant items would be removed, but reading through it, it doesn't look to be in bad shape [23:17] I found it more useful in the translated form [23:17] as a user can see a concept (maybe translated) [23:17] and search to see what's that [23:17] for example if I want to search yelp for "sesiune" (the romanian translation for session) , it will return 0 results [23:17] if I will try "session" (but I don't know if a user will do that) , yelp returns to many results, from different applications [23:17] but the term is not described in any result [23:18] that's strange [23:18] yelp should find translated words as well, I wonder why sesiune doesn't have any results [23:20] "session" is popular in gnome-user-docs [23:20] but gnome-user-docs is not yet fully translated [23:20] I see [23:20] "session" doesn't appear in the Glossary on the help wiki though... [23:21] maybe we could add items from other glossaries [23:21] I like the idea of having a wiki as it is easy to edit [23:22] but that glossary is not included in yelp [23:22] maybe create a script to parse the wiki and create a yelp document [23:22] looking after other glossaries is another step [23:23] there is an Gnome one... but it was not updated [23:23] it would be great to have one glossary for all open source projects [23:23] there are no good tools in existence for converting wiki markup to docbook, otherwise we'd have our whole project in a wiki [23:23] but I don't know if this is feasible [23:24] there are some, but they all have quite significant defects [23:26] so the best we can do is to export the wiki page into xml using one of the existing tools, tidy it up, and continue to maintain it in xml [23:26] I would like to have a translatable glossary for 2 reasons. 1. Help users, 2. Help translators [23:27] right, but a glossary for Rosetta would be very difficult to a glossary for Ubuntu documentation [23:28] true... maybe have the translators glossary and from a subset of those term to create the documentation glossary [23:28] I could imagine that for translators, this glossary will look more like a terminology [23:29] hmm [23:31] but a least for Ubuntu, from the user point of view, I can imagine a common glossary for Ubuntu and GNOME [23:31] right, that's what I meant by adding items from other glossaries [23:32] apart from GNOME, what other glosarries were you thinking of? [23:32] any others that exist, I don't know [23:33] ok [23:33] I will start a discussion on the mailinglist to see what other glossaries we could use [23:34] and what people say about it... maybe the glossary will not be of to much help in ubuntu-docs [23:34] yes. You can carry on the existing thread [23:39] * mdke goes to bed, night all [23:39] good night [23:39] the script is still translating xml files [23:39] :)