On Thu, Jun 29, 2006 at 08:17:09AM +0200, Martin Pitt wrote:
> > So, can you explain for me why "the POT file needs a header to be
> > imported properly"? Imported into what?
>
> Rosetta so far, but it is basically the same if you start a new
> translation manually: a .po file needs a correct h
Hi Nathan,
Nathan Scott [2006-06-29 13:19 +1000]:
> - the acl.pot file is actually only used as the starting point of
> a new translation. It exists only in the source package, and is
> not installed anywhere, ever. Its generated from the source code.
Correct. We use the file generated at b
Hi Nathan,
Nathan Scott [2006-06-29 12:02 +1000]:
> > The POT file created by the acl package is broken since it does not
> > have a proper header.
>
> Well, that doesn't strictly make it "broken", but no matter.
Well, true, but since it is meant to be a template for translators, it
should have
Hello again Martin,
On Wed, Jun 28, 2006 at 09:00:51AM +0200, Martin Pitt wrote:
> The POT file created by the acl package is broken since it does not
> have a proper header.
OK, I had a closer look, and now I'm even more confused. ;)
First some i18n refresher notes -
- the acl.pot file is actu
Hello Martin,
On Wed, Jun 28, 2006 at 09:00:51AM +0200, Martin Pitt wrote:
> Package: acl
> Version: 2.2.39-1
> Tags: patch
>
> The POT file created by the acl package is broken since it does not
> have a proper header.
Well, that doesn't strictly make it "broken", but no matter.
> We fixed thi
Package: acl
Version: 2.2.39-1
Tags: patch
The POT file created by the acl package is broken since it does not
have a proper header. We fixed this by removing the --omit-header
argument to xgettext and also updating the POT file on package build,
so that it is always current.
Thank you,
Martin
-
6 matches
Mail list logo
