Re: Flynx-dev Re: msg00798.html (was: 0x2276 handling)

[Nelson Henry Eric]

> choices are to 1) force a download offer, 2) fill the screen with Uhh
> characters (with overhead to do those conversions, that don't yield any
> readability), or 3) ignore the charset information and set an assumed
> charset which should be "safe", e.g., iso-8859-1, or whatever the user
> has set as assumed in conjunction with the current Display Character Set.=

One vote here for status quo, #3.  Reasoning is simply that current Display
Character Set has been chosen by the user to be the best choice for his
working environment (the real world).

> no good alternatives, and so no choice is good.  I like forcing a
> download offer when thinking about it tonight, but would rather not

Means I'd have to do a lot of downloading.  If #1 is beneficial to the
majority of users, it would be desirable from this corner to at least
then offer #3 automatically in the download option menu.

> Set, and it should not fail in that case (and didn't, as far as I know,
> in v2.7.2, nor would I expect it to in v2.8. I won't even try to

I knew you were using Win32, so I wanted to speak from CJK usage on that
port, too, but as I stated, I have not had a chance to update from
2.7.1ac-0.81.  I think Klaus debugged this META problem around ac-0.98,
before 2.7.2.  There has been no problem since on SunOS, still my port of
choice.

> address the gibberish followups he posted, though.  Sorry :).

Either you've lost your superb sense of humor, or my stories aren't
funny enough anymore.  I'll work on it :).

__Henry