XPost: alt.comp.os.windows-10, alt.comp.microsoft.windows
From: this@ddress.is.invalid
Herbert Kleebauer wrote:
> On 12/31/2025 7:21 PM, Marian wrote:
>
> > Bear in mind there is much more than just Unicode characters in
> > pasted web-page text as Unicode is only the container; the real trouble
> > comes from the variety of characters inside it such as zero-width
> > spaces & joiners, directional control characters, soft hyphens, etc.
>
> I don't understand the problem. In these days, (nearly) any web page
> and usnet posting uses utf-8 character encoding. Also your posting
> uses utf-8;
>
> Content-Type: text/plain; charset=UTF-8; format=flowed
> User-Agent: tin/1.6.2-20030910 ("Pabbay") (UNIX) (CYGWIN_NT-10
0-WOW/2.8.0(0.309/5/3) (i686)) Hamster/2.0.2.2
I don't know whether or not he used UTF-8, but, as with all his
postings, these headers are fabricated/bogus.
For example the 'User-Agent:' header is stolen from my postings
(extremely unlikely that anyone else has that exact combination of
newsreader/local server). And I normally don't use any 'Content-Type:'
header and if I do, it's not UTF-8, nor format=flowed, so that header is
fabricated/ bogus as well.
He claims you're partly responsible for him generating this crap :-) :
Message-ID: <10j7auc$mji$1@nnrp.usenet.blueworldhosting.com>
> There shouldn't be any problem when you copy text from a web page and
> past it into an usnet posting. There is only a problem if you
> convert the utf-8 text into "something else" and then paste it
> into the posting. You don't solve a problem, you create a problem.
Creating problems is his purpose in life.
> Just post a link to a web page which has a problem with copy&paste
> text into an usnet posting.
Don't hold your breath.
--- SoupGate-Win32 v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)
|
