This article is within the scope of WikiProject Computing, a collaborative effort to improve the coverage of computers, computing, and information technology on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.ComputingWikipedia:WikiProject ComputingTemplate:WikiProject ComputingComputing
This article is within the scope of WikiProject Classical music, which aims to improve, expand, copy edit, and maintain all articles related to classical music, that are not covered by other classical music related projects. Please read the guidelines for writing and maintaining articles. To participate, you can edit this article or visit the project page for more details.Classical musicWikipedia:WikiProject Classical musicTemplate:WikiProject Classical musicClassical music
The following Wikipedia contributor may be personally or professionally connected to the subject of this article. Relevant policies and guidelines may include conflict of interest, autobiography, and neutral point of view.
Bfinn (talk·contribs) / Sibelius (software) This user has contributed to the article.
In 1996 or so there was still a (small) RISC OS market and Sibelius being a killer app meant people were willing to buy Risc PCs just to use Sibelius, so I imagine a RISC OS version could have worked. But I recall reading in Acorn User that the new version of Sibelius was not available for RISC OS because the platform lacked a C++ compiler of acceptable quality (Acorn C/C++ not being good enough for reasons I wasn't knowledgeable enough to understand). The cancellation of the Risc PC 2 and then collapse of Acorn was just the final nail in the coffin. Hairy Dude (talk) 17:04, 8 March 2020 (UTC)[reply]
The article includes a disproportionate amount about this, with too much fine detail and numerous references presumably created as part of the campaign but no longer of interest, so I've moved it here:
Section #Timeline contains a lot of facts which appear NPOV but seem to place undue weight on some unimportant events in a promotional manner. For example, the three mentions of Japan are uncited and don't add relevant information. #Add-ons relies a lot on primary sources and seems to be flouting Sibelius' features. In general features/gameplay sections tend to be overly detailed since they are often written by fans. It's more neutral than some other articles, of course, but there are still issues to fix.
@Sungodtemple: The Save Sibelius campaign originally had its own article, that was absorbed into this one, around the same time that we merged two other articles that were very similar, so as to make this with the new definition of 'scorewriter' appended. Save Sibelius has extensive citations in the original article, which I will hunt for and reinstate here, but for now, the MacUser article I have just copied back as a citation documents the campaign. I will look into the other points you make and work on them. Chrisdevelop (talk) 22:56, 28 May 2023 (UTC)[reply]
@Sungodtemple: I have copied MacUser and ZDNET citations over from the original Save Sibelius section with multiref from Lede to Timeline 2012. I added {{citations needed}} for the 2012 claim about the 20% lead in sales over MakeMusic because I couldn't find a source. I presume whoever contributed this will have a source. I removed a couple of promotional words relating to Awards both in the Timeline and in the Awards section. Regaring the WP:PS concerns in the Add-ons section, that's a bit more problematic. These appear to be not for corroboration of the information itself, but to link readers to the companies to find out more about them, but even though I agree this can be construed as not WP:NPOV, I am loath to delete them. So instead, so far, I have added citations from external sources for the control surfaces, without removing the existing WP:OR citations at this point. AudioScore is covered with citations to customer reviews and I added new citations for MOTU Symphonic Instrument and Note Performer. Chrisdevelop (talk) 01:17, 2 July 2023 (UTC)[reply]