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

On 3/12/2026 11:24 AM, MikeS wrote:
> On 12/03/2026 07:08, ...w¡ñ§±¤ñ wrote:
>> On 3/11/2026 5:32 PM, Maria Sophia wrote:
>>> 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)
>>
>> w = standard lower case w keystroke
>> ¡ = Alt 0161
>> ñ = Alt 0241
>> § = Alt 0167  or § = Alt 21
>> ± = Alt 0177
>> ¤ = Alt 0164
>> ñ = Alt 0241
>>
>> All from one or more fonts available in Character Map.
>>   - I've come across other folks that use some available character 
>> codes that appear blank - just copy the code and paste into a field to 
>> meet the '*' required character entry.
>>
>>
> I also see your name as ...w¡ñ§±¤ñ (in Betterbird). It doesn't bother me 
> unduly but it has puzzled me for a while. May I ask what you are doing 
> and why not simply use winston as in your email address?

Have used that form for nntp and signature since 1998
Html nntp, Text nntp[1], private nntp groups, private list servers, 
private web groups, blogging...

[1] text nntp(e.g. Eternal Sept. like servers - no HTML formatting 
composition) users are the only source where questions, criticism, 
comments occur...but less than 5% of where 'it's' being used.

<g>Before 1998, the nomenclature was slightly longer
   =>  W¡ñ§±¤ñ¬Ößóògîë


-- 
...w¡ñ§±¤ñ