=== _thumper_ is now known as thumper [09:55] What does \gls mean? [09:56] Should I translate things like: \gls{panel}? [10:02] What does \gls mean? [10:03] Should I translate things like: \gls{panel} into \gls{paneel}? [10:06] I think gls means glossary [10:09] hannie: yes \gls is glossary [10:10] So I should translate {panel} [10:10] hannie: i think you can translate the text INSIDE the command but NOT the command itself [10:11] ok, is that the same with ss:(English text} where ss is screenshot (not to be translated? [10:11] ss: (no smiley!) but screenshot [10:27] hannie: yea sorry thats right [10:27] hannie: dont translate ANY tex commands [10:30] I think I am getting the picture. I do NOT translate \gls, ss, ch etc. But I DO translate text between {} [10:31] Example: \newglossaryentry{Ethernet port} becomes \newglossaryentry{Ethernet-poort} [10:34] Or should it be: \newglossaryentry{Ethernet port}{name={Ethernet-poort} [10:40] hannie: im not the best person to ask about translations [10:40] godbyk: ^^^^ [10:40] Have you checked the style guide? [10:41] ChrisWoollard: is there translator stuff in there> [10:41] ? [10:43] It is rather a matter of syntax, not style [10:46] What I need to know is: what happens with the text between {} after \newglossaryentry? Is this the entry of the English or the Dutch glossary? [10:52] thats the name of the actual glossary entry, i im pretty sure you need to translate that [10:56] ay, ay, ay, I am not so sure. After \newglossaryentry{text} you get {name={text}, description={text}}. [10:57] I DO translate {text} 2 and 3, but I am not sure about {text} 1 [10:57] i would expect there to be one label that shouldn't be translated [10:58] And that is \newglossaryentry{text}? [11:00] Perhaps it's a good idea to send an email about this to the ubuntu-manual mailing list. I think I will try that. [11:03] hannie look at /topic it has the stlye guide with lots of information for translators [11:12] I tried this: https://translations.launchpad.net/ubuntu-manual/topic [11:12] Where do I type /topic? [11:12] type "/topic" in the irc window [11:15] got it hannie ? [11:15] This doesn't work: /topic style guide [11:15] I am sorry, I am a beginner here [11:16] type just "/topic" [11:16] no problem [11:16] http://files.ubuntu-manual.org/style-guide.pdf is what you want [11:17] Thanks [11:18] When I type /topic I get a message: you are not allowed to change the subject [11:18] strange i get http://paste.ubuntu.com/440321/ [11:19] I have downloaded the style-guide.pdf file. I am going to read it. Thanks for the tip [11:28] Style-guide.pdf says: \newglossaryentry{⟨keyword⟩}{name={⟨term⟩}, description={⟨definition⟩} where (term) and (definition) are in RED. These should be translated, NOT (keyword), which is in BLACK. [11:28] Thank you all for helping me out :) [11:28] hannie: no prob, thanks for persevering through my lame translation knowledge [11:29] ;) [11:50] Hannie: Sorry for not responding further. I have had network problems. [12:03] ok, I have downloaded the style-guide.pdf file [12:05] I hope it helped [12:05] There is a lot of reading there :( [12:05] But thanks anyway [16:11] humphreybc, hey, so I should use LaTeX to start the developer's manual, right? [16:12] rickspencer3: i didnt know it was you doing the dev manual :) [16:15] nisshh, well, I'm "editor" and I have a few chapters [16:15] https://wiki.ubuntu.com/DesktopTeam/10.10/DeveloperManual [16:15] rickspencer3: cool, i may contribute to it too [16:16] nisshh, http://launchpad.net/~ubuntu-developers-manual [16:16] oops [16:16] https://edge.launchpad.net/~ubuntu-developer-manual [16:23] rickspencer3: I'm about to head to sleep, it's pretty late here. Have a chat with godbyk, he should be around today [16:23] LaTeX should be good though yeah [16:23] thanks dude [16:24] I want to make the first commit today or tonight [16:24] sleep well! [16:24] godbyk's our latex guy so he'll be able to hook you up with some sweet templates etc [16:25] rickspencer3: latex kicks-ass, its awesome for this sort of thing [16:25] I've never used it [16:25] I installed a Lyx, thought that might help me get started [16:26] is the manual in LaTeX format? [16:26] Can I just copy from that? [16:26] its really easy to learn to write in latex [16:26] yep manual is in latex [16:31] I am not sure on exactly what stuff you would need to copy from the manual. [16:37] you would probably have to modify whatever you copy, since the dev manual will probably be structured differently [16:40] That looks really cool. [16:41] the developers manual that is. [17:44] home again, home again, jiggity jig. [17:46] * vish silently loosens a few more bolts in godbyk's cars :p [17:47] lol [17:47] It did manage to get me to the grocery store and back last night. [19:24] hey @all [19:26] Hi, daker. [19:27] wassup ? [19:29] the sky :P [19:29] yeah :p [19:30] * ubuntujenkins goes back to revision [19:30] good luck :) [19:31] thanks [19:44] Waw the new website is looking great [19:44] ubuntu.com [20:42] godbyk: ping [20:43] c7p: pong [20:44] is there anything new about the greek manual :) [20:50] c7p: not yet. sorry. I've been busy with work and car repair the past couple days. [20:50] I'll try to work on it a bit later tonight, though. [20:52] godbyk: ok np :) hope you finish it soon [20:54] c7p: We'll get there, don't worry! The first one always takes a bit longer. :) [20:55] godbyk: hehe I know, we had previous experience with index, fonts .. etc! [22:26] godbyk: ping [22:26] ubuntujenkins: pong [22:26] I was bored in a lecture and was thinking about the ubuntu-manual program there are a few issues with the current idea [22:27] cool. fire away! [22:27] we said we would download them from the website but we need to store them in /usr/share/doc/ubuntu-manual. the permissons are root only. It is rather silly to need root permissions to download a pdf [22:28] * ubuntujenkins is a slow typer [22:28] so I am thinking of packaging each one. but we then have to work out how easy it is to get stuff in universe after release [22:29] also it the user had no interent and got the package at work or an internet cafe. they would then be anoyed that they have to somehow get internet again. [22:29] true. [22:29] we could also store it in their homedir. [22:30] but then it has to be downloaded for every user on the pc [22:30] (in, say, ~/.local/share/ubuntu-manual/) [22:30] true [22:31] and ~/.local/share/ubuntu-manual/) its not the convetionally correct way to do it. I think convetions are supposed to be stuck to [22:33] well, there is some convention (XDG directories) and we'd follow that convention if we put it in someone's home directory. [22:33] I am just asking in #ubuntu-motu about getting stuff in universe after release [22:33] 'kay. [22:34] I did some very rough sketches of the old work flow, which ment i found this problem [22:35] right [22:35] do the team know its the doc/manual/learning meeting on monday 31st 16.00 utc? [22:36] I don't know if anyone's paid attention to that. [22:36] I may be in a meeting IRL at that time; I'm not sure yet. [22:36] I'll attend if I can, though. [22:36] I saw the email [22:36] IRL? [22:36] in real life. [22:37] ok, i can make it as its a bank holiday for me [22:37] (I think it's one of those old-school acronyms that you kids don't use anymore. :-)) [22:38] Ooh, good point. It's a federal holiday here, too, so maybe I won't have that meeting. [22:39] * ubuntujenkins hmm #ubuntu-motu is quite === ubuntujenkins_ is now known as ubuntujenkins [23:24] 83307 [23:25] * ubuntujenkins ops not empathy [23:40] night all [23:53] It felt like a very quiet evening here today. [23:57] Goodnight