From: elf@ee.ryerson.ca (luis fernandes)
Subject: Acronym expansion caveats
Date: Tue, 14 Jan 1997 12:37:13 -0500 [thread overview]
Message-ID: <199701141737.MAA00755@gemini.ryerson.ca> (raw)
I've not been following the AE thread but I had some thoughts on the
matter last night (excuse me if this has already been discussed).
(One assumption I have made is that there is a function that expands
all the acronyms in a buffer).
1) When someone's post is cited in a follow-up, acronyms in the cited
text should not be expanded; i.e. the original author's post
should be reproduced verbatim.
2) What happens when an acronym has two possiblities; e.g. CGI, in
the www newsgroups is "Common Gateway Interface", and "Computer
Generated Imagery" in the visual-effects/computer graphics
newsgroups.
next reply other threads:[~1997-01-14 17:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-01-14 17:37 luis fernandes [this message]
1997-01-15 1:10 ` Lars Magne Ingebrigtsen
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=199701141737.MAA00755@gemini.ryerson.ca \
--to=elf@ee.ryerson.ca \
/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 NNTP newsgroup(s).