Punctuation Matters

I have recently become somewhat embroiled in a bit of controversy over the correct form of possessive to use when dealing with singular nouns and names that end in single-s: I thought it might be worth documenting my viewpoint and the justification for it. First things first, then: in the 1970s my grammar school taught me a very simple, three-part rule:

  • Words ending in not-s (e.g., bell) take apostrophe-s: The bell's chime was clear.
  • Words ending in double-s (e.g., princess take apostrophe-s: The princess's dress was blue.
  • Words ending in single-s (e.g., bus) take apostrophe only: The bus' route was blocked.

This is indeed coded into my music player Giocoso, with code I first wrote back in 2019:

# For apostrophes, if a word ends in single-s, add only an apostrophe. If it ends in ss or not in s at all, then it's apostrophe+s.    
if [[ ! -z $displaycomp ]]; then   	 
    if [[ ${displaycomp: -2} == ss ]]; then
      displayapostrophe="'s"
    elif [[ ${displaycomp: -1} == s ]]; then
      displayapostrophe="'"
    else
      displayapostrophe="'s"
    fi
  else
    displayapostrophe=""      # If, for some reason, they are playing un-tagged FLACs directly, then we can't be displaying this at all
  fi

This code is why you'll see this sort of thing when playing music with Giocoso:

Or this:

Arthur Bliss ends in double-s, so he gets an apostrophe-s, but Ralph Vaughan Williams ends in single-s, so he gets a naked apostrophe to indicate possession.

It is possible, of course, that I was taught extremely badly back in the 1970s (and it's also very likely that fashions have changed since those days). However, I checked what (vaguely) current authorities on the matter have to say.

First, we have New Hart's Rules, OUP, 2014: The Oxford Style Guide, p.71

This is certainly more nuanced than the rule I was taught. Indeed, with the example given of “Lord Williams's School” it appears to flat-out say my rule is simply wrong. Except that it does no such thing: if it gives the example of Nicholas' and Nicholas's, it's showing that either form is acceptable. I cannot see a meaningful difference between the name “Nicholas” and “Williams”: both are three-syllable names ending in single-s, so what applies to Nicholas should equally apply to Williams. The examples given are, in other words, merely pointing out that long, multi-syllable names ending in single-s can and cannot take a naked apostrophe ending. They specifically chose to say Nicholas' was correct; they could equally well have said that Williams' was acceptable on precisely the same logic… but I imagine space got the better of them!

We shouldn't, in any case, look for a rule spelled out that simply mandates or forbids the naked apostrophe. The point is to demonstrate that a formidable authority on punctuation has just demonstrated that the naked apostrophe is acceptable “where an additional s would cause difficulty in pronunciation”. It is, in other words, more a matter of 'internal voicing' that occurs when you read than a hard-and-fast rule-book approach.

This well-known hospital would, for example, probably want to take issue with their advice on 'personal names ending in s':

Anyway: the New Hart's Rules permits naked apostrophes for singular names that end in s. It doesn't compel their use but it doesn't ban them, either.

My second authority is The Oxford Guide to Style, published in 2002. On page 113 we find:

Almost all these examples (why syphillis should be unique, I have no idea!) support the idea that words ending in single-s get a naked apostrophe when forming the possessive. More importantly, however, is the statement that there is no hard-and-fast rule but that “euphony is the overriding concern”, again making the point that it is the pleasing nature of your 'inner voice' as you read that determines whether a naked apostrophe is acceptable or not.

Which brings me to my inner voice, I guess! When I read of “Vaughan Williams' symphonies”, I do not pronounce it in my head (and never have) as “Vaughan Williamz-iz symphonies”. The extra syllable is, for me, redundant. I hear it as simply “Vaughan Williams Symphonies”, with the middle word pronounced as three syllables, not four. I am not claiming that other people don't 'hear' it with the extra “-iz”: if they wish to type “Vaughan Williams's symphonies”, they're not wrong to do so, if that's how their 'inner voice' works. Whatever is euphonious to someone is correct: I just happen to find the extra syllable jarring and ugly.

It is probably fair to say that I am somewhat old-fashioned in this, however: it's quite difficult to find, quickly, examples of modern literature that do it 'my way'. I can always find plenty of examples from the past that agree with me, of course:

  • A dog—old Carlo, Mr. Rivers’ pointer, as I saw in a moment—was pushing the gate with his nose, and St. John himself leant upon it with folded arms; his brow knit, his gaze, grave almost to displeasure, fixed on me. I asked him to come in. (Charlotte Brontë, Jane Eyre (1847), Chapter 31)
  • “I am an archer of my lord Douglas’ outer guard. I can have no promotion save from him or those of his house — not even from the King himself.” (S.R. Crockett, The Black Douglas (1899), Chapter VIII)

Somewhat more modern, though:

  • A cloud began to cover the sun slowly, wholly, shadowing the bay in deeper green. It lay beneath him, a bowl of bitter waters. Fergus’ song: I sang it alone in the house, holding down the long dark chords. (James Joyce, Ulysses (1921), Chapter 1)

This time, something a little more specifically relevant to music and to Vaughan Williams specifically:

  • I can think of the complete Matthew Passion, Brahms’ Requiem, and works like Parry's Job and Vaughan Williams’ Sea Symphony (Adrian Boult, My Own Trumpet, 1973, Page 51)
  • April 1935 saw the first performance of Vaughan Williams’ F minor Symphony… (Adrian Boult, My Own Trumpet, 1973, Page 106)
  • Vaughan Williams’ Job made a deep impression, helped perhaps by my idea of putting up some large cards with numbers, which showed the nine scenes, so that the audience could follow dramatically as well as musically. (Adrian Boult, My Own Trumpet, 1973, Page 138)

And finally, something equally relevant to music, but from Benjamin Britten:

  • …you know how I dislike conducting. But because of Krips’ sudden defaulting I had to take on Budd… (Reed, Cooke & Mitchell, Letters from a Life, Volume 4, Page 42, quoting Britten letter 728 written March 1952).

Anyway: my point remains, there's ample support for using the naked apostrophe on names ending in single-s, in both grammatical authority and literature, including literature that is specifically musically- and Vaughan Williams-related. It's not a requirement, but a personal preference, depending on one's sense of 'euphony'.

While we're on punctuation matters, I'd also like to throw this in:

That's from the same Oxford Style Guide (2002) as before, this time page 117. It again acknowledges that there is no single, hard-and-fast rule on the acceptable use of the comma: it is a matter of fashion as much as anything and 'best comma practice' is a moveable feast. My own personal approach to them, again taught back in the 1970s, is to never use them before conjunctions and to avoid excessive 'slow down' commas — that is, commas whose function is to exhibit the writer's sense of pacing and breath-drawing which may not match my own. Generally, I prefer to let the reader parse things as they wish or need… but again: it's all to do with 'inner voicing' as one reads, not blind application of a simplistic grammar rule.

Lest I be accused of selective quoting, let me make it clear that the Oxford Style Guide goes on to recommend the use of commas before conjunctions:

My reaction to that is that it's an awfully convoluted rule to state and difficult to apply: you have to assess whether main clauses are 'semantically related', 'grammatically similar' and 'too long', which is an incredibly subjective thing to determine, I would say. Of the first three examples shown, with commas, I would dispose of the comma in the first two. The third one (“I will not try now, yet it is possible…”) I think is just ugly writing. I would re-write it to be “I will not try now. It is possible I may try again in future”. The second set of three examples are, I think, how I would generally try to write: I wouldn't reserve that comma-less approach for just 'short and closely linked' clauses. Interesting that the last example cited is practically a verbatim re-write of the third but without the comma: I think it proves that the comma in that third example is really unnecessary and thereby demonstrating that comma usage is a matter of taste as much as anything else.

It has been said to me directly that commas are necessary to structure a complex sentence properly. They may well be: but my response to that assertion was and remains that you shouldn't be writing sentences so complex that their meaning necessitates numerous commas in the first place. At best, they will make your prose slower to read; at worst, they will not resolve ambiguities that your convoluted prose wraps in a tangle of clauses and sub-clauses. Epithetically: write more simply; need fewer commas.

Of course, the Oxford Style Guide is going to recommend the use of the Oxford Comma (or 'serial comma' as it's sometimes called), too:

I cannot stand the Oxford Comma: for me and my 'inner voice', the presence of that last comma in the list just enforces a pause that is completely unnecessary: there's nothing wrong with 'urban, squat and packed with guile'. There's no ambiguity about what's meant and I'd much prefer to get on to the end of the sentence than have a visual instruction to halt momentarily for no good reason. Putting it bluntly, I find the Oxford Comma slows down reading by introducing visual clues to pause for no good reason.

Sometimes, removing the comma would give rise to confusion. A dedication of a book that read To my parents, Mother Teresa and the pope certainly suggests that the author has two illustrious parents, neither of whom should really be having children at all, let alone together! The suggestion is that re-writing that as To my parents, Mother Teresa, and the pope makes it clear that three separate dedicatees are intended. I don't completely buy that argument but I can certainly agree that the slight, momentary pause introduced before the Pope is mentioned helps makes it a little less problematic. My personal preference would be to re-phrase the dedication completely, however (for example: To my parents, to Mother Teresa and to the Pope).

In the general case, removing an Oxford Comma may need a sentence to be lightly re-worded to make it retain sense and specificity. I think writing is clearer (and more euphonious) when the Oxford Comma is disposed of and I rather suspect that's why the in-house style guides of both The Times newspaper and the The Economist magazine say not to use it. Plenty of other style guides do recommend it, of course: I'm not suggesting otherwise. I am suggesting merely that it is as valid to dispense with it as to retain it.

In conclusion, therefore: naked apostrophes, comma abuse in general and the use of the Oxford Comma specifically are matters of taste and 'inner ear', not ones of rule-book rigour. I do not, in other words, claim that, “I am right” but merely assert that, “I am not wrong”.

2026/01/10 14:58 · hjr · 0 Comments

Giocoso 3.33 Released

I've just released version 3.33 of Giocoso, a day later than planned …but a day earlier than feared!

Upgrades are via the usual path: Administration menu, Option 1. After the update completes, quit Giocoso and re-launch it to have the new features picked up and applied. Ignore any errors that may be displayed on program exit: they're expected!

Key new features, in no particular order:

  • Album Art captions are now scaled and sized more appropriately, to better deal with high-resolution monitors
  • Various improvements to make things work better on macOS
  • The program logo now displays correctly again
  • Timebars are no longer limited to 999 hours: they are now unlimited
  • MacOS now can do Giocoso Pro properly, given that ancient macOS versions will tend to install ancient versions of the MariaDB client, which need special measures to deal with the existence or non-existence of ssl connection issues
  • MacOS mouse gestures would screw up the Giocoso program display: they no longer do so

Full details, as ever, in the Changelog.

Again: a happy new year to all Giocoso users!

2026/01/01 16:30 · hjr · 0 Comments

Happy New Year, 2026

A short note to wish all my readers, regulars and just-passing alike, a very happy 2026. I shall likely be off-line for much of January and early-to-mid-February, given my editing responsibilities for the Ralph Vaughan Williams Society's Journal, but I hope to keep the software coming nonetheless.

2025/12/31 18:46 · hjr · 0 Comments

Christmas News

My apologies to readers for basically not having posted anything over the Christmas period and not even getting around to wishing anyone a Happy Christmas! :-( The unfortunate truth was that I woke up on the morning of December 20th basically unable to move. I've no idea why, but perhaps I'd slept at an awkward angle or something: my neck would spasm in excruciating pain if I did so much as try to talk. Two days in bed, immobile, brought some relief… but the problem still hasn't entirely resolved itself a week and a bit later. I am at least moving around, able to cook the Christmas lunch and get plastered at the local watering hole, though: so things are looking up!

A new version of Giocoso will probably be released on schedule sometime on December 31st, but my enforced bed-rest has meant less ability to code than I'd have liked, so I might push the release date back a day or two.

It's going to be an interesting release, though, because a long-standing speed/screen refresh issue has finally been resolved. The problem is that Giocoso draws its various screen elements at specific positions in the terminal by means of making calls to the external (i.e., non-Bash) tput utility. It works fine… but every call-out to tput requires a context switch on the CPU and is thus relatively expensive in compute resources. On PCs with slightly under-powered CPUs (such as my Raspberry Pi 4 that I use as my music player, or the 2015 iMac I'm now using as my daily driver) the consequence was that every change of the terminal contents would produce notable “flashing” as the screen was laboriously re-drawn. It looked pretty ugly.

And then I started watching Dave Eddy's YouTube channel! The man is a wicked genius at Bash scripting (and other stuff, but his Bash skills are extraordinary) and in his latest Christmas video, specifically around the 32 minutes mark, he happened to mention in passing that he'd written a purely-Bash implementation of much of the tput utility's functionality. Since it's all done within the same Bash session, there's no CPU context switching and the functionality is thus implemented with much greater efficiency than before. His code was therefore swiftly copied and pasted into assorted parts of Giocoso… and the transformation has been immediately, obvious and impressive. The thing finally runs much more effectively and without the 'flashing' during screen re-draws. It's an amazing little tweak, for which I can't thank Dave enough… though he does get a formal copyright acknowledgement in the code comments inside giocoso3.sh!

In the New Year, I'll be busy editing my second edition of the Ralph Vaughan Williams Society Journal, due out before the end of February, so coding is likely to take a back seat during that period. The promised new version of Semplice that (mostly!) runs on macOS will thus have to wait until after that's all done: maybe some time in March, then.

By way of a bit of catch-up, I can't help but report on this, which happened in November:

That's me, fourth from the right, looking directly at the camera, singing on the stage of the Snape Maltings Concert Hall! A lifetime's dream come true, basically :-) The occasion was a 'Ceremony of Carols from Scratch', wherein a complete bunch of amateurs came together to sight-read and rehearse Benjamin Britten's great work from the 1940s, A Ceremony of Carols, and then to give a performance later in the afternoon. I so rarely get to sing these days that the occasion would have been great fun even if it had taken place in someone's backyard. To be able to do it on that particular concert platform, however: amazing!

Now is also about the time that I do a 'year in review' of my music playing. The charts tell their own story: this year, I've played fewer recordings (by number) than in any year since 2018. That's because, in my efforts to drive down the number of recordings in my collection that hadn't been played at least once by Giocoso, I spent the first half of the year playing lengthy works by the likes of Wagner and Verdi. Few in number, but lengthy in terms of minutes of play-time: that's why you'll also see that the 'Play Durations by Year' graph shows me playing 3,875+ hours of music this year …almost matching last year's play durations and comfortably exceeding the duration of music listened to in any of the other previous four years. That many hours, by the way, equates to 161 days: I was basically listening to music for 44% of the year!

My top composers this year have been (with hours of play-time shown next to each composer name):

Johann Sebastian Bach526
Richard Wagner400
Ludwig van Beethoven330
George Frideric Handel314
Giuseppe Verdi271
Wolfgang Amadeus Mozart263
Antonio Vivaldi120
Joseph Haydn92
Gioachino Rossini81
Benjamin Britten54

Britten squeaks into the list this year because of his November 22nd birthday… everyone else is there because of the 'drive to play everything once' playing campaign. I have found, since that goal was achieved on October 14th, that I'm now playing a huge number of different composers once more, which is much more pleasant. I have Giocoso set up to prevent a composer's works being replayed more than once per month and to restrict play durations to less than 90 minutes: the number of variety of relatively short compositions played have therefore rocketed in the past three months, which has been a delight.

Given the names in the 'top composers of 2025' list, it shouldn't be a surprise what were the most common genres to be played this year (again, with hours played shown in the second column):

Opera1388
Oratorio466
Symphonic388
Choral351
Keyboard324
Concerto221
Orchestral151
Chamber80
Quartet58
Film - Theatre - Radio53

Most of that huge opera listening was thanks to just two lads from 1813: Wagner and Verdi. They're going to be rare pleasures in 2026, given that the need to play them at least once has now passed and the desire to play them again is tempered by the realisation that you're into a multi-hour-long bout of melodrama and emotional excess if you once start playing anything of theirs!

Perhaps the biggest news from 2025 from the deepest recesses of musical Lincolnshire is that I have abandoned Linux as my daily driver and switched to, er, <cough> macOS. Yup: I don't particularly like Apple's software, but their hardware is lovely and the retina screens from even a decade ago are pleasing to my ageing eyes. I'm really hoping that in the New Year I shall finally summon up the wherewithall to go purchase a modern Apple Silicon iMac from the Apple store in Cambridge. It will involve eye-watering amounts of cash… and I hate the built-in obsolescence timer that means anything you buy now will cease to receive official support in just a handful of years. I had been contemplating a move from Linux to BSD at some point: Linux developers have been doing weird things of late (Wayland, anyone?!) and though I've been using it exclusively since 2012, I've basically had enough of it. Apple's macOS is essentially BSD under the hood, with a very weird userland on top of it! I can cope, I think. I just need the bank balance to expand to accommodate the new fashion!

Anyway, that's it from me for 2025: see you again soon in the New Year, I hope. Entirely incidentally, bonus points to anyone who can examine the thumbnail to this post and work out why AI is very artificial and definitely not intelligent!!

2025/12/28 17:09 · hjr · 0 Comments

Giocoso Version 3.32 Released

A day later than anticipated, I've just released Giocoso Version 3.32. It contains some significant new features, including support for Kitty graphics for terminals that can't display album artwork using sixel graphics; a terrible logic bomb I created back in 3.30 affecting the way the time bar worked that is now fixed; a new installer that looks better and performs more efficiently; and support (somewhat rudimentary!) for running on macOS.

Administration Menu Option 1 should get you the update, without major issue.

Edited to add: documentation is progressing well, with new pages regarding installation on Windows 11 now nearly complete.

2025/12/11 21:23 · hjr · 0 Comments

Older entries >>

  • blog.txt
  • Last modified: 2025/10/02 16:27
  • by hjr