[05:53] dpm: I have the latest updates but theme names and (default) are in English. I only see revision 237 of 04_new_appearance_settings.patch - bug 968290 [05:53] Launchpad bug 968290 in Ubuntu Translations "System settings -> Appearance -> Theme entries don't appear translated" [Medium,Fix released] https://launchpad.net/bugs/968290 [05:55] hi artnay, good morning. Yeah, I was pinging you about it yesterday. Would you mind filing a separate bug as a follow-up? This way the desktop team can track it and clean it up [05:58] dpm: yes, I saw your highlight this morning. shouldn't I just reopen that bug and tell that theme names (originating from http://l10n.gnome.org/POT/gnome-themes-standard.gnome-3-4/gnome-themes-standard.gnome-3-4.pot ) were not marked for translation? [06:00] artnay, generally developers prefer not re-opening new bugs after they've been marked as fix released. That's why I would suggest filing a new one, and adding a reference to the old one in the description [06:01] as per (default) being in English, it was a recent change, which I'm not sure it has made it to the language packs yet [06:01] so the English (default) part might be a non-bug, but the English theme names definitely still applies [06:32] dpm: yeah, default was included in g-c-c template but not the theme names. I'll file a new one later. [06:32] great, thanks artnay! [09:18] hi TLE, morning. If you've got a minute, would you mind testing if http://91.189.93.101/ is working for you now? [10:38] dpm: it shows an index of files [10:42] ah, we're not there yet, but getting better :) [10:46] argh, it was a cronjob that didn't create the localized files. Let me try again... [11:15] TLE, can you try again? [11:17] dpm: we have lift off [11:17] \o/ [11:17] ;) [11:17] awesome [11:18] gotta go for two min [11:18] thanks for testing [11:18] np [11:46] ok, leaving early to start Easter Holidays, see you all on Tuesday! [12:45] hey there [12:45] kelemengabor: hey [12:45] hi === vibhav_ is now known as vibhav [12:55] kelemengabor: I sent you a mail just now, via launchpad [13:14] gotwig: okay, I took a look at your code. what you currently need is a beginners guide to i18n, and we don't really have one except for this: https://wiki.ubuntu.com/MeetingLogs/OpWeek1003/Translate [13:15] based on this, I think you can start learning how to internationalize your program [13:15] currently, I don't have time to do it for you, sorry :( [13:16] kelemengabor: no problem. I am in my holidays :-) I try to apply some code from the video lens [13:17] kelemengabor: ok ? [13:17] basically, you need to set up a little build system, I'd recommend python-distutils-extra, because its really simple [13:17] that would be great :) [13:22] kelemengabor: looks tooo complex :/ [13:58] kelemengabor: is there a way to create the POT files automaticly? [13:59] gotwig: using gettext? [13:59] you can run intltool-update -p any time [14:00] in the po directory, that is [14:00] but I dont know how to make a template for that... [14:00] I inserted all the variables at the header of the files [14:00] "in" [14:00] where I want translations [14:00] so, what now? [14:01] create a po directory [14:01] kelemengabor: have it already [14:01] and a po/POTFILES.in file [14:01] I applied that one from the other [14:01] so, yeah have it [14:01] list all the files with translatable strings in it [14:01] just the pot files are missing... [14:02] good :) [14:02] so what now :D [14:02] then you need to run intltool-update -p [14:02] in the po directory [14:02] that will create the pot file [14:03] I already have created directories [14:03] like launchpad wrote [14:03] for every file [14:03] but if you use python-distutils-extra, that will create one when you do ./setup.py build [14:03] so I can remove these dir's? [14:04] what dirs exactly? [14:04] *with no content* [14:04] for every pot file [14:04] I created a directory [14:04] geez, no! [14:04] there is only one pot file [14:04] kelemengabor: launchpad said that [14:05] no need for more for such a tiny program [14:06] cd into the po directory, and issue intltool-update -p, this should create one pot file [14:06] that's enough [14:07] vide.lens.in [14:07] *video* , ehm I need also such a thing, right? [14:08] yes, the .lens files are technically .desktop files [14:09] so whatever is written about their localization, stands for .lens files too [14:09] ehm but I have .service file already [14:09] isnt that enough? [14:09] that's a different thing [14:10] .service files are for D-Bus, not users, so there is nothing to do with them [14:11] .lens files contain user visible strings, so you need to deal with them [14:12] kay [14:12] now I have untitled.pot [14:14] kelemengabor: so what now :-) [14:15] translate it :) [14:15] but first, check if it really has all the strings you want to translate [14:18] kelemengabor: yes, it has. What you mean with translate it. I want to import it on my launchpad project [14:19] that too, but first it is better to test it, just to see if everything is in place [14:19] kelemengabor: oh ok [14:19] I'd bet that this isn't the case ;) [14:19] kelemengabor: so directly in the POT file? [14:20] yes [14:20] * gotwig is lazy [14:20] then save it as de.po [14:22] then you can build the project, and see it in action [14:24] kelemengabor: I think the pot file is wrong... [14:25] kelemengabor: http://paste.ubuntu.com/914590/ [14:26] looks good [14:26] kelemengabor: but the " " " things [14:26] kelemengabor: whats with them [14:27] what do you mean by " " " things ? [14:28] kelemengabor: msgid "" "Can't find gourmet recipe managers database in ~/.gourmet/recipes.db. Is it " "installed?" msgstr "" [14:29] those are just long lines broken into shorter ones, don't worry [14:31] there is one thing to worry about when testing, the "Content-Type: text/plain; charset=CHARSET\n" line - you need to replace CHARSET by UTF-8 in this. other default values can be left unchanged, but msgfmt will bail out on this one [14:36] kelemengabor: ok, so I have now my de.po [14:36] kelemengabor: what now [14:37] did you set up your project with python-distutils-extra? [14:38] kelemengabor: what you mean, no [14:38] okay, then that's the next step [14:38] you need a minimalistic build system, to: [14:39] kelemengabor: setup.py and such stuff [14:39] * merge the translations into the lens file [14:39] yup [14:39] kelemengabor: ?? [14:39] * create .mo files from .po files and install them [14:40] you need to automate these things, and a build system does that [14:40] kelemengabor: can I apply the one from the video lens? [14:40] yes [14:40] with minor changes :) [14:41] kelemengabor: so setup.cfg and setup.py? [14:41] yes, nothing else! [14:42] * gotwig is amazed [14:45] kelemengabor: 'lib/unity-lens-video' [14:45] kelemengabor: duno how to replace that, or with what [14:48] kelemengabor: ok, finished somehow, how does that look? [14:49] kelemengabor: http://paste.ubuntu.com/914623/ [14:50] with the data_files, you should tell the build system where to install and what [14:50] so probably the lib part should have been left unchanged [14:52] basically what you now do in the debian/unity-lens-cooking.install file should be abstracted out into setup.py [14:53] kelemengabor: in the data_files section? [14:54] yes [14:55] kelemengabor: for each file? [14:55] but I'm not really a programmer myself to explain it in enough depth [14:55] kelemengabor: you dont have to [14:55] kelemengabor: so for each file? [14:55] no, for each target directory [14:56] so if you have more .service files that go into the same directory [14:56] they can go into the same entry [14:56] kelemengabor: e.g? [14:56] "no programmer" [14:56] sorry :( [14:57] kelemengabor: thats no programming stuff xD [14:57] ^^ [14:57] I saw something like this in language-selectors setup.py [14:57] please check that [14:57] kelemengabor: language-selectors, what you mean? [14:57] lp:language-selector [14:59] kelemengabor: This branch is obsolete. Please use bzr branch ubuntu:language-selector from now on. [14:59] lol [14:59] yay :) [15:08] kelemengabor: http://paste.ubuntu.com/914644/ [15:09] looks good [15:09] kelemengabor: so what now [15:10] now you can run ./setup.py build_i18n [15:10] and it will/should generate a pot file [15:10] like magic! :) [15:10] and its name won't be untitled.pot, but unity-lens-cooking.pot [15:11] now you can commit that into the branch and set it up for import into LP [15:11] ERROR [15:11] ? [15:11] kelemengabor: NOTICE: po/de.po is not in UTF-8 but CHARSET, converting... Unknown encoding 'CHARSET' at /usr/bin/intltool-merge line 419 [15:12] yay... [15:12] told you :) [15:12] kelemengabor: so what xD [15:12] (16.31.11) kelemengabor: there is one thing to worry about when testing, the "Content-Type: text/plain; charset=CHARSET\n" line - you need to replace CHARSET by UTF-8 in this. other default values can be left unchanged, but msgfmt will bail out on this one [15:13] * gotwig ist wütend [15:13] kelemengabor: intltool-merge -d po cooking.lens.in build/share/unity/lenses/cooking/cooking.lens Merging translations into build/share/unity/lenses/cooking/cooking.lens. [15:13] kelemengabor: worked [15:14] the translations exported from LP won't suffer from this, but if you test manually, you have to take care of such silly details [15:14] nice! [15:14] kelemengabor: so what now [15:14] ;) [15:14] build a package with debuild for my own? [15:14] yes [15:14] kelemengabor: how old are you [15:15] and see if that goes alright [15:15] that's irrelevant ;) [15:16] not for me, Sir ^^ [15:16] kelemengabor: thanks for your help [15:16] you are welcome :) [15:18] so now testing [15:18] finished [15:18] have to restart my pc... [15:25] hey [15:26] kelemengabor: dont worked, I think I have to import some libraries... [15:26] kelemengabor: NameError: name 'APP_NAME' is not defined [15:26] um, yes [15:27] there is a few lines to be inserted in the code [15:27] kelemengabor: what is the error here ^ [15:27] http://docs.python.org/library/gettext.html [15:27] kelemengabor: In the scopes : NameError: name '_' is not defined [15:28] see the example code under 22.1.1. GNU gettext API [15:29] kelemengabor: whats up with APPNAME? [15:30] APP_NAME [15:31] in many cases the gettext initialization needs to happen in many files, because there are multiple executables in the same project, and to make this more reliable, developers define these in a config.py file, which they import and use the variables [15:32] this is why you see this APP_NAME in the copied code [15:32] config.py :/ [15:32] but, for such simple projects, this is not necessary [15:32] and you can simply replace it with the name of the pot file [15:32] which is called here the translation domain [15:33] and the path part in the bindtextdomain call can be /usr/shar/locale [15:33] the local_PATH ? [15:34] so just hardwire it in the code, and hope that it won't get much more complicated in the future :) [15:34] yes, that one [15:34] and APP_NAME? [15:35] kelemengabor: hm, I g2g in 1 min... [15:36] that would be the value of the name= key in setup.py [15:36] hi! [15:36] andrejz: jo [15:36] does docs site work for anyone else http://91.189.93.101/ ? [15:36] unity-lens-cooking [15:37] andrejz: not for me [15:37] kelemengabor: thanks [15:38] kelemengabor what does unity-lens-cooking do? [15:38] searches recipes online [15:38] gotwig was learning how to internationalize things :) [15:39] that sounds quite cool [15:39] altough i don't know how helpful is it to internationalize the lense if the source (recipies) are in english [15:40] yeah... but it just became apparent that we don't really have good developer tutorials on this topic [15:42] well, that's a good question, but I think the helpful thing is that he learned a little about i18n in general :) [15:49] too bad web page doesn't work [15:49] i was planning to review the documentation [15:50] version on HDD is outdated :( [16:08] hey [16:08] kelemengabor1: jo [16:08] kelemengabor1: the lens now somehow runs, but the scope give me : Traceback (most recent call last): File "./unity-scope-recipefy", line 14, in RUNNING = _("Failed to own name %s. Bailing out. An other instance is already running!") NameError: name '_' is not defined [16:08] hi gotwig [16:09] kelemengabor1: should I paste the file? [16:09] yes - you have to import gettext in every file [16:09] that contains translatable strings [16:10] also the _ = gettext.gettext line [16:10] kelemengabor1: http://paste.ubuntu.com/914729/ [16:11] and nothing else - so not the textdomain things [16:11] kelemengabor1: is in the lenns file tooo much info? [16:11] "lens" [16:12] no :) [16:13] but the _ = gettext.gettext is missing in most of these [16:13] kelemengabor1: I need more than that [16:13] kelemengabor1: LANG= etc. , roo [16:13] "too" [16:14] in theory, not [16:14] the initialization stuff needs to be defined once per process [16:14] kelemengabor1: so yes... ? [16:14] the meaning of the underscore is once per file [16:14] kelemengabor1: per system process? [16:15] kelemengabor1: I totaly dont understand what I have to do now :( [16:17] so... [16:17] kelemengabor1: cant I just apply the specific header things from the lens file? [16:17] if it is a standalone process, it needs to know where it should look for translations [16:18] if it is an imported module, then this is not needed [16:18] this is why the textdomain needs to be set once per process [16:19] but the gettext module needs to be imported into each file that uses it [16:20] and because it is a little long to type gettext.gettext(), you need to define a convenience alias for it [16:20] also for each file that uses it [16:21] now on to the paste, I think the gettext initialization is overcomplicated for no specific reason, between lines 251 and 290 [16:22] the environment variables are usually handled correctly by Python itself [16:22] so no need to fuss with them, IMHO [16:23] kelemengabor1: the video lens has these lines (?) [16:23] ask its developer why :) [16:24] because usually it is not necessary... [16:24] kelemengabor1: the developer said he had nothing to do with the translations [16:24] kelemengabor1: so do you know how I can replace it ? [16:25] * gotwig wishes a 'golden' paste [16:25] yes, look at the example code on http://docs.python.org/library/gettext.html [16:25] those are the important things [16:28] kelemengabor1: haha, my translated error message gets displayed [16:28] cool :) [16:28] for geeks maybe xD^^ [16:32] kelemengabor1: hm.. I got a few problems [16:33] still? :( [16:33] kelemengabor1: I restart [16:33] kelemengabor1: wait [16:40] hey [16:40] kelemengabor1: jo [16:40] kelemengabor1: does not work!! :X [16:41] :( [16:41] any error message? [16:42] kelemengabor1: in the lens, yes [16:42] (process:7915): libunity-WARNING **: unity-scope-factory.vala:78: Unable to search for scopes: No such file or directory [16:43] kelemengabor1: hmm... [16:44] this is at least not an i18n error :) [16:44] rather packaging... [16:47] Hi! Is there a way for my translation of vimtutor file be in the Precise repositories? [16:48] kelemengabor1: ... any plan? should i paste ß [16:48] ? [17:03] re [17:04] kelemengabor1: any idea, boss :D ? [17:04] well, without seeing the code... [17:04] kelemengabor1: well, I could up it [17:04] kelemengabor1: but that would break some stuff [17:05] please do [17:05] kelemengabor1: I mean, its not that stable [17:05] kelemengabor1: can I past it [17:05] ? [17:05] or, wait I just up it in U1 [17:05] paste is fine [17:05] kelemengabor1: which files? [17:06] hm, any/all of them :) [17:06] kelemengabor1: ok, wait for U1 up :O [17:10] kelemengabor1: you can edit the files, when I have your mail [17:10] okay, kelemeng at ubuntu dot com [17:11] a ubuntu mail adress, cool :P [17:11] be an ubuntu member, and you can have one too :) [17:11] I know, but its not that easy :X [17:12] kelemengabor1: ok, I added you to the share list [17:12] got it [17:15] kelemengabor1: goood [17:17] kelemengabor1: hmm, do you know the IRC channel name of canonical? [17:17] no [17:19] kelemengabor1: hm, do you see something strange in the code ... ? [17:22] * gotwig is afk for 10 mins [17:22] nothing yet [17:31] * gotwig is back [17:35] kelemengabor1: :-) [17:36] kelemengabor1: you haven't found anything wrong, right :X ? [17:37] gotwig: sorry, something is wrong with my U1 account, I see the folder on the web, but it does not sync locally [17:37] could you share it again, this time with kelemeng at gnome dot hu? [17:37] kelemengabor1: ok [17:38] thanks [17:38] kelemengabor1: I thank you. [17:39] kelemengabor1: got it? [17:39] yes [17:49] kelemengabor1: :-) ? [17:49] still does not sync :( [17:49] please send a tarball :) [17:55] kelemengabor1: hmmm [17:55] kelemengabor1: you can simply download it over the webpage [17:56] , cant you? [17:57] I don't see an option for that [17:57] wget has all options, lol. :D [17:58] kelemengabor1: to the gnome mail adress? [17:58] yes please :) [18:00] kelemengabor1: sent [18:03] kelemengabor1: got it? [18:03] yes [18:08] kelemengabor1: good [18:16] kelemengabor1: found anything ( third question :O ^^) [18:16] nothing outstanding, but the deb file is successfully built :) [18:16] logging out to test it [18:21] kelemengabor1: back.. [18:21] kelemengabor1: somehow I had a timeout [18:22] henninge: hey [18:26] Hi gotwig_ ! [18:27] henninge: J0! [18:29] gotwig_: okay, one problem: the package does not contain the .mo files [18:30] kelemengabor1: ok [18:30] kelemengabor1: so do you have a solution [18:31] they are generated in build/mo, they should go to /usr/share/locale/ [18:32] well... this is just one problem, there may be others too. not sure yet [18:32] kelemengabor1: can I manualy copy them there, and than retest? [18:32] yes, it is worth a try [18:33] kelemengabor1: it doesnt looks bad, IMHO... [18:33] kelemengabor1: the error message in console worked [18:33] for scope [18:33] kelemengabor1: in german [18:33] good, then we are close :) [18:34] kelemengabor1: but I g2g soon :(! [18:34] kelemengabor1: in which timezone are you? [18:34] CEST [18:34] but tomorrow I'll be traveling [18:34] damn [18:34] :-) [18:35] have fun [18:35] usually, you can find me here [18:35] I'll be offline only for one day, so you can find me on friday and after :) [18:36] kelemengabor1: I dont know why they dont run... [18:36] kelemengabor1: oh and I see no lenss [18:36] "lens" [18:36] I see it, but does not work [18:37] I mean after typing in something, I should see some results, right? [18:38] kelemengabor1: yes, and you should see the icon of the lens [18:38] kelemengabor1: in the dash [18:38] kelemengabor1: thats more importantt [18:38] "important" [18:38] the icon appears [18:38] kelemengabor1: do you know someone other that may help me? [18:39] not really, I'm not into lens development, but ask on #ubuntu [18:39] kelemengabor1: thanks, bye [18:39] bye [18:39] kelemengabor1: good night ;Ü [18:40] oh, one more thing! [18:40] you install the lens from the wrong dir [18:41] in debian/unity-lens-cooking.install [18:41] you should install the one from build/share [18:41] not the one from the project root [18:41] which, btw, should not exist anymore [19:29] kelemengabor1: hey [19:33] re gotwig [19:58] kelemengabor1: so, is there something wrong in packaging? [19:59] yes, the lens file [19:59] I don't think this is why it does not work, but nevertheless :) [20:00] kelemengabor1: hm [20:00] these things: http://irclogs.ubuntu.com/2012/04/04/%23ubuntu-translators.html#t18:40 [20:01] ?? [20:02] kelemengabor1: eh, so does your build work?? [20:02] no, it doesn't, this is another problem [20:02] kelemengabor1: which? [20:03] duno :X? [20:03] the lens file [20:03] you do not install the translated one, but the old one [20:03] kelemengabor1: so do you have a solution?? [20:04] I have to take the one from build, rightt? [20:04] I have no idea why the search itself does not work === vibhav is now known as Guest6358 [20:04] yes [20:05] kelemengabor1: maybe it has problems with communicating with the scopes... ? but I changed nothing there [20:05] kelemengabor1: so what do I have to change now, to be on the same level as you? [20:07] um, I didn't changed anything, I'm just telling what to do :) [20:07] but this install problem is in the debian/*install file [20:09] cooking.lens /usr/share/unity/lenses/cooking [20:09] this line [20:10] what with it [20:10] and of course you should be fixing the .mo files installation while you are there :) [20:11] so whats wrong in the install file [20:11] build/share/unity/lenses/cooking/cooking.lens /usr/share/unity/lenses/cooking [20:11] I think this should do it [20:12] and similarly with mo files [20:12] build/mo/* /usr/share/locale [20:17] gotta go, bye all! [21:42] hey [21:42] Please help me in translating my cooking lens & scopes in your native lanuage :-) https://translations.launchpad.net/lens-cooking/trunk