home *** CD-ROM | disk | FTP | other *** search
/ NetNews Usenet Archive 1992 #30 / NN_1992_30.iso / spool / comp / os / mswindo / apps / 6015 < prev    next >
Encoding:
Internet Message Format  |  1992-12-13  |  1.2 KB
  1. Xref: sparky comp.os.ms-windows.apps:6015 comp.os.ms-windows.misc:5442
  2. Newsgroups: comp.os.ms-windows.apps,comp.os.ms-windows.misc
  3. Path: sparky!uunet!spool.mu.edu!wupost!cs.utexas.edu!asuvax!ncar!csn!boulder!ucsu!colfelt
  4. From: colfelt@ucsu.Colorado.EDU (Andrew BW Colfelt)
  5. Subject: Re: Distinguish WinWord and WFW
  6. Message-ID: <1992Dec13.044230.11213@ucsu.Colorado.EDU>
  7. Organization: University of Colorado, Boulder
  8. References: <jcmorris.722454499@mwunix> <1992Nov25.033326.15840@ucsu.Colorado.EDU> <1992Dec02.074743.7971@microsoft.com>
  9. Date: Sun, 13 Dec 1992 04:42:30 GMT
  10. Lines: 27
  11.  
  12. blakeco@microsoft.com (Blake Coverett) writes:
  13.  
  14. >colfelt@ucsu.Colorado.EDU (Andrew BW Colfelt) writes:
  15. >>
  16. >>W4W WFW WfW WinWord 
  17. >>
  18. >>WWG WG Workgroups
  19.  
  20. >Around Microsoft WFW always means Windows for Workgroups. 
  21. >Word for Windows is typically called Word or WinWord.
  22.  
  23. >-Blake (seems like a reasonable convention to me.)
  24.  
  25. Completely reasonable!  Here's a rebuttal:
  26.  
  27. My suggestion, widely accepted or not, is sensitive
  28. to the habit people have already formed, one that
  29. requires no habit-kicking.  Further, "Word" and 
  30. "WinWord" are not really abbreviations.
  31.  
  32. Chaos will prevail, no doubt.
  33.  
  34.  
  35. -- 
  36. Andrew          
  37. Colfelt@ucsu.Colorado.EDU
  38. --
  39.