Question: Do Winston's headers cause charset issues for anyone else?

Question: 
Do Winston's headers cause charset issues for anyone else? 
Or just me?

I am trying to understand something about how different newsreaders handle
malformed headers because my home-grown "newsreader" has "problems" when
responding to Winston's posts due to the way he formats his "FROM" header.
 From: ...w¡ñ§±¤ñ <[email protected]>

That line apparently contains non-ASCII characters in the display name:
 ¡ (U+00A1)
 ñ (U+00F1)
 § (U+00A7)
 ± (U+00B1)
 ¤ (U+00A4)
 another ñ (U+00F1)

When I reply to posts from Winston (the ones where his display name
contains characters like "w!n§±¤n"), my own outgoing article sometimes gets
corrupted on the way out. The corruption seems to happen, I think, because
Winston's display name or headers contain raw 8-bit characters that are not
valid UTF-8 and not MIME-encoded.

Usenet (like email) requires that all headers must be pure ASCII unless
they use MIME encoded-words, which means Winston's headers maybe should be
 From: =?UTF-8?Q?w=C2=A1=C3=B1=C2=A7=C2=B1=C2=A4=C3=B1?= <[email protected]>
This is fully legal for Usenet and will not trigger nntp server rewrites.

I wrote my own newsreader so I manually enforce strict 7-bit ASCII in my
outgoing posts by the use of an extensive shortcuts.xml conversion macro.

However, when Winston's illegal header bytes get copied into my attribution
line or reply headers, some NNTP servers rewrite the article to "fix" the
mismatch, which ends up mangling my otherwise clean pure-7-bit ASCII text.

My question of others, since you're using "normal" newsreaders, is:
 Q: Do any of you see charset or encoding issues when replying to Winston's
    posts, or do your newsreaders and servers silently fix the illegal 
    bytes so you never notice?

I am trying to determine whether this is something unique to my strict
ASCII workflow, or whether other clients also have to deal with it.

Thanks for any insight.

Note that I'm implementing the following shortcuts.xml to fix this, 
but nobody else will be using that conversion so it's just an N.B.

<!-- Remove Unicode garbage from quoted Usenet 'X wrote:' lines --> 
<!-- (e.g., Winston's illegal headers) so my posts stay 7-bit clean -->
 <ReplaceRE Find="[^\x00-\x7F]" Replace="" />
 <ReplaceRE Find="^.*wrote:" Replace="Winston wrote:" />
 <ReplaceRE Find="^(References|In-Reply-To):.*" Replace="" />
-- 
When you write your own newsreader, you have to do everything yourself.