|
|
Posted by NRen2k5 on 02/09/07 23:22
Tim McNamara wrote:
> In article <wrNyh.14423$tt1.63173@wagner.videotron.net>,
> NRen2k5 <nomore@email.com> wrote:
>
>> J.J. O'Shea wrote:
>>> On Wed, 7 Feb 2007 14:24:58 -0500, Michelle Steiner wrote (in
>>> article <michelle-3D0DB2.12245807022007@news.east.cox.net>):
>>>
>>>> In article <Topyh.46212$3D6.1944022@weber.videotron.net>,
>>>> NRen2k5 <nomore@email.com> wrote:
>>>>
>>>>> Please don't try to use curly quotes on Usenet. They don't always
>>>>> work. Stick with pure ASCII.
>>>> I copied and pasted the article without attempting to edit it. I
>>>> did not notice that they had used curly quotes.
>>>>
>>>>
>>> You gotta consider who's complaining.
>>>
>>> And the simple fact that if only he had a real newsreader, he'd not
>>> be complaining, as real newsreaders showed either straight quotes
>>> or knew enough to show curly quotes and not some fool escape code.
>>>
>>> Ignore the twit.
>> You're a moron.
>>
>> "Some fool escape code"??? LMAO! What are you going on about?
>>
>> It's perfectly fucking simple, but I'll repeat it for the mentally
>> challenged anyway: Michelle's newsreader is fucked up; it's not using
>> a proper character encoding; nonstandard characters such as curly
>> quotes in her posts show up as other characters instead - in my case
>> they're appearing as superscript numerals.
>
> Since the post looked fine in other newsreaders, the problem appears to
> be yours and not Michelle's.
The post looked fine in SOME other newsreaders. It did not in others.
The problem is entirely Michelle's; her newsreader isn't declaring the
character set it's using. That leaves it up to chance whether other
newsreaders will interpret any non-ASCII characters she posts as she
intends them to.
<Childish retort snipped>
Navigation:
[Reply to this message]
|