On Wed, 6 Nov 2013 05:34:38 +0700
"Urmas" <firstname.lastname@example.org> wrote:
Simple. The evil machinations of Microsoft.
I will repeat. If any and all Windows application could use Ctrl+J
for anything, why WordStad suddenly couldn't?
Ok, let me spell it out for you. Microsoft, as the developers of the
OS, put code in their OS to capture the Ctrl+J key combination, and not
pass it on to the foreground application. However, they also put in
code to allow an application to request that the key combination be
passed on, code that most people, including the developers of WordStar,
didn't know about (at least until after it was too late). Then
Microsoft, as developers of Word, put in the necessary request to make
the OS pass on the Ctrl+J key combination to Word. They knew to do
this, because they were the same company.
Or, alternatively, Microsoft, as the developers of the OS, put code in
to detect a running copy of WordStar, and hide the Ctrl+J key
combination from it. They did this because they were also the
developers of Word, and wanted it to have a monopoly.
I'm not saying they did any of this, I have no personal experience with
the Ctrl+J key combination, nor have I any insights into exactly how
they did this if it actually is true. I just know that they have done
evil and rude things to get or maintain a monopoly in the past, more
than once, including something very, very similar, and I wouldn't put
it past them to have done this too. I'm merely suggesting ways in which
they could have done it. I'm sure there are more.
Impressum (Legal Info)
: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (MPLv2
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our trademark policy