RISC OS bore: https://20000.org
www.youtube.com/watch?v=0aLI...
www.youtube.com/watch?v=0aLI...
This is why KeyPress must be interpreted in the current Alphabet.
This is why KeyPress must be interpreted in the current Alphabet.
Form an orderly queue.
[I’ve put this on #123 for this demo but I haven’t allocated a number for CP-437 yet. Sadly the number 437 has b7 set so I can’t use that. Boo.]
Form an orderly queue.
Later there'd be 65C102, 80186, 80286, 32016 and of course ARM.
Later there'd be 65C102, 80186, 80286, 32016 and of course ARM.
<follow>
<immediately reminded why I stopped following>
<unfollow>
Six months later...
<follow>
<immediately reminded why I stopped following>
<unfollow>
Six months later...
That's a Wynne-Win for me.
That's a Wynne-Win for me.
Both of these are RISC OS Alphabets (but not 7bit numbers) and make a distinction between semantic and appearance Unicodes:
Both of these are RISC OS Alphabets (but not 7bit numbers) and make a distinction between semantic and appearance Unicodes:
"I don't think that we should allow ourselves to be bullied into thinking that the BBC is only any good, if it reflects the prejudice of the last person who shouted at it." ~AA
"I don't think that we should allow ourselves to be bullied into thinking that the BBC is only any good, if it reflects the prejudice of the last person who shouted at it." ~AA
PO to pay £41m to Fujitsu.
Fujitsu was instrumental in persecution of innocent postmasters. £1.2bn compensation paid from public purse. More to follow. Fujitsu haven't paid a penny, no one has been charged.
Why is Fujitsu being rewarded?
PO to pay £41m to Fujitsu.
Fujitsu was instrumental in persecution of innocent postmasters. £1.2bn compensation paid from public purse. More to follow. Fujitsu haven't paid a penny, no one has been charged.
Why is Fujitsu being rewarded?
#solarpower
electrek.co/2025/11/04/a...
#solarpower
I’ve just added a long-planned feature: “StrongTabs” seps mode – which isn’t limited to tab characters or one-character separators, but consumes multiple separators as one...
I’ve just added a long-planned feature: “StrongTabs” seps mode – which isn’t limited to tab characters or one-character separators, but consumes multiple separators as one...