Microsoft might change the cadence of its Windows 10 feature rollouts starting next year in order to help prioritize Windows 10X development.

On 21.07.20 15:53, 😉 Good Guy 😉 wrote:
You should know the drill by now. To read my posts, you need HTML-enabled Newsreader such as Mozilla Thunderbird.

Thank you.


Idiot.

On 2020-07-21, Sjouke Burry wrote:
Idiot.

HTML has no legitimate place on Usenet. Neither do bullet points.
I've killfiled the perverted asswipes that insist on using them here.

--
------------------------------------------------------------------------------
Roger Blake (Posts from Google Groups killfiled due to excess spam.)

The US Census, what info must you give? -- http://censusfacts.info
Don't talk to cops! -- http://www.DontTalkToCops.com
Badges don't grant extra rights -- http://www.CopBlock.org
The facts about Climate Change -- http://www.RealClimateScience.com
------------------------------------------------------------------------------

On 7/21/2020 7:24 PM, Roger Blake wrote:
On 2020-07-21, Sjouke Burry wrote:
Idiot.
HTML has no legitimate place on Usenet.


I agree.


Neither do bullet points.


But I disagree with that. What's wrong with bullet points?

--
Ken

On Wed, 22 Jul 2020 at 09:42:50, Ken Blake wrote:
On 7/21/2020 7:24 PM, Roger Blake wrote:
On 2020-07-21, Sjouke Burry wrote:
Idiot.
HTML has no legitimate place on Usenet.


I agree.


Neither do bullet points.


But I disagree with that. What's wrong with bullet points?

They can be quite effectively done with a lower-case letter O

o like this.

I've also seen people using a full stop (US: period; actually, probably
best just to say a dot)

.. like this,

