Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[WriteLog\]\s+feature\s+request\,\s+Thank\s+You\s+file\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[WriteLog\]\s+feature\s+request\,\s+Thank\s+You\s+file\s*$/: 2 ]

Total 2 documents matching your query.

1. [WriteLog] feature request, Thank You file (score: 1): Author: "FireBrick" <w9ol@billnjudy.com>; Date: Sat, 25 Sep 2004 09:29:29 -0500; Working a little in the CQWW. Most everyone says TU ur etc. etc. I'd love to see a feature, that reads the callsign, determines it's native language and instead of TU says something like: F6IRF MERCI; /archives//html/WriteLog/2004-09/msg00154.html (7,324 bytes)
2. Re: [WriteLog] feature request, Thank You file (score: 1): Author: Bob Naumann - N5NJ <n5nj@gte.net>; Date: Sat, 25 Sep 2004 16:05:10 -0500; Bill, While I appreciate the creativity, I am thinking that all of the abbreviations we currently use, are both: -short, and -widely understood regardless of one's native language. I guess I'm a die-; /archives//html/WriteLog/2004-09/msg00164.html (8,801 bytes)

Current List: 1 - 2
Page: [1]