In a message dated 2009.10.23 23:26 -0500, NoOp wrote:

<http://www.bsa.org/country/BSA and Members/Our Members.aspx>
Spaces in URLs.  Tut, tut.  Surely, *they* should know better....

Indeed they should. I must say that I just copy/pasted the link without noticing that. Sorry that I failed to do the "%20" substitutions as needed, or even to check the link, but I appreciate the evidence of Business Software Alliance stupidity. Fitting. BSA is of course a mostly Microsoft-driven "Alliance", running on MS Windows servers.

And that has what to do with OOo licensing and the OP's OOo question?

(1) The OP began with a concern for BSA.
(2) A subsequent poster asked What it BSA?
(3) I posted a link answering (2) - overlooking that it was a poorly-formed URL.
(4) A poster observed that it was a poorly-formed URL.
(5) I apologized for the oversight - with a comment about BSA, MS and the MS commitment to web/Internet/[any(?)] standards. As the URL problem would have only occurred on an IIS server, the comment was gratuitous - for which I apologize - but not entirely irrelevant.

This is somewhat ironic:
User-Agent: Thunderbird 2.0.0.22 (Windows/20090605)
You have an seem to have an objection to Microsoft & Microsoft Windows
servers, yet you don't seem to object to using their products.

FWIW, I do object to using MS products - if you could see even further into my environment, you would see that this mail is handled under a profile "Diane" - but it's a long story, and even more irrelevant to this thread or the business of this list. Thus I will not further burden the list bandwidth with this distraction, even if there is a follow-up comment. I was mildly annoyed that my attempt to briefly answer a question blew up into a distraction; I was even more annoyed that the distraction arose from yet another MS departure from yet another published standard (in this case, RFC-1738).

John

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to