Re: lynx-dev Posted message has no text error message

[David Woolley]

> A little who-where-how on the "to specify the correct locale," please.
> If I run "locale" without arguments it reports "japanese" for all
> categories except LC_ALL=, which is blank.  Are you saying the user
> needs to do something, or Lynx needs to do something?

This is dependent on a C library that understands locale; in particular,
a statically linked US version of the code is unlikely to understand
Japanese.  Actually, Japanese may be a problem anyway, as how do you
classify 8 bit characters.

In principle you set the language in the environment, but this assumes
that the program doesn't override it (overriding may be desirable because
the program is dealing with canonical form data, like Postscript) and that
the libraries know what to do.

If there are problems with libraries not knowing what to do, the best 
solution is probably to include replacement modules in the Lynx source.

> 
> Is Klaus W., or someone familiar with the news RFCs, on the list?  By
> changing that to '!isspace(c)', I worry we could be opening Lynx's news
> handling up to abuse, i.e., ability to post inappropriate control/escape
> sequences.  (I'm asking, not complaining, nor blaming, nor arguing.)

The main risk is probably from sending escape sequences to terminals not
to the news protocol itself, but this is the sort of reason why I think
the isspace hack is short sighted.