Re: [bug-gettext] New Gettext contributor

[Daiki Ueno]

Miguel Ángel <address@hidden> writes:

> Daiki Ueno <address@hidden> writes: 
>> Miguel Ángel <address@hidden> writes:
>> It seems not yet, see my private mail.
>
> Yes, I saw it. How couldn't i see there is no sign in the pdf? :(

Maybe good to wait for the response from FSF copyright clerk, before
starting actual work in the Savannah git.

> GSettings and update gnome are not dependant, but the first needs expat
> compatibility extraction from x-glade.c (or adding an unlikely related
> file type to x-glade.c to parse also GSettings) and the second needs
> GtkBuilder extraction and

This sounds like a bigger topic than just supporting GSettings schema
files, since intltool allows any element whose name starts with "_" to
be translated.

Also there were some requests to support the file formats used in GNOME:

<https://lists.gnu.org/archive/html/bug-gettext/2011-05/msg00006.html>

I think we should ask GNOME people what they want these days.  A
discussion on their lists (possibly address@hidden) would
be a good start.

> I do not think that we want to depend on intltool in our examples. ;-)

The current hello-c-gnome and hello-c++-gnome examples do not use any
settings.  How about starting from a minimal example, which does not
depend on your gsettings patch?  Then it can be easily merged.

>> What's the current state of each patch?  Last time I looked at your
>> patches posted here, they were work-in-progress and github commits
>> were more up to date.  Are they now stable?
>
> I did a couple of minor changes since I have posted them, but GtkBuilder
> patches has not changed since 2013-02-06 and Glade and xgettext ones
> since 2013-01-31. They are tested with make check and with each package
> with NLS I build at my main machine.

Okay, so those "core" patches can be reviewed.

> I was going to send them (arglist_parser, Glade2, GtkBuilder and
> libasprintf) but I have to do a question before, do I have to update
> ChangeLog date? I mean, which date (patch date or the commit one) must
> be there?

I'm not sure :-)  But it could be tweaked later.

> And about libgettextpo trailing backslash: It could be a documented
> feature and not a bug, comments are welcome.

I agree.

Regards,
-- 
Daiki Ueno