From: Jamie Kahn Genet on
Warren Oates <warren.oates(a)gmail.com> wrote:

> In article <1jfj839.io8x0n4b74zuN%jamiekg(a)wizardling.geek.nz>,
> jamiekg(a)wizardling.geek.nz (Jamie Kahn Genet) wrote:
>
> > I do. It's called MacSOUP. Usenet is plain text. NOT HTML.
>
> I don't see any HTML here.

Then your client either supports and is rendering the HTML (ugg), or
shows only the plain text version. Either way - what value does HTML add
to Usenet? Or most email for that matter? The answer is extremely
little. So little that it's simply more trouble than it's worth IMO.

I don't want inconsistent fonts, sizes, colours, etc. If you can't make
your point in plain text, then loud fonts and colours sure as hell won't
help. Either what you're saying is of value or not. Jazzed up
space-wasting HTML can't disguise a lack of content.
--
If you're not part of the solution, you're part of the precipitate.
From: Michael Narciso on
On 2010-03-17 23:37:59 -0400, Jamie Kahn Genet said:

> Warren Oates <warren.oates(a)gmail.com> wrote:
>
>> In article <1jfj839.io8x0n4b74zuN%jamiekg(a)wizardling.geek.nz>,
>> jamiekg(a)wizardling.geek.nz (Jamie Kahn Genet) wrote:
>>
>>> I do. It's called MacSOUP. Usenet is plain text. NOT HTML.
>>
>> I don't see any HTML here.
>
> Then your client either supports and is rendering the HTML (ugg), or
> shows only the plain text version. Either way - what value does HTML add
> to Usenet? Or most email for that matter? The answer is extremely
> little. So little that it's simply more trouble than it's worth IMO.
>
> I don't want inconsistent fonts, sizes, colours, etc. If you can't make
> your point in plain text, then loud fonts and colours sure as hell won't
> help. Either what you're saying is of value or not. Jazzed up
> space-wasting HTML can't disguise a lack of content.

Just so I'm clear... is Unison 2 the culprit? There's a 'Make Plain
Text Button' here but it's greyed out and it won't let me click it. Is
this posting in HTML?

From: Jamie Kahn Genet on
Michael Narciso <volcomjerk(a)gmail.com> wrote:

> On 2010-03-17 23:37:59 -0400, Jamie Kahn Genet said:
>
> > Warren Oates <warren.oates(a)gmail.com> wrote:
> >
> >> In article <1jfj839.io8x0n4b74zuN%jamiekg(a)wizardling.geek.nz>,
> >> jamiekg(a)wizardling.geek.nz (Jamie Kahn Genet) wrote:
> >>
> >>> I do. It's called MacSOUP. Usenet is plain text. NOT HTML.
> >>
> >> I don't see any HTML here.
> >
> > Then your client either supports and is rendering the HTML (ugg), or
> > shows only the plain text version. Either way - what value does HTML add
> > to Usenet? Or most email for that matter? The answer is extremely
> > little. So little that it's simply more trouble than it's worth IMO.
> >
> > I don't want inconsistent fonts, sizes, colours, etc. If you can't make
> > your point in plain text, then loud fonts and colours sure as hell won't
> > help. Either what you're saying is of value or not. Jazzed up
> > space-wasting HTML can't disguise a lack of content.
>
> Just so I'm clear... is Unison 2 the culprit? There's a 'Make Plain
> Text Button' here but it's greyed out and it won't let me click it. Is
> this posting in HTML?

Nope, it's plain text :-)
--
If you're not part of the solution, you're part of the precipitate.
From: David Empson on
Michael Narciso <volcomjerk(a)gmail.com> wrote:

> On 2010-03-17 23:37:59 -0400, Jamie Kahn Genet said:
>
> > Warren Oates <warren.oates(a)gmail.com> wrote:
> >
> >> In article <1jfj839.io8x0n4b74zuN%jamiekg(a)wizardling.geek.nz>,
> >> jamiekg(a)wizardling.geek.nz (Jamie Kahn Genet) wrote:
> >>
> >>> I do. It's called MacSOUP. Usenet is plain text. NOT HTML.
> >>
> >> I don't see any HTML here.
> >
> > Then your client either supports and is rendering the HTML (ugg), or
> > shows only the plain text version. Either way - what value does HTML add
> > to Usenet? Or most email for that matter? The answer is extremely
> > little. So little that it's simply more trouble than it's worth IMO.
> >
> > I don't want inconsistent fonts, sizes, colours, etc. If you can't make
> > your point in plain text, then loud fonts and colours sure as hell won't
> > help. Either what you're saying is of value or not. Jazzed up
> > space-wasting HTML can't disguise a lack of content.
>
> Just so I'm clear... is Unison 2 the culprit? There's a 'Make Plain
> Text Button' here but it's greyed out and it won't let me click it. Is
> this posting in HTML?

No, that one was plain text.

The previous ones were multi-part MIME with plain text and HTML parts.

It might depend on the content, e.g. if you copy and paste text from
somewhere else, Unison might decide it needs to preserve the fonts and
therefore posts in HTML and plain text.

(I can't tell, as I can't even use Unison to test it - it isn't
compatible with my ISP's news server, as I noted elsewhere in this
thread.)

The previous post included a web link - perhaps that is what triggered
the HTML?

--
David Empson
dempson(a)actrix.gen.nz
From: Michael Narciso on
On 2010-03-20 07:36:44 -0400, David Empson said:

> Michael Narciso <volcomjerk(a)gmail.com> wrote:
>
>> On 2010-03-17 23:37:59 -0400, Jamie Kahn Genet said:
>>
>>> Warren Oates <warren.oates(a)gmail.com> wrote:
>>>
>>>> In article <1jfj839.io8x0n4b74zuN%jamiekg(a)wizardling.geek.nz>,
>>>> jamiekg(a)wizardling.geek.nz (Jamie Kahn Genet) wrote:
>>>>
>>>>> I do. It's called MacSOUP. Usenet is plain text. NOT HTML.
>>>>
>>>> I don't see any HTML here.
>>>
>>> Then your client either supports and is rendering the HTML (ugg), or
>>> shows only the plain text version. Either way - what value does HTML add
>>> to Usenet? Or most email for that matter? The answer is extremely
>>> little. So little that it's simply more trouble than it's worth IMO.
>>>
>>> I don't want inconsistent fonts, sizes, colours, etc. If you can't make
>>> your point in plain text, then loud fonts and colours sure as hell won't
>>> help. Either what you're saying is of value or not. Jazzed up
>>> space-wasting HTML can't disguise a lack of content.
>>
>> Just so I'm clear... is Unison 2 the culprit? There's a 'Make Plain
>> Text Button' here but it's greyed out and it won't let me click it. Is
>> this posting in HTML?
>
> No, that one was plain text.
>
> The previous ones were multi-part MIME with plain text and HTML parts.
>
> It might depend on the content, e.g. if you copy and paste text from
> somewhere else, Unison might decide it needs to preserve the fonts and
> therefore posts in HTML and plain text.
>
> (I can't tell, as I can't even use Unison to test it - it isn't
> compatible with my ISP's news server, as I noted elsewhere in this
> thread.)
>
> The previous post included a web link - perhaps that is what triggered
> the HTML?

I guess it was the link. I'll try to keep a look out to see if I'm
posting in HTML or Plain Text. I'd prefer to post to plain-text if I
can help it.

Thanks for verifying this.