The bury ending for a place name indicates that there was once a castle, stronghold or fort at that location and it can also be found in many nearby places such as Highbury and Barnsbury, yet the on-board announcements for those are OK, so why has TfL got Canonbury wrong?!
Yes, I know it's an automated, patched-together, voice thing and I could almost forgive the error if she said it in the same way as the verb 'to bury' which is pronounced 'berry' and echoes the market town in Greater Manchester. But here in Canonbury, the misappropriated burrie thing makes no sense when there is no word that sounds like that at all. I mean, what is a burrie?
Isn't the English language fun?!
Feel free to enlighten me either in a comment of via jane@janeslondon.com
Recently I wrote about the coal hole cover plates in Canonbury Square, N1.
Thanks for the comments – for some reason I am unable to reply/comment myself at the moment (Sep2022)
I think we have to accept the rather shoddy pronunciations offered by TFL - they're not ever properly researched. Here in E17, we live, apparently, in a place called WOLL-them-stO
ReplyDeleteBury in Greater Manchaester is actually pronounced 'Burry', not 'Berry'.
ReplyDeleteA possible variation is that it may be to please American visitors, who would pronounce the word exactly as announced by the TfL voice simulator. Similar to how Buckingham - Bucking-HAM, and not Bucking'm - is pronounced Stateside.
ReplyDeleteThat did cross my mind. But doubtful. Especially as this isn’t a tourist route. And why would TfL consider that as an option rather than appeal to locals who know what it’s actually called?!
DeleteAnnouncements like these are made using a cut and paste process so this pronounciation is a kind of aural mashup.
Thanks, Jane.