Bug#184774: Buttons not translated
On Mon, 2003-05-05 at 09:10, Martin Sjögren wrote:
> mån 2003-05-05 klockan 09.22 skrev Denis Barbier:
> > On Mon, May 05, 2003 at 08:01:28AM +0100, Alastair McKinstry wrote:
> > > Ok,
> > >
> > > As newt maintainer, I'm fixing this bug upstream, in newt (if Redhat,
> > > the original newt upstream, will accept the fix).
>
> Do you mean in whiptail?
>
> > > However, the simplest method of doing so in newt is gettext support, but
> > > I don't wish to pull two i18n schemes into debian-installer.
> > >
> > > So, I'm proposing that libnewt-pic, which is used to build cdebconf, is
> > > built without gettext support, and that the dialogs are constructed
> > > "manually" in the cdebconf newt frontend with the button text pulled
> > > from the debconf template.
> > >
> > > Does anybody have any objections/comments ?
>
> Well, I don't see a reason why whiptail cannot use gettext, it will not
> touch libnewt as such.
>
> <Next>/<Back> is what RH netinstall uses, IIRC. And, you know, the
> button texts aren't fixed in libnewt, they are however fixed in
> whiptail. I intend to change the newt frontend to say <Next>/<Prev>
> instead of <OK>/<Cancel>, because I think it makes more sense.
>
>
I should examine the sources of the packages I take over more closely
:-). It appears that the buttons are in dialogboxes.o, linked into
everything _but_ libnewt.
So, yes, whiptail, the whiptail tcl and python modules will be
translated via gettext, and this doesn't affect libnewt.
Because the strings are common to packages dependent on libnewt, the po
files themselves may go into libnewt, but libnewt will not depend on
gettext.
> /Martin
- Alastair
Reply to: