/srv/irclogs.ubuntu.com/2010/11/29/#ubuntu-translators.txt

dpmgood morning all!08:15
andrejzMorning!08:17
dpmgood morning andrejz!08:21
andrejzdpm, i have a question for you (again) :)08:21
dpmandrejz, no problem, shoot ;)08:22
andrejzWhile testing some translations i found out that launchpad import function doesn't work as it should08:22
andrejzSome translations aren't updated from upstream for a long time08:22
andrejzan example in our case is gnome-system-monitor08:22
andrejzwhich was imported in september 200908:23
andrejzand not imported afterwards (from gnome)08:23
dpmlet me have a look at the package...08:23
andrejzthe same thing happened with evolutoin, which was automatically imported from upstream some 2 weeks ago, but not since february before08:24
dpmok, let me see if I can find out something08:25
andrejzi noticed it yeasterday and manually added translation from upstream08:25
andrejzbecause i wanted to fix errors before language pack update08:26
dpmok, yeah, I'll be looking at the package itself, so don't worry, your latest uploaded translations will not make a difference to what I'm looking at08:27
andrejzok, good08:27
dpmandrejz, ok, I've found out what's happened with gnome-system-monitor. The upstream version is 2.32, whereas in Ubuntu we've got 2.28 (I don't know why, but I'd guess for stability, security or dependencies reasons). So unless you've been comitting to the gnome-2-28 upstream (I'm guessing not, because it's an old version and you've probably been comitting the latest translations to head or gnome-2-32), there are no new upstream translations that c08:43
dpman be imported08:43
andrejzyes, i see.08:43
andrejzwe were always commiting to the newest stable and unstable branch08:43
andrejzthis is not good, because we fix bugs in gnome and then don't check in launchpad.. so is it possible to get a list of packages which are older than newest upstream version?08:44
dpmandrejz, there might be, but we'd better ask in #ubuntu-devel or #ubuntu-desktop. Let me see if there's anyone around that can help us08:46
andrejzok, that would be great, thanks08:46
dpmok, asked, let's see if anyone can help08:51
oierHello08:53
oiera team member told me that there is a bug with a basque translation in the kubuntu installer08:53
oierthe original string is "Try Kubuntu"08:54
oierI am looking for the corresponding package to fix it08:54
oierbut can not find it08:54
oiercould you please help me08:54
oier?08:55
andrejzHello Oeir08:58
dpmhi oier, is that what you're looking for: https://translations.launchpad.net/ubuntu/maverick/+source/gfxboot-theme-ubuntu/+pots/bootloader/eu/+translate?batch=10&show=all&search=try+kubuntu08:58
oierno08:59
oierthat translations are correct08:59
dpmoier, ok, can you give us more information, so we can better help? What is the incorrect translation? On which version of Ubuntu is it shown?09:01
oierhe told me that the current (wrong) translation says "saiatu kubuntu" instead of the correct "probatu kubuntu"09:01
oierhe didn't told me in which version it is shown but I assume it is Maverick since it followed a post in which I forwarded your message about the Maverick LanguagePack updates09:02
andrejzoier, it's possible that the translation is correct but has not been exported in time09:03
oierI am not sure...09:04
dpmoier, nothing comes up after a search for "saiatu" in https://translations.launchpad.net/ubuntu/maverick/+source/gfxboot-theme-ubuntu/+pots/bootloader/eu/+translate?batch=10&show=all&search=saiatu - that's the only package where AFAIK that string is shown. Could you please ask the person who asked to give more detailed info? E.g. a) Ubuntu version, b) where does he see the string c) a screenshot, if possible, would be great09:04
oieryes09:05
oierI can ask him to fill a bug09:05
oierby the way, I am unsure about how kubuntu translations are managed by Launchpad09:05
dpmthey are managed more or less the same way the gnome translations are09:06
oierso I assume most of the translations of KDE are imported from upstream09:06
dpmyes09:06
oierbut we can modify them in Launchpad?09:06
dpmyes09:07
dpmoier, probably there is no need to file a bug for the "saiatu" issue. If he can just give you that info, you can just forward it to us on IRC and we'll try to find out. If the problem becomes complex, we can think of filing a bug09:07
oierok09:08
oierby the way dpm09:10
oierdid you received my email yesterday with the question?09:11
dpmoier, yes, I haven't got to it yet. Let me see if I can answer you in the next few minutes09:12
oierthanks!09:12
dpmno worries :)09:13
dpmandrejz, here you can see all the desktop-related packages' versions. If you want to filter out on versions, you can play around with the code used to generate the list (there is a link at the bottom of the page). I hope this helps09:27
andrejzwhere is here?09:29
andrejzi think you forgot to give me the link09:31
dpmandrejz, err copy & paste fail, here it is: http://people.canonical.com/~platform/desktop/versions.html ;)09:31
andrejzok, great thanks09:31
andrejzi would also like to mention that i agree with the procedure for SRU of lang pack09:32
andrejzAlso about the thing i was bugging you last week - about the list of words - we found a solution via a firefox extension and it works great for our purposes. I will blog about it on the planet sometime this week09:33
dpmah, great, glad to hear that, some people were not so happy with it and preferred langpacks to be updated without testing, so that's great to hear :)09:33
dpmand looking forward to hear more from that FF extension :)09:33
andrejzWell, in general i believe that in 99% of the cases the translations improve with the update so it's not really that necessary, but i think it's good to do a quick check09:34
andrejzthat's how i found out gnome-system-monitor translations didn't update properly09:34
andrejzmy moto is that you always learn something (even if it's not what you thought it would be initially)09:35
dpm:-)09:37
dpmoier, if you're still around, I've replied to your e-mail question on a private message, let me know if that helped you09:38
oieryes it helped very much09:39
oierthanks09:39
oierBTW09:39
oierI got feedback09:39
oierfrom the translation bug09:39
oierthe reporter told me that the string appears when you boot from a Kubuntu or Ubuntu 10.10 CD09:40
oierand you get two options "try (k)ubuntu" or to install it09:40
oierso that first string appears to be the problematic one09:41
oieris that the ubiquity package?09:41
dpmoier, yeah, if it's not bootloader, it can only be ubiquity or debian-installer. Try to do a search for "saiatu" there09:41
oierubiquity-debconf?09:42
andrejzdpm, i have an idea. Do you think it's possible/makes sense to add some space on the installation slideshow (like two or three sentences) where translator teams could add link to local pages / support forums09:42
dpmoier, yes, sorry, I meant ubiquity-debconf, not ubiquity09:43
oierok09:43
oierI think I found it09:43
andrejzif someone uses ubuntu in slovenian it would be great if he would also have links to available ubuntu resources in slovenian09:43
oierthanks!09:44
andrejzor anyone else - so you think idea above is good / makes sense ?09:47
dpmandrejz, that's something someone tried to do by changing the links to the official channels in a translation, and the ubiuity developers weren't too happy about it. The argument was that for an LTS release there should only be links that are supposed to be alive throughout the 5 years lifecycle of the release. That said, I think it makes sense. It would be a good idea to start a debate about it. Perhaps on the ubuntu-translators and loco-contacts09:49
dpm mailing lists + the ubiquity-slideshow one, if there is one09:49
andrejzOK, i will post it on loco contacts and ubuntu translations later today09:49
oierdpm09:58
oierI have another problem...09:58
oiera team member exported the translations of Transmission in Launchpad (which is upstream) and imported it in the Maverick package10:00
oierbut 58 unstranslated strings are shown after the import10:00
oierand it looks like some strings have been slightly modified10:01
oierfor example from "Set _Location..." in Launchpad10:01
oierto "Set _Location" in the maverick package10:01
oieror from "Use _global settings" to "Use global settings"10:02
oierdo you know why or how this divergence happened?10:05
oierdpm are you there?10:12
dpmoier, I am back, I was in a call, let me have a look...10:40
dpmoier, the divergence is because most probably the upstream code is newer than the maverick package. So I think the upstream code (which might not even have been released) might have just changed some original strings, but these new strings are not in maverick yet, because maverick has the latest stable version of the package instead of the bleeding edge upstream code10:42
oierbut 58 different strings are quite a lot and most of the changes are minor things as you can see in the examples10:43
dpmoier, well, to Launchpad "_this string" and "this string" is not a complete match, so it won't add the translation of the first one to the second one, and it will not do fuzzy matching either, so even if "_this string" is translated, when importing the translations, when it finds "this string" it will not translate it10:48
dpmso it does not matter if it's a minor difference, as long as it is a difference, translations will not be carried over10:48
oierok10:50
oierthanks10:50
=== Mirv_ is now known as Mirv
dpmTLE, are you around? Are you happy with using the next maverick PPA langpacks for testing and subsequent upload to maverick-updates? I figured out, that even if they did not fit any scheduled date on the calendar, we might as well release them asap, since it's been too long without any update for maverick14:15
askhl_dpm: For what it's worth I think it's an excellent idea to release a langpack update at this point15:03
dpmaskhl_, ah, thanks for the feedback, glad to hear that!15:04
TLEdpm: get back to you when I get home, or tomorrov of you have left by then16:18
dpmAndre_Gondim, could you confirm that bug 632760 has been fixed in maverick for the Brazilian version of Firefox?16:29
ubot4`Launchpad bug 632760 in language-pack-zh (Ubuntu) (and 6 other projects) "Language variants don't work in Firefox because the language codes are separated with an underscore rather than a hyphen in chrome.manifest (affects: 16) (dups: 1) (heat: 103)" [High,Fix released] https://launchpad.net/bugs/63276016:29
Andre_Gondimdpm, let me c, just a moment16:52
dpmcool, thanks Andre_Gondim :)16:53
Andre_Gondimdpm, yeah, it's solved16:54
dpmthanks Andre_Gondim!16:55
TLEdpm: hey17:02
dpmhey TLE, thanks for coming back to me :-)17:02
TLE*G* np, I was in the lab all day, so I didn't see your message before like 1 minute before I was running out the door17:03
dpm:)17:04
TLEyou were saying something about doing an update soon, because we have not have one yet17:04
TLEok, so17:09
TLEaccording to the plan it is release + 2, 6, 12, 22, 35 and 43 weeks17:10
TLE2 and 6 have already passed due to me being to slow17:10
TLE12 would be due in week 1 of next year and should be a 2 week testing release17:11
dpmTLE, it's not you being slow, it's just the way it went. The maverick PPA was not ready until last week, so there is not much we could do17:11
TLEbut we could just move it forward and take it in the first beginning of december17:11
TLEin the first part of december17:12
TLEI'll draw up a scedule right now and send it to you17:12
dpmTLE, I was thinking of doin it this week as per the message I sent to the list. The packages in the PPA will be ready on Wed/Thu and we could send the call for testing then17:13
TLEand then along with I'll also send those durations of the different parts of a language part update that we talked about17:13
TLEok, that sound fine17:13
dpmTLE, ok, that sounds good too, thanks17:14
TLEdpm: there we go: https://wiki.ubuntu.com/Translations/LanguagePackUpdatesQA/MaverickLanguagePackUpdateReleaseSchedule17:38
dpmTLE, great, thanks! One thing though: I'd suggest shortening the test period to 1 week instead of two, in order to reduce the time it takes to get a language pack out. It is also the same amount of time the QA team spend for the testing periods before releasing milestones during the release cycle, and I think the simple tests we've got with translations shouldn't really take more than a week. Does it sound good to you?17:45
TLEjust for this one, or in general?17:46
dpmin general17:48
TLEwe could do that, since people have been warned in advance that is probably ok17:50
TLEit would however not be exactly one week but more like 5 days17:51
dpmTLE, I think it should still be fine, if not, we can look at going back to 2 weeks. Btw, why would it be ~5 days instead of 7?17:58
TLEdeadline for testing is one day before upload and call for testing is probably one day after they have been uploaded to released17:59
dpmright, gotcha18:01
TLEI'll update the schedule in a sec18:02
dpmok, thanks. So I'll go ahead with the schedule and do the call for testing when the packages are copied to -proposed18:04
TLEyes18:06
TLEbtw, about the calendar18:07
dpmand I've just read your e-mail, thanks a lot, I'll update the figure accordingly18:07
TLEI'll just do a google calendar (and I-Cal file) this time, then we can figure out later if that is the way we want to go18:07
TLEgreat18:07
dpmTLE, yeah, I think that'll be the easiest option to get us started. Once we've got that, we can copy the milestones to the main calendar or decide if we want to keep it separate18:09
TLEdpm: yes18:09
TLEdpm: there we go: https://wiki.ubuntu.com/Translations/LanguagePackUpdatesQA/MaverickLanguagePackUpdateReleaseSchedule18:12
TLEdo you see any other problems with it?18:12
dpmTLE, we'll also have to think the location where we want to have the wiki calendar, as I'd like to have it somewhere else than as a subpage of LanguagePackQA - I'm thinking of either w.u.c./Translations/MaverickLangpackSchedule, w.u.c/MaverickLangpackSchedule or w.u.c/MaverickReleasaSchedule/MaverickLangpackSchedule. I haven't thought about it in detail yet, and I'm open to suggestions. It may well be that after the e-mail conversation with Kate S18:13
dpmtewart we consider putting it in that *Interlock page or on the main release schedule page18:13
dpmTLE, let me have a look at it now, thanks18:13
TLEw.u.c.?18:15
dpmwiki.ubuntu.com, sorry18:16
TLEahh *G*18:16
TLEI don't have any string opinions about that, maybe it's most appropriate as a w.u.c./Translations/-subpage?18:17
TLEerr: strong opinions18:17
dpmTLE, yes, perhaps. I'll think about it and come up with something before Thursday18:18
TLEstring opinions what the hell is that, maybe something you have considering python18:18
dpmTLE, well translators do have strong string opinions when reviewing translations ;)18:18
TLEtrue abough :: yes ok, but as long as the wiki-page is done is should be easy to move, I will get going with the calender so we can have it all ready for thursday18:19
dpmTLE, yeah, the updated Maverick schedule looks good to me, I think we're good to go to road-test it on the update this week. And yes, having the calendar there by then would be awesome18:20
TLEgrumble, enter time zone madness18:28
dpmTLE, :-) I'd just stick to UTC18:31
TLEyeah, the problem is that I google calendar uses my time as the reference, oh well, I'll figure it out18:32
dpmok everyone, see you all tomorrow!18:55
michael_kbb!18:55

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!