9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Nigel Roles <nigel@9fs.org>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] A prick into the wasps' nest ;-)
Date: Thu, 10 Jun 2004 11:36:09 +0100	[thread overview]
Message-ID: <40C83999.6040602@9fs.org> (raw)
In-Reply-To: <BCEE8679.1594%andrew.simmons@monitorbm.co.nz>

Andrew Simmons wrote:

>Surely a shade harsh? And a pedant might claim that PAL, NTSC, and SECAM are
>colour encoding systems, and as such independent of frame rate. Not to
>  
>
Yes, I think you'd have to be a pedant to claim that they weren't video 
standards.
Sorry if I appeared harsh; It was the preceding sequence of gun related
stuff that got me going; I was about to moan about it anyway, and then hit
this email.

>mention the fact that Fowler prefers "recognize" to "recognise", and claims
>that "synthetize", not "synthesize" is the correct formation.
>
>  
>
I have to admit that synthetize was a new one on me; I can now bore at 
parties
with that one. Looking back I see that 'interpolate' would have been a more
accurate word in the first place.

>Oh right, so you have to know what you're talking about if you're going to
>post to 9fans? If that were the case, then I'd certainly never ... ah, I see
>what you mean. Better shut up now.
>
>  
>
With a chap from Snell & Wilcox on the list I thought through what I 
posted, yes!




  reply	other threads:[~2004-06-10 10:36 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-10  9:43 Andrew Simmons
2004-06-10 10:36 ` Nigel Roles [this message]
     [not found] <20040609125113.UCQG24541.imf23aec.mail.bellsouth.net@Xaplos>
     [not found] ` <4fa4328626f76766f4799367fc0550c7@vitanuova.com>
2004-06-09 18:41   ` boyd, rounin
2004-06-10  8:16   ` vdharani
2004-06-10  3:25     ` boyd, rounin
2004-06-10  5:45       ` Nigel Roles
2004-06-10  9:20         ` Steve Simon
2004-06-10  9:20         ` Bruce Ellis
2004-06-10 14:55         ` boyd, rounin
     [not found] <40C6C916.5080004@chunder.com>
2004-06-09 15:04 ` Mark F Rodriguez
2004-06-09 16:04   ` Bruce Ellis
2004-06-09 16:08     ` rog
2004-06-09 16:11       ` Bruce Ellis
2004-06-09 18:54   ` boyd, rounin
  -- strict thread matches above, loose matches on Subject: below --
2004-06-08  6:51 cej
2004-06-08  8:17 ` Vladimir Los
2004-06-09 23:10   ` kim kubik
2004-06-09 23:22     ` boyd, rounin
2004-06-09 23:40       ` George Michaelson
2004-06-09 23:41         ` boyd, rounin
2004-06-09 23:41       ` andrey mirtchovski
2004-06-09 23:44         ` boyd, rounin
2004-06-09 23:55           ` Geoff Collyer
2004-06-09 23:27     ` rog
2004-06-10  8:03     ` Vladimir Los
2004-06-07  7:09 cej
2004-06-07 15:53 ` Rob Pike
2004-06-08  7:32   ` Vladimir Los
2004-06-08 18:18     ` Sape Mullender
2004-06-08 18:55       ` Mark F Rodriguez
2004-06-08 18:58         ` William Josephson
2004-06-08 19:05         ` rog
2004-06-08 19:39           ` Mark F Rodriguez
2004-06-08 20:50             ` boyd, rounin
     [not found]     ` <40C6C6E8.1000302@chunder.com>
2004-06-20 22:35       ` vdharani

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=40C83999.6040602@9fs.org \
    --to=nigel@9fs.org \
    --cc=9fans@cse.psu.edu \
    /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).