[pacman-dev] Deadline for translations?

[Dan McGee]

On 2/12/07, Dan McGee <dpmcgee at gmail.com> wrote:
> On 2/12/07, Pierre Schmitz <pierre at archlinux.de> wrote:
> > Am Montag, 12. Februar 2007 16:06:17 schrieb Alessio 'mOLOk' Bolognino:
> > > 2007/2/12, Pierre Schmitz <pierre at archlinux.de>:
> > > > Am Sonntag, 11. Februar 2007 23:24:20 schrieb Dan McGee:
> > > > > That would be great. Keep in mind that having a good start to the
> > > > > translation helps a lot, obviously messages will change but the
> > > > > translation tools rectify that. There have been a few minor string
> > > > > changes since we last updated the po files, but nothing huge.
> > > >
> > > > How should I synchronize to the latest English translation?
> > >
> > > I think you are looking for msgmerge (in the gettext package), as easy
> > > to use as:
> > > $> msgmerge it.po pacman.pot > it.new.po
> >
> > I think I got it with "make update-po" (as described in "translation-help").
> > The result wasn`t allways optimal but a good start.
>
> This seems to be the best way I know of, because you need to update
> the .pot file as well before you can do a merge. I will try to put
> some updated pot files soon into CVS, but you can always take this
> step on your own.

Just discovered this- "make libalpm.pot-update" works to just update
the pot file. This can then be followed by a "make it.po-update" or
any other language to update the respective po file.

> > Another question: What about all the blanks within the strings? Are they used
> > for proper indention? For example "Version      :" What should we do if the
> > translated text is longer than the English one (including spaces)?
>
> Yes, they are usually for proper indentation and spacing. Sometimes
> seeing them in the context of the code may be helpful, note that their
> positions are listed in the po files. The spaces in the instance you
> mentioned above are not crucial, the biggest idea is simply making
> sure all of those labels are the same length.
>
> -Dan
>