Re: gettext

[Christian Rose <menthos menthos com>]

"Tomas V.V.Cox" wrote:
> > >From the translators perspective, all he has to do is running a script
> > that extracts those messages by using xgettext. Such tools already exist
> > in the form of the GNOME xml-i18n-tools suite, which are GNOME tools
> > acting as wrappers around gettext, and adding support for more types of
> > message sources.
> > If xgettext itself does not grok how to parse .php files in the search
> > for _() messages, this support can be added to xml-i18n-tools (it
> > already supports .c, .cpp, .desktop, .oaf, .glade, .xml, and mime-type
> > files and who knows what =).
> 
> Sometime ago, I started to build a web frontend to the .po files. With
> it, people could work on translations directly from the web without
> nothing else than a web browser.
> Now the proyect is "vaporware", because there is only a ".po to SQL"
> done, but if you think that this idea could help us, I/we can start
> working on it again.

Personally, I'm very fond of using cvs, and I think it was said
previously that the gnome.org pages would probably be maintained as a
module in gnome cvs (I think they already are?).

My own opinion is that adding the "update-via-browser" concept for the
gnome.org pages is probably not worth it - all translators have direct
or indirect cvs access today (via someone else), and having to add a
frontend for authentication and a cvs checkin system for the
"update-via-browser" seems messy.

But your code could probably very well be used in other translation
projects that do not use cvs. But then I guess this discussion really
belongs on gnome-i18n gnome org  Feel free to join that list =)


Christian