On Wed, May 28, 2003 at 10:56:32PM +0200, Rüdiger Kuhlmann wrote:
> >--[Denis Barbier]--<[EMAIL PROTECTED]>
> > On Sun, May 18, 2003 at 11:39:09PM +0200, Denis Barbier wrote:
>
> > Many thanks to those who replied, here is an updated list.
>
> Btw, did you also check for packages that don't conta
>--[Denis Barbier]--<[EMAIL PROTECTED]>
> On Sun, May 18, 2003 at 11:39:09PM +0200, Denis Barbier wrote:
> Many thanks to those who replied, here is an updated list.
Btw, did you also check for packages that don't contain the upstream
provided translated man pages? Because often, upstream doesn't
On Sun, May 18, 2003 at 11:39:09PM +0200, Denis Barbier wrote:
> Hi,
>
> below is a list of source packages containing gettext .po files,
> for which binary packages do not ship any file under a LC_MESSAGES
> directory.
> There might be several reasons:
> a. Programs use gettext PO files to stor
[EMAIL PROTECTED] (Denis Barbier) writes:
> Hi,
Hi,
> below is a list of source packages containing gettext .po files,
> for which binary packages do not ship any file under a LC_MESSAGES
> directory.
> There might be several reasons:
> a. Programs use gettext PO files to store translations bu
Hello.
On Sun, 18 May, 2003 at 23:39:09 +0200, Denis Barbier wrote:
> There might be several reasons:
> b. PO files are not used, e.g. they are test files (po-debconf)
...
> zssh
Upstream original source contains the full lrzsz source tree.
zssh isn't gettextized, but lrzsz is (that is wh
Hi,
below is a list of source packages containing gettext .po files,
for which binary packages do not ship any file under a LC_MESSAGES
directory.
There might be several reasons:
a. Programs use gettext PO files to store translations but manage them
with other tools at run time (eg. abiword
6 matches
Mail list logo
