[07:57] <andrejz> good morning
[08:08] <trijntje> good morning people
[08:57] <dpm> good morning everyone!
[12:25] <RawChid> Good morning
[12:27] <RawChid> Anyone know how I can get/install podiff?
[12:34] <RawChid> Never mind, I found the script
[12:34] <RawChid> dpm, is it an idea to add podiff to the Translations Tools?
[12:36] <dpm> RawChid, yeah, it would be an idea, but I've never seen a fully working implementation of a podiff tool, so it might be a bit of work if you want to create it from scratch
[12:39] <RawChid> At the moment I'm looking at https://code.launchpad.net/~glatzor/podiff/main
[12:41] <RawChid> Looks like there isn't done anything about it in 5 years
[13:00] <askhl> Hello.  TLE and I are working on something related to a 'fully working implementation of a podiff tool'.  What would be the 'requirements' in order for it to be a fully working implementation?
[13:00] <askhl> RawChid, dpm ^
[13:01] <askhl> (I.e. what are your specific needs?)
[13:04] <RawChid> I'm not yet familiar with the podiff tool. Just looking what it does at the moment. FYI, I'm working on https://launchpad.net/ubuntu-l10n-tools  and was wondering if we should add podiff to this project (keep all scripts in a central place)
[13:06] <askhl> I thought a podiff implementation was already part of that project
[13:08] <askhl> (I'll be back later)
[13:21] <dpm> RawChid, yeah, I'd be up for keeping podiff in ubuntu-l10n-tools. I was aware of the ubuntu-translator tools project, but I started a new one because I wanted to start from scratch and write all tools in python instead of having shell scripts. At some point though, when ubuntu-l10n-tools is stable and provides a superset of the ubuntu-translator-tools functionality, we should either unify both projects or disable one of them.
[13:22] <dpm> but before moving or forking podiff from ubuntu-translator tools, I'd ask glatzor for permission
[13:22] <dpm> he's the original ubuntu-translator-tools developer
[13:23] <dpm> he maintains aptdaemon these days, and he's usually in #ubuntu-devel
[13:24] <dpm> askhl, I don't have very high requirements on a diff tool for now. Just that I can do 'podiff -u ca.orig.po ca.po' and that it gives me some meaningful output :)
[13:24] <dpm> I remember you guys mentioned you were working on this. Can you remind me where the project is, and what its status is?
[13:46] <RawChid> Okay
[14:02] <askhl> dpm, https://launchpad.net/pyg3t
[14:02] <dpm> ah yes, thanks askhl
[14:04] <askhl> There's a big difference bewteen the stable version and the development version
[14:04] <askhl> should probably finish the ongoing changes and make a release...
[14:06] <dpm> RawChid, so perhaps you should talk to askhl and unify efforts on the podiff tool ^
[14:08] <TLE> who said something about podiff
[14:08]  * TLE looks around
[14:08] <TLE> *G*
[14:10] <RawChid> l
[14:13] <TLE> ahh, sorry I missed the start of the conversation
[14:13] <TLE> you need a podiff for something?
[14:14] <RawChid> Okay, Not really
[14:14] <RawChid> http://paste.ubuntu.com/616725/
[14:14] <RawChid> In case you missed something
[14:14] <RawChid> I was wondering of we could add it to ubuntu-l10n-tools project.
[14:15] <RawChid> But now I understand you are working on that tool.
[14:15] <askhl> TLE, maybe it's time to finally release a new version
[15:36] <andrejz> wov. I just got data from provider of slovenian ubuntu mirror
[15:37] <andrejz> number of visitors has icreased by 40% compared to last year :)
[15:54] <TLE> dpm, RawChid: Ahh, I just catched up with the conversation. The podiff that is a part of pyg3t works (it is used quite a lot in the danish team) and it has a active maintainer (me). pyg3t as a whole is a pet project that Ask and I work on when we want to do some coding. It is pure python and has been written with maintainability in mind (e.g. with a separate po-parser that all modules use). If you want to include scripts I 
[15:55] <TLE> askhl: Yeah maybe we should, it is just very bad timing as you know, I'd have way more time to do the cleanup after the changes in the parser in september
[15:55] <TLE> I mean to do the clean up properly
[15:57] <TLE> dpm: RawChid: In stead of including scripts back and forth we could also consider just sharing a PPA
[15:57] <TLE> afk 5 min
[16:00] <askhl> TLE, the only critical stuff is that the obsoletes should be handled properly.  The parser is compatible with everything I think...
[16:00] <askhl> TLE, looks like the first (longest) of your messages may have been clipped
[16:01] <askhl> In any case, I don't think any cleanup is really required.
[16:10] <TLE> ahh I will paste it in parts:
[16:11] <TLE> dpm, RawChid: Ahh, I just catched up with the conversation. The podiff that is a part of pyg3t works (it is used quite a lot in the danish team) and it has a active maintainer (me).
[16:11] <TLE> pyg3t as a whole is a pet project that Ask and I work on when we want to do some coding. It is pure python and has been written with maintainability in mind (e.g. with a separate po-parser that all modules use).
[16:11] <TLE>  If you want to include scripts I humbly think that it is a good place to start. We also have a tool for grepping in pofiles, for xml-checking in po-files and for looking for common errors
[16:12] <TLE> askhl: yeah, it was mainly podiff I would have liked to restructure, but that can wait, lets get together some evening and finish the migration to the new parser up and make a release
[16:29] <RawChid> Okay, thanks for the info.
[17:23] <dpm> Andre_Gondim, are you around?
[17:24] <dpm> I got disconnected a couple of times, so reposting this in case it didn't go through:
 TLE, yeah, it looks good. It looks to me that's already the best place for a podiff tool, since I understand that the aim is for the project to be generic, whereas right now ubuntu-l10n-tools is still a bit Ubuntu-specific (apart from the search tool). If you are interested in feedback, I do have a comment on the project: I'd suggest calling it something more readable than pyg3t, as it's not really catchy or easy to remember, and most import
[17:24] <dpm> antly,
[17:24] <dpm>   it does not say what the project is about
[17:51] <TLE> PYthon GetText Translation Toolkit = pyg3t, and then you read it like py-get, ahh we thought it was so clever
[17:51] <TLE> dpm: ^^
[17:52] <TLE> *G*
[17:52] <TLE> we'll think about it
[17:52] <TLE> anyway
[17:52] <askhl> There's a choice between googlability and legibility.  It's one or the other
[17:53] <askhl> But I suppose a sufficiently obscure proper name would also do
[17:53] <dpm> TLE, yeah, I got it when I went to the LP page :) It's definitely clever, but it sounded a bit cryptic to me. Anyway, just a piece of feedback, I've been looking at the code and it looks nice
[17:54] <TLE> yes, the project is meant to be general
[17:54] <TLE> but since a ppa is fairly ubuntu centric I guess there wouldn't b a problem with sharing a PPA
[17:54] <TLE> who knows
[17:56] <TLE> in any case, maybe the most important thing is that we are still active, and interested in making it do cool stuff,
[17:56] <TLE> so we would be open to suggestions and feature requests as long as they fir within our ideas for the project
[17:58] <TLE> err: fit
[18:00] <TLE> have to reboot, be back in 2 min
[18:09] <TLE> ahh that felt better, I've been stuck in windows all day
[18:24] <dpm> I bet it's like getting out of the matrix ;)