From: Ævar Arnfjörð Bjarmason Date: Fri, 06 Aug 2010 17:01:19 GMT Subject: Re: Cooking of the ab/i18n series Message-ID: In-Reply-To: <7viq3nagje.fsf@alter.siamese.dyndns.org> On Fri, Aug 6, 2010 at 15:48, Junio C Hamano wrote: > Ævar Arnfjörð Bjarmason writes: > >> On Fri, Aug 6, 2010 at 13:30, Junio C Hamano wrote: >>> That is one good example.  Perhaps we can get a list of messages that we >>> can place in Documentation/ area (e.g. "'Not up-to-date' - this message is >>> given when you have local changes in a file in the working tree; given by >>> command X, Y and Z") out of that effort for free?  Perhaps such a list can >>> help us verify that i18n does not break plumbing output (because the list >>> does not contain plumbing messages)? >> >> We'd get this sort of list out of "TRANSLATORS:" comments for >> free. They're automatically extracted and presented to translators and >> others with the xgettext program. >> >> Maintaining a list of messages in Documentation/ somewhere that's >> bound to get out of date with the source code doesn't make sense given >> the TRANSLATORS support. > > Read it again---I didn't say "maintaining" a list at all; we are saying > the same thing more or less ;-)  You might need to massage the output from > TRANSLATORS: comment to a more readable form suitable for inclusion in the > documentation (depending on how that thing looks like), though. Ah yes. I didn't read it carefully enough. Yeah, if we're just talking about autogeneration it isn't hard to get a list of all translatable strings into a single ASCIIDOC page. I plan to write some translator documentation once this gets in and we start having people submit translations. E.g. a document that lists some of the core Git concepts that the translator will need to translate (e.g. "pull", "push", "commit", "tree", "object" etc.).