| |
N2NOV > ALL 19.08.25 19:00l 33 Lines 1701 Bytes #999 (0) @ WW
BID : DYUZ_N2NOV
Subj: Message Layout and Formatting for Amateur Radio
Path: IZ3LSV<IK6IHL<IK7NXU<HB9ON<HB9ON<PI8ZTM<PI8LAP<DK0WUE<N2NOV
Sent: 250819/1641z @:N2NOV.#RICH.NY.USA.NOAM $:DYUZ_N2NOV
Let's call this my HTML use in amateur datamodes complaint. I am not just
talking about the badly formatted packet bulletins, but also how we should
really be reaching for a least common denominator in amateur radio data
communications. There are many who have been enamored with the WL2K use of
HTML forms and email attachments, but they do add a bit of bloated bandwidth
and a sense that it is the internet email, but over the air. Shouldn't we be
looking to streamline and minimize the amount of airtime so that more message
may be passed? The FLmsg structure of the FLdigi suite of programs by W1HKJ
looks to just transmit the data fields of a form an not the fluff. This is
akin to XML, but in an easier human readable format with field tags showing
pertinent field size, etc.
There is a similar feeling about this on the Winlink mailing list this morning.
I always have to cleanup a packet message that originated as a copy and paste
from a website as it includes odd versions of characters and lines with messy
formatting that are wrapped around and longer than 80 characters. This makes
for a very tiring read as well as takes up more space and bandwidth than it
really needs to.
Some guidelines to use for any packet/digimode message or bulletins:
- maximum 72 to 80 character line length before a CR/LF
- convert webpage text as standard ASCII characters
- provide links to attachments/pictures if needed
- convert pictures as Base64 attachments (and indicate it in the text)
- spreadsheets should be saved as CSV for easy ASCII-only transmission
- word documents should be saved as TXT for easy ASCII-only transmission
--
73 de N2NOV
n2nov@n2nov.ampr.org
n2nov@n2nov.#rich.ny.usa.noam
Read previous mail | Read next mail
| |
