threads / discuss / 48584

protocol for updating .po gettext files?

Subject: protocol for updating .po gettext files?

## tl;dr

2 messages between May 28, 2018 and May 28, 2018.

replies: 1people: 2as markdown or json

Robert P. J. Day· May 28, 2018, 11:56 UTC · lore

   i was going to submit a minor patch to fix grammar here:

builtin/init-db.c: warning(_("templates not found %s"), template_dir);

as it should display "templates not found in %s" to be consistent with other messages, but i know from nothing about .po files, so does one also have to update those, or how does that work?

rday

-- 
========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                  http://crashcourse.ca/dokuwiki

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================

Junio C Hamano· May 28, 2018, 13:47 UTC · re: Robert P. J. Day · lore

Re: protocol for updating .po gettext files?

"Robert P. J. Day" <rpjday@crashcourse.ca> writes:

Show 7 quoted lines

>    i was going to submit a minor patch to fix grammar here:
>
> builtin/init-db.c: warning(_("templates not found %s"), template_dir);
>
> as it should display "templates not found in %s" to be consistent with
> other messages, but i know from nothing about .po files, so does one
> also have to update those, or how does that work?

You as a developer generally don't. Instead, you just update the code i.e.

	-	warning(_("t not found %s"), t);
	+	warning(_("t not found in %s"), t);

and leave it up to the i18n coordinator to update *.pot and *.po so that localization teams can work on it, which all happens closer to the next release.

I think po/README has a bit more details describing which part is handled by whom.