but I think in most fonts the o is better.
--
J. P. Gilliver. UMRA: 1960/1985 MB++G()AL-IS-Ch++(p)Ar@T+H+Sh0!:`)DNAf

Do we vote for the people who got us into this mess, or the people who can't
get us out? - Jay Leno, quoted by Ron Bauerle 2015-7-24

In article , J. P. Gilliver (John)
wrote:

Neither do bullet points.


But I disagree with that. What's wrong with bullet points?

They can be quite effectively done with a lower-case letter O

o like this.

I've also seen people using a full stop (US: period; actually, probably
best just to say a dot)

. like this,

but I think in most fonts the o is better.

even better is using an actual bullet point character.

nospam wrote:
In article , J. P. Gilliver (John)
wrote:

Neither do bullet points.


But I disagree with that. What's wrong with bullet points?

They can be quite effectively done with a lower-case letter O

o like this.

I've also seen people using a full stop (US: period; actually, probably
best just to say a dot)

. like this,

but I think in most fonts the o is better.

even better is using an actual bullet point character.


Well if you are being true to Usenet it should be only US ASCII
characters and there are no bullet point characters in ASCII 127.

--
Take care,

Jonathan
-------------------
LITTLE WORKS STUDIO
http://www.LittleWorksStudio.com

In article , Jonathan N. Little
wrote:

Neither do bullet points.

But I disagree with that. What's wrong with bullet points?

They can be quite effectively done with a lower-case letter O

o like this.

I've also seen people using a full stop (US: period; actually, probably
best just to say a dot)

. like this,

but I think in most fonts the o is better.

even better is using an actual bullet point character.


Well if you are being true to Usenet it should be only US ASCII
characters and there are no bullet point characters in ASCII 127.

unicode replaced ascii long ago in all modern operating systems.

nospam wrote:
In article , Jonathan N. Little
wrote:

Neither do bullet points.

But I disagree with that. What's wrong with bullet points?

They can be quite effectively done with a lower-case letter O

o like this.

I've also seen people using a full stop (US: period; actually, probably
best just to say a dot)

. like this,

but I think in most fonts the o is better.

even better is using an actual bullet point character.


Well if you are being true to Usenet it should be only US ASCII
characters and there are no bullet point characters in ASCII 127.

unicode replaced ascii long ago in all modern operating systems.


We are not talking about OSes, we are talking about Usenet.

--
Take care,

Jonathan
-------------------
LITTLE WORKS STUDIO
http://www.LittleWorksStudio.com

On 2020-07-23, Jonathan N. Little wrote:
We are not talking about OSes, we are talking about Usenet.

On Usenet, both bullet points and HTML are the products of diseased minds.

--
------------------------------------------------------------------------------
Roger Blake (Posts from Google Groups killfiled due to excess spam.)

The US Census, what info must you give? -- http://censusfacts.info
Don't talk to cops! -- http://www.DontTalkToCops.com
Badges don't grant extra rights -- http://www.CopBlock.org
The facts about Climate Change -- http://www.RealClimateScience.com
------------------------------------------------------------------------------

In article , Jonathan N. Little
wrote:

Neither do bullet points.

But I disagree with that. What's wrong with bullet points?

They can be quite effectively done with a lower-case letter O

o like this.

I've also seen people using a full stop (US: period; actually, probably
best just to say a dot)

. like this,

but I think in most fonts the o is better.

even better is using an actual bullet point character.


Well if you are being true to Usenet it should be only US ASCII
characters and there are no bullet point characters in ASCII 127.

unicode replaced ascii long ago in all modern operating systems.


We are not talking about OSes, we are talking about Usenet.

which is is accessed via a newsreader app running an os.

unicode is the current standard, which supports all characters. ascii
does not.

In article ,
nospam wrote:
....
Well if you are being true to Usenet it should be only US ASCII
characters and there are no bullet point characters in ASCII 127.

unicode replaced ascii long ago in all modern operating systems.


We are not talking about OSes, we are talking about Usenet.

Quite so. I was just about to post in exactly those same words.

which is is accessed via a newsreader app running an os.

It must hurt to be this stupid.

unicode is the current standard, which supports all characters. ascii
does not.

And that has nothing to do with anything that is being discussed in this
thread. In future, pay attention! Get smarter!

--
Which of these is the crazier bit of right wing lunacy?
1) We've just had another mass shooting; now is not the time to be talking about gun control.

2) We've just had a massive hurricane; now is not the time to be talking about climate change.

nospam wrote:
unicode is the current standard, which supports all characters. ascii
does not.

And what does that have to do with the NNTP protocol. Not sue if this is
the only RFC that defines it but here is one:

https://www.w3.org/Protocols/rfc977/rfc977.html

2.2. Character Codes

Commands and replies are composed of characters from the ASCII
character set. When the transport service provides an 8-bit byte
(octet) transmission channel, each 7-bit character is transmitted
right justified in an octet with the high order bit cleared to zero.

I don't see Unicode mentioned anywhere, but for content & commands is
the *ASCII* character set

--
Take care,

Jonathan
-------------------
LITTLE WORKS STUDIO
http://www.LittleWorksStudio.com

On Thu, 23 Jul 2020 01:08:40 -0000 (UTC), in alt.comp.os.windows-10,
Roger Blake wrote:

On 2020-07-23, Jonathan N. Little wrote:
We are not talking about OSes, we are talking about Usenet.

On Usenet, both bullet points and HTML are the products of diseased minds.

Preferred line length? Just curious.

Fixed width font just goes without saying. I won't even ask.

--
Zaghadka

Seems a computer engineer, a systems analyst, and a programmer were
driving down a mountain when the brakes gave out. They screamed down the
mountain, gaining speed, but finally managed to grind to a halt, more by
luck than anything else, just inches from a thousand foot drop to jagged
rocks. They all got out of the car:
The computer engineer said, "I think I can fix it."
The systems analyst said, "No, no, I think we should take it
into town and have a specialist look at it."
The programmer said, "OK, but first I think we should get back
in and see if it does it again."

On 23 Jul 2020, Zaghadka wrote
(in ):

On Thu, 23 Jul 2020 01:08:40 -0000 (UTC), in alt.comp.os.windows-10,
Roger Blake wrote:

On 2020-07-23, Jonathan N. wrote:
We are not talking about OSes, we are talking about Usenet.

On Usenet, both bullet points and HTML are the products of diseased minds.

Preferred line length? Just curious.

80 xtrs


Fixed width font just goes without saying. I won't even ask.

Lucida Typewriter Std 12 point

On 23 Jul 2020, Jonathan N. Little wrote
(in article ):

nospam wrote:
unicode is the current standard, which supports all characters. ascii
does not.

And what does that have to do with the NNTP protocol. Not sue if this is
the only RFC that defines it but here is one:

https://www.w3.org/Protocols/rfc977/rfc977.html

2.2. Character Codes

Commands and replies are composed of characters from the ASCII
character set. When the transport service provides an 8-bit byte
(octet) transmission channel, each 7-bit character is transmitted
right justified in an octet with the high order bit cleared to zero.

I don't see Unicode mentioned anywhere, but for content & commands is
the *ASCII* character set

Some people, myself included, have done things like selecting unicode display
fonts specifically because they want to be able to access rather more than
plain ASCII. There are those who object; several have told me that they
don’t like the way that non-ASCII characters display (apparently ‘curly
quotes’ can cause conniptions) and have demanded that I stop using
non-ACSII or else. When I tell ‘em that I’d like to see the ‘or
else’, typically they mumble something about their killfile. I tell ‘em
to go right ahead. I post the way I want, they never see my posts, everyone
is happy. Personally, I have a reason for using non-ASCII characters, a
simple one: my spelling, or lack of same. Those who haven’t killfiled me
may have noticed that my spelling is not the best. I try to fix it, and one
of the ways I try to fix it is to use the actual words, some of which have
various accents, umlauts, and other things. If my attempts to spell words,
and particularly names, correctly offends some, well... I don’t see why
their not liking non-ASCII characters is more important than spelling
properly, and, frankly, if they object so much, the cure is in their
killfiles.