[Top][All Lists]

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

Re: lynx-dev Do we need [Y] AND [N] strings? Could they be [Y/N]?

From: dickey
Subject: Re: lynx-dev Do we need [Y] AND [N] strings? Could they be [Y/N]?
Date: Sat, 21 Nov 1998 08:15:20 -0500 (EST)

> > on top of that we need a utility function (on my list) to prompt for 
> > yes/no/cancel. 
> Oh, yes, been waiting for something like that.  Won't do anything then 
> since a much better solution is in the making. 

ok (we already have one variant - I was looking at it last night), but it's
a little incompatible with the other uses.
> > > There are a few instances like the following:  
> > >    (WAIS Index)  
> > >   WAIS Index:  
> > >    WAIS Index.\n  
> > > I haven't looked at the code yet, but I suspect the same string  
> > > could be used in all three situations.  Or perhaps only the  
> > > "WAIS Index" could be within the gettext() call.  
> >  
> > that is what I would do - and make the string a #define in LYMessages_en.h 
> Okay, in general, then, I'll move in that direction.  As for the 
> example I gave (WAIS), I propose that actually we remove gettext from 
> all of them since WAIS is all but dead as a protocol.  The strings 
> are probably more understandable in English than translated anyway. 
> I'll also be reviewing the lynx.po file from that point of view, i.e., 
> checking for validity as a target for translation, as well. 

if we can reduce the list of filenames to 1024 characters, that will
let us use the Solaris xgettext code - iirc we are around 1350 now.
> __Henry  

Thomas E. Dickey

reply via email to

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