lynx-dev Re: gettext yes/no (was: structured description of lynx.cfg settings)

[Webmaster Jim]

On Mon, May 03, 1999 at 01:38:49PM -0400, address@hidden wrote:
> >             case 'N': 
> >             case 7:     /* Ctrl-G */ 
> >             case 3:     /* Ctrl-C */ 
> >                 /* 
> >                 **  Reject the cookie. 
> >                 */ 
> >                 HTUserMsg(REJECTING_COOKIE); 
> >  
> > Since these cases depend on first-letter, can we add numbers so that NLS 
> > messages can be clearer: 
> > Allow? (Y/N/Always/Never) => Allow? (1=Y/2=N/3=Always/4=Never) 
> that sounds reasonable (I was only thinking in terms of a unique
> abbreviation).

There are other cases of multiple input characters that could be altered
for gettext, such as these references in LYMessages.h:

#define HEAD_D_L_OR_CANCEL \
 gettext("Send HEAD request for D)ocument or L)ink, or C)ancel? (d,l,c): ")
 gettext("Send HEAD request for 1)Document or 2)Link or 3)Cancel (1,2,3): ")

#define MSG_DOWNLOAD_OR_CANCEL gettext("%s  D)ownload, or C)ancel")
                               gettext("%s  1)Download, or 2)Cancel")

#define PROCEED_OR_CANCEL gettext("P)roceed, or C)ancel ")
                          gettext("1)Proceed, or 2)Cancel ")

++++++++++++++++++++++++++++
Marvin the Paranoid Android.