Prev: Why html5/proprietary H.264 will fail (was) Scribd "scrappingFlash and betting the company on HTML5"
Next: Airport turns off on reboot
From: Jon Ribbens on 6 May 2010 21:50 On 2010-05-06, BreadWithSpam(a)fractious.net <BreadWithSpam(a)fractious.net> wrote: > Jolly Roger <jollyroger(a)pobox.com> writes: >> It looked fine both times here, though the initial post was in a >> different font on my screen, because you sent it with 8-bit UTF 16 >> encoding. I probably have MT-NewsWatcher set to use a different font for >> such posts. If it looked fine, it only did so because your newsreader is broken, I'm afraid ;-) > I realized afterwards that it was because of the quoted included > material from Michelle's post. There were a couple of 8-bit > characters in there and my newsreader detected them and went > and encoded the whole message as 8bit. That's not the problem, the problem is that the article claimed it was in UTF-16 (i.e. 2 bytes per character) but actually wasn't.
From: David Empson on 7 May 2010 01:25 Your Name <your.name(a)isp.com> wrote: > In article <Xns9D70C46A4D1F9noonehomecom(a)74.209.131.13>, Larry > <noone(a)home.com> wrote: > > > Michelle Steiner <michelle(a)michelle.org> wrote in news:michelle- > > 034CAB.12355406052010(a)62-183-169-81.bb.dnainternet.fi: > > > > > I expect that by 2015, there will be something else to replace H264. > > > > By 2015, they'll all be looking back and laughing at the iPhone....like > > they do the Newton, Palm PIlot, Power book or Pentium II PCs now. > > > > iPhone will be long gone by then, replaced by 12G at 480GB/second > <snip the usual Loser Larry irrelevant and incomprehensible drivel> > > The "iPhone" name is likely to be around for a long while, although the > models will of course be updated over the years. The "iMac" name has been > around for about 10 years already The iMac was introduced 12 years ago this month, though it wasn't available until August. > and shows no sign of being replaced (even if the "i" has lost its > original "Internet" menaing). Apple's use of the "i" prefix has always meant personal as opposed to professional (it is a bit like "my", thus "iMac" is "my Mac"). iBook vs PowerBook iMac vs PowerMac iMovie vs Final Cut Pro (or Express) iDVD vs DVD Studio Pro iPhoto vs Aperture iTunes, iPod, iPhone etc. have no professional equivalent from Apple and are inherently personal products. > As for the Newton, it was way ahead of it's time (and is STILL the best > PDA you can get) and without it there would probably never have been a > Palm Pilot. -- David Empson dempson(a)actrix.gen.nz
From: Warren Oates on 7 May 2010 09:08 In article <Xns9D70C46A4D1F9noonehomecom(a)74.209.131.13>, Larry <noone(a)home.com> wrote: > By 2015, they'll all be looking back and laughing at the iPhone....like > they do the Newton, Palm PIlot, Power book or Pentium II PCs now. But will we finally have flying cars? -- Very old woody beets will never cook tender. -- Fannie Farmer
From: Jolly Roger on 7 May 2010 10:13 In article <slrnhu6sfr.f7v.jon+usenet(a)snowy.squish.net>, Jon Ribbens <jon+usenet(a)unequivocal.co.uk> wrote: > On 2010-05-06, BreadWithSpam(a)fractious.net <BreadWithSpam(a)fractious.net> > wrote: > > Jolly Roger <jollyroger(a)pobox.com> writes: > >> It looked fine both times here, though the initial post was in a > >> different font on my screen, because you sent it with 8-bit UTF 16 > >> encoding. I probably have MT-NewsWatcher set to use a different font for > >> such posts. > > If it looked fine, it only did so because your newsreader is broken, > I'm afraid ;-) In that case, I suppose I'm glad it's "broken" in this case, since it actually allowed me to read the message. : ) How did it look for you? -- Send responses to the relevant news group rather than email to me. E-mail sent to this address may be devoured by my very hungry SPAM filter. Due to Google's refusal to prevent spammers from posting messages through their servers, I often ignore posts from Google Groups. Use a real news client if you want me to see your posts. JR
From: Jolly Roger on 7 May 2010 10:18
In article <hrvmv5$hvi$1(a)news.eternal-september.org>, Larry Gusaas <larry.gusaas(a)gmail.com> wrote: > On 2010/05/06 10:42 AM Jolly Roger wrote: > > In article<yob8w7xrosf.fsf(a)panix2.panix.com>, > > BreadWithSpam(a)fractious.net wrote: > > > > > >> BreadWithSpam(a)fractious.net writes: > >> > >> [Dunno how, but my post got mangled, at least it looked that > >> way on my server. Trying only once more, and my apologies if > >> this doesn't fix it] > >> > > It looked fine both times here, though the initial post was in a > > different font on my screen, because you sent it with 8-bit UTF 16 > > encoding. I probably have MT-NewsWatcher set to use a different font for > > such posts. > > > > Your first post had these headers: > > > > Content-Type: text/plain; charset=utf-16be > > Content-Transfer-Encoding: 8bit > > > > Your first post read as Chinese characters until I changed the character > encoding to UTF-8 and then it read in English. I've set my news reader to use a Western font for everything, which is why I was able to read it. I don't read any asian news groups, so I don't need my news reader to display Chinese or any other asian characters. : ) -- Send responses to the relevant news group rather than email to me. E-mail sent to this address may be devoured by my very hungry SPAM filter. Due to Google's refusal to prevent spammers from posting messages through their servers, I often ignore posts from Google Groups. Use a real news client if you want me to see your posts. JR |