bug-gnu-utils
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Bug#114019: gettextize will not preserve changes to po/Makefile.in.in, a


From: Santiago Vila
Subject: Bug#114019: gettextize will not preserve changes to po/Makefile.in.in, and has no way to be told of extra keywords for xgettext (fwd)
Date: Mon, 1 Oct 2001 11:03:13 +0200 (CEST)

Hello.

Received this from the Debian Bug System.
[ Please keep the Cc: lines ].

Thanks.

---------- Forwarded message ----------
Date: Sun, 30 Sep 2001 20:15:02 -0300
From: Henrique de Moraes Holschuh <address@hidden>
To: Debian Bug Tracking System <address@hidden>
Subject: Bug#114019: gettextize will not preserve changes to
    po/Makefile.in.in, and has no way to be told of extra keywords for xgettext

Package: gettext
Version: 0.10.40-1
Severity: important

Some programs need to change the invocation of gettext() from _() to
something (e.g. tue to the DES libraries of kerberos using _() in some
incarnations).

gettextize will lose that information, which is in po/Makefile.in.in. It
should have an option switch to inform it of a new set of keywords to use
instead of the default _() and N_() in po/Makefile.in.in's invocation of
xgettext.

Since there is no workaround against this bug and it causes silent breakage
that is very unlikely to be noticed before it causes damage and headaches,
I tagged it 'important'.

-- System Information
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux godzillah.khazad-dum.debian.net 2.2.19 #1 Thu Mar 29 19:31:38 BRT 
2001 i586
Locale: LANG=pt_BR, LC_CTYPE=pt_BR

Versions of packages gettext depends on:
ii  gettext-base                  0.10.40-1  GNU Internationalization utilities
hi  libc6                         2.2.4-1    GNU C Library: Shared libraries an

-- 
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh




reply via email to

[Prev in Thread] Current Thread [Next in Thread]