[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
lynx-dev gettext yes/no (was: structured description of lynx.cfg setting
From: |
Webmaster Jim |
Subject: |
lynx-dev gettext yes/no (was: structured description of lynx.cfg settings) |
Date: |
Mon, 3 May 1999 12:54:28 -0400 |
> > Do you consider adding NLS support for data input a new feature ot a bug
> > fix? I haven't gotten around to it, and think that gettext is broken if
> > it asks a French user (o/n) but accepts (y/n).
> I may have missed an occurrence, but HTConfirmDefault does this now:
> PUBLIC BOOL HTConfirmDefault ARGS2(CONST char *, Msg, int, Dft)
> {
> char *msg_yes = gettext("yes");
> char *msg_no = gettext("no");
> int result = -1;
>
> ...
> } else if (TOUPPER(c) == TOUPPER(*msg_yes)) {
> result = YES;
> } else if (TOUPPER(c) == TOUPPER(*msg_no)) {
> return(NO);
Oops I missed that; thought it accepted the english characters even
though the message was translated.
Small remaining issue there then, for questions with more than Y/N, such
as yes/no/always/never:
HTAlert.c
---------
if(!LYAcceptAllCookies) {
char *message = 0;
HTSprintf(&message, ADVANCED_COOKIE_CONFIRMATION,
server, namelen, name, valuelen, value);
_statusline(message);
FREE(message);
}
[...]
switch(TOUPPER(ch)) {
case 'A':
/*
** Set to accept all cookies for this domain.
*/
de->bv = ACCEPT_ALWAYS;
HTUserMsg2(ALWAYS_ALLOWING_COOKIES, de->domain);
return TRUE;
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)
------
<http://www.cs.indiana.edu/picons/db/users/us/md/lib/bcpl/jspath/face.xbm>
<http://www.altavista.com/cgi-bin/query?q=%22web+home+for+jim+spath%22>
Marvin the Paranoid Android says:
My capacity for happiness you could fit in a matchbox...
(without taking the matches out first)