On 07/28/2009 10:33 AM, Robert Staudinger wrote:
> On Mon, Jul 27, 2009 at 8:31 PM, Hubert Figuiere<hfiguiere@teaser.fr> wrote:
>> On 07/27/2009 03:25 AM, Robert Staudinger wrote:
>>> I think leveraging gtk-builder's gettext support is the natural choice
>>> with the move to gettext. Quite possibly the issue of duplicated
>>> strings can be solved somewhere else, like providing a patch to
>>> intltool to include that option or using a script of our own to prune
>>> the .po files.
>> So how do you want to handle the two other platforms?
>
> Why can't they just either continue to use the StringSet API or move
> to gettext as well, whatever deemed best?
It is not gettext the problem. It is the way you use gettext and how you
consider that only Gtk has translation. As it stands now, both Win32 and
Cocoa will have to have their own translation (and by translation I
really mean the strings in the PO files).
I'm not sure what the proper solution is, but surely using the
GtkBuilder files as a reference is NOT.
I have already said that a couple of weeks ago while you were away.
Hub
Received on Tue Jul 28 18:04:57 2009
This archive was generated by hypermail 2.1.8 : Tue Jul 28 2009 - 18:04:57 CEST