From: Shankar Unni <shankar@cotagesoft.com>
To: cygwin@cygwin.com
Subject: Re: wtf wtf
Date: Mon, 03 Nov 2003 20:07:00 -0000 [thread overview]
Message-ID: <bo6ch6$soa$1@sea.gmane.org> (raw)
In-Reply-To: <gkrcqv89n4epskombnn5rfuaugd4km34g0@4ax.com>
zzapper wrote:
> What I really want to know is why there are so few acronyms in WTF,
> does anyone have bigger datafiles??
Because as distributed, it was not intended to be a universal acronym
dictionary (which could run to millions of acronyms).
WTF has generally been used to expand acronyms for phrases used in
typical mailing list/newsgroup settings (e.g. IMO, etc.)
But hey, if someone has the energy to create *and maintain* a univeral
acronym library, go for it!
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
next prev parent reply other threads:[~2003-11-03 20:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-03 13:24 kevin.lawton
2003-11-03 15:10 ` zzapper
2003-11-03 20:07 ` Shankar Unni [this message]
2003-11-03 20:35 ` zzapper
2003-11-03 23:24 ` Igor Pechtchanski
-- strict thread matches above, loose matches on Subject: below --
2003-11-02 12:10 zzapper
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='bo6ch6$soa$1@sea.gmane.org' \
--to=shankar@cotagesoft.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).