What’s with the bizarre punctuation style in these messages? Even if they used to be sent over a system which didn’t have colons and commas and non-capital letters, what about phrases like “VERY DIFFICULT…AND POTENTIALLY DEADLY” which would be perfectly fine with a space and no punctuation mark at all? Is there some reason they still have to look like they were sent from your great-aunt’s AOL account?
I think this is the format that used to be sent out via teletype, which was all uppercase. For the ellipsis you cite, it seems to be used to draw your attention to the following text, which would otherwise be lost in the larger block of text.
… and is there a guide to their terminology? What does this mean:
The winter weather advisory has been canceled … WHEW!
But … wait … there’s a winter storm warning now? In the same breath?
IIRC, having asked the same question of a friend of mine doing his PhD in meteorology, “advisory” translates to “there is a possibility of this happening, be careful”, while “warning” translates to “as far as we can tell, this is going to happen. Take proper precautions (and don’t be stupid)”.
The terms are defined in this glossary.
Note that it’s perfectly fine with a comma too. I’ve always read the ellipses in NWS reports as “punctuation mark goes here.”
Many, many decades ago I was the news editor at my campus radio station. We got our news from the AP in exactly that same format. Well, not exactly that format. Our originals were badly typed, with missing spaces and weird inserted characters and other stuff not generally compatible with polished final format.
When you use three dots instead of other punctuation, however, there is absolutely no doubt that at least a space and probably some other punctuation is needed. If you use “rip and read” - take the physical copy that comes off the printer, rip off the section that contains the news you want, and read that on air as your copy - it is actually much easier to insert mentally your own pauses when they are in a format that means pause rather than a specific semicolon.
Why they still use it now is harder to explain. However, if you’re going to use this system at all, this format is actually a pretty good one. It evolved to meet the needs of users. It’s like the difference between a standard book with normal size serifed typeface and a weird-sized book with sans serif fonts and lots of white space in two columns. The latter may be an art director’s dream and perfect for the individual project, but the former will be readable for almost everybody almost all of the time for almost every possible subject. Which is what the news is.
Once you get used to it, it’s like FORTRAN, to use an example equally ancient. A coder can read it with blinding speed because its a specialized format geared exactly to their needs. Whether outsiders stumble is not really the issue. Is FORTRAN written differently today because it’s on screens instead of punchcards?
(Much of this is WAG, but it feels right. As a Colbert disciple, I feel reality with my gut.)
Hah. Well, that depends greatly on the coder and on the needs. I’d be… downright terrified, as a matter of fact, to see someone capable of writing a graphical first-person shooter in FORTRAN-IV. I’d also be surprised to see a modern business application developer capable of reading it.
Yes, in fact, and you picked a bad example as many others will be around to tell you. For one thing, Fortran has evolved into something that looks like it had a tryst with Pascal. For another, even ancient FORTRAN isn’t maintained with coding forms, keypunches, and “same-day service”* anymore: The people maintaining ancient physics software use text editors and compile their own code just like the rest of us.
*(“Same-day service” is what you want with a batch programming system, where everyone lines up to use the same computer, one at a time. Same-week might be more like it.)
My guess is so it can be read by the text-to-speech program they use to do the weather radio broadcasts. The ellipses would be the pauses the computer voice has between counties.
I was going to mention this. The weather radio voices essentially just read these messages on a loop. Probably some text-to-speech software would work without this format, but it’s already written like this, so that’s probably a good enough reason to stick with it.
It was sort of a guess, but I think that may be it. I have two text-to-speech programs and have to use ellipses for pauses instead of commas, which they skip right over. I guess it makes sense because you wouldn’t want it to pause on the comma between a city and state, but you would want it to pause when the comma is in a sentence. The simple solution would be to do away with commas entirely (none in the NWS bulletin) and use ellipses for pauses.
I couldn’t find a weather channel with a similar alert to listen to the pauses in the voice but I did hear one that listed counties and it breezed through them very fast, leading me to believe it was reading it in the “WINNEBAGO-BOONE-MCHENRY” format from the OP’s post. From what I can remember of local alerts, the cities following have pauses in between.