Gary Kramlich spake unto us the following wisdom:
> First off, the po directory. Up until now it was fine the way it is;
> having the translations for both the core and the UI. This isn't really
> what we'll want. It is possible to split it into multiple .pot files,
> but the question is, do we want to do this now, or later?
I think we should keep single .po files, actually, as this reduces the
burden on the translators. Tools exist (or can be written) to divide
the monolithic translations based on where the strings originate, if
anyone *really* wants to divide libgaim from Gtk+ gaim, and they care
that the translations are divided, too. I'm more concerned about
keeping the translators' jobs simple than having "appropriately"
divided po files.
> It was also just recently brought to my attention that the qq prpl uses
> gtk code. After a bit more investigation, I discovered this:
> grim@...$ grep -i gtk * | wc -l
> This obviously needs to be corrected.
> There is still also some gtk code in at least the perl loader. I know
> this is not an issue for the mono loader, and I have yet to check the
> tcl loader. Now it makes sense that these have UI code in them as well
> so that the plugins they load can take advantage of the UI. So the
> question I have here is, do we want something like trunk/loaders/? I
> know it seems odd, but as I mentioned above, a conditional include of UI
> code does seem reasonable.
The Tcl loader contains no Gtk+ code.
I would look first and see if the perl Tcl code can be replaced by the
request API, or if the request API can be trivially extended to
encompass what the Perl plugin requires. If the case is that the Perl
plugin allows for writing general Gtk+ gaim plugins (I honestly don't
know), this is a different matter ... and I guess that makes it a Gtk+
plugin unless it can be handily divided in two. (?) In either case,
I don't see a reason to move it up to a toplevel location; it's either
a core plugin or a Gtk+ plugin.
> Also, what do we want to do with files like plugins/ChangeLog,
> plugins/ChangeLog.API, and plugins/HOWTO? I would suggest moving them
> to doc, but I'm open to ideas here.
This sounds good to me.
> Finally, right now I'm moving pixmaps/ and sounds/ to gtk/. Now at
> first this made perfect sense, but do we want to keep at least a logo
> available in the core/ directory?
We might in fact move a number of "generic" images to the core/
directory, for the benefit of alternate UIs; this might include the
prpl-related icons, a Gaim logo, and the gaim dude -- which may or may
not be most of our images. This stuff might also warrant a
toplevel-ish media/ directory, to facilitate the building of
gaim-media type packages.
The laws that forbid the carrying of arms are laws [that have no remedy
for evils]. They disarm only those who are neither inclined nor
determined to commit crimes.
-- Cesare Beccaria, "On Crimes and Punishments", 1764