Re: [PATCH 1/5] Internationalization of git-gui
- From
Johannes Schindelin <johannes.schindelin@gmx.de>
- Date
- Jul 22, 2007, 14:29 UTC
- Message-ID
- <Pine.LNX.4.64.0707221526080.14781@racer.site>
- In-Reply-To
- <200707221535.46422.stimming@tuhh.de>
Hi,
On Sun, 22 Jul 2007, Christian Stimming wrote:
Show 12 quoted lines
> Am Samstag, 21. Juli 2007 23:28 schrieb Junio C Hamano: > > > - The i18n coordinator (could be Shawn but anybody else can > > volunteer; as things stand, I think Christian and Johannes > > are doing this): responsible for running "make > > po/git-gui.pot; make update-po" from time to time in order to > > keep po/*.po in sync with the vocabulary. > > Actually, please DO NOT RUN update-po except right before a new tarball > is being packaged and distributed! It sucks royally if I have updated my > de.po translation, only to discover someone has run update-po on the > server and I have to figure out how to get out of the de.po conflicts.
I plan to work on that. It seems to be pretty easy to define a sane merge behaviour, and we have gitattributes: by setting "*.po diff=po merge=po" we can provide a custom merge program, just for .po files.
Show 17 quoted lines
> > - Translators (one for each language): responsible for updating > > po/xx.po file; > > > > initially, start by copying po/git-gui.pot to create > > po/xx.po; > > > > maintainance of "glossary" part of po/xx.po could also be > > made this person's responsibility instead of i18n > > coordinator's. > > > > This way, the translators do not have to be so familiar with the > > gettext toolchain nor even have to have gettext installed. > > Translators who are unfamiliar with gettext are a mixed blessing. [...] > I wouldn't spent too much effort to enable translation work without > gettext tools; instead, I'd rather encourage to optimize the setup for > those translators that have the full toolchain available.
You need not work on the "without gettext toolchain" part; I will. Let's see how far I get ;-)
Ciao, Dscho