Just in Case somone doesn't subscribe to the CQ-Contest reflector or missed this. W0ETC Date: Fri, 17 Dec 2004 11:58:23 -0500 From: "Henderson, Dan N1ND" <dhenderson@arrl.org> Subject: [CQ-Contest] "
When did things change? I'm just getting back to RTTY after a slight break in service of 30 years. My RTTY documentation shows that all Amateur Teletype equipment is set up with slash 0 for the numbe
I'm not sure when things changed, but they sure did. Nowdays, the zero and the "O" are differentiated by their thickness. A zero is skinny, an "O" is fat. 0O - which is which? There is a True Type fo
On Dec 17, 2004, at 10:19 PM, Bill Turner wrote: I'm not sure when things changed, but they sure did. Nowdays, the zero and the "O" are differentiated by their thickness. A zero is skinny, an "O" is
"Kok Chen" <chen@mac.com> wrote: "I think what N1ND refers to are characters which look like zeros but are not." Hmmmmmmmmmmm....kindasorta dispels the "if it looks like a duck, walks like a duck, th
I think what N1ND refers to are characters which look like zeros but are not. I thought he was referring to Ø (alt-0216). -- No virus found in this outgoing message. Checked by AVG Anti-Virus.
It's entirely dependent on what character set you are using and which font. The terminal I'm on right now (the default terminal window in SuSE) shows them as two different widths. Other character set
What is comes down to is the vast majority of RTTY operators now use computer generated, decoded and logged RTTY with MMTTY being the most popular sound card program. Also I would guess that nearly 1
One workaround I had forgotten about is to set your font to FIXEDSYS. The number zero has a sort of squiggle in it which makes it distinctive from the letter O. It's not exactly a slash, but there's
Ø - I'm at work where I have a proper terminal. The character at the left margin is NOT ASCII, and I think that's what N1ND was referring to. Sure looks neat in a zero-land callsign, though. :
On Dec 20, 2004, at 8:47 AM, Peter Laws wrote: Ø - I'm at work where I have a proper terminal. The character at the left margin is NOT ASCII, and I think that's what N1ND was referring to. Sur
The ARRL log robot permits a callsign to contain the 7-bit ASCII characters for the digits 0-9, the letters A-Z and the slash bar. There is no limitation as to what kind of slashed-oh character you