Re: Testing SNAP v1.1.3, take two

["Marc S. Ressl" <mressl@gmail.com>]

On 29 feb, 16:13, dog_...@macgui.com (D Finnigan) wrote:
> Linards Ticmanis wrote:
> > On 02/28/2012 08:11 PM, D Finnigan wrote:
>
> >> It's whatever you get when you hold option and type the keys on a IIgs.
> >> Holding Shift-Option gets you MouseText. Unfortunately, SNAP doesn't do
> >> any
> >> MIME encoding, so when these articles get injected.... "What should we do
> >> with these characters out of ASCII range? Who knows?"
>
> > You might want to include a "Content-Type:" header with some value that
> > makes sense.
>
> > Or if you want to be fancy, convert from the IIgs native encoding to
> > something smarter like ISO-8859-1 or even Unicode (does NNTP handle
> > UTF-8 these days?). As long as you stick to a 256 or less character set
> > (i.e. the native GSOS encoding, whatever that is...) you should be able
> > to do it with a very simple table.
>
> Mr. Wannop read your suggestion, and I also made a suggestion to him.
>
> From the looks of things, having the ability to post articles with MouseText
> characters is, practically speaking, useless (even though SNAP can properly
> parse and display its own articles with those characters). The next version
> of SNAP is going to filter out these non-standard characters.
>
> As for UTF-8 and NNTP, the standard is built around 7-bit ASCII messages.
> Anything else is supposed to be encoded, whether by quoted-printable or
> base64. Of course people write newsreaders (and we mostly get this with
> non-Latin character set languages) that post raw, unencoded 8-bit data. It's
> a "naughty" thing to do, but most article parsers can handle it if the
> programmer is clever enough to use heuristics.
>
> --
> ]DF$
> Mac GUI Vault - A source for retro Apple II and
> Macintosh computing.http://macgui.com/vault/

...

Somebody seems to be having fun :-).

With the best wishes,

Marc.-