The perpetual calendar
in [Math]
|
Prev: THE MIND OF MATHEMATICIANS PART 7 " SPATIAL MATHEMATICS , VALUE OF 1 and 3
Next: Exactly why the theories of relativity are complete nonsense- the basic mistake exposed!
From: Peter T. Daniels on 3 Mar 2010 07:11 On Mar 3, 2:47 am, Nick <3-nos...(a)temporary-address.org.uk> wrote: > Glenn Knickerbocker <N...(a)bestweb.net> writes: > > Nick wrote: > >> >> You're the persistent Google groups user IIRC. Â Look it up, or don't > >> ^ > >> Look! There's another one. Whenever you quote me there's a little > >> underscore-like character appears where the second of my double spaces > >> was. > > > Google is translating your second space into a nonbreaking space (0xA0) > > so that it will be displayed in a Web page. > > Which is a perfectly sensible thing to do when displaying it - turn > strings of spaces into alternating string and . I do it myself. > > But why on earth is it then sending it out. Among other things, for the > structure of my post it's /wrong/. It's the /first/ space of a doublet > that should be non-breaking (so it remains at the end of the previous > line). Otherwise Google is telling people to break my sentences with a > space at the start. > Like this. > > I'm very grateful they run a Usenet archive (even if it seems to be > impossible to search it sensibly at the moment, perhaps they can fix > it). I'm getting FTB with them -hide quoted text- -show quoted text- > spewing gunge all over Usenet. > > I>t's properly displayed as > > > just a space, but Emacs must be showing it to you as something else to > > alert you that it's not a "normal" space. Google does change the data, > > but it's your tool, not Peter's, that's changing its graphical image. > > > Then, when you post it, Gnus encodes it in UTF-8. My ancient Netscape > > (which I may finally replace with Thunderbird now that a few more of the > > missing basic functions have been added in version 3) then displays it > > without decoding it, so I wind up quoting it as an A-circumflex followed > > by a space (0x4120). > > > I still think it would be nice if mail and news tools left 8-bit data > > unencoded when it didn't use any of the code points that differ between > > the ISO 8859 and Windows code pages, unless some other code page was > > specified. > > When I wrote it, of course, it didn't. So Google is making a post that > I write that you can easily read and transforming it, when quoted, into > something that's messy and that you can't easily quote. > > See above. No one but you sees "something that's messy and that you can't easily quote."
From: James Silverton on 3 Mar 2010 08:32 PaulJK wrote on Wed, 3 Mar 2010 16:58:29 +1300: > James Silverton wrote: >> PaulJK wrote on Tue, 2 Mar 2010 21:01:20 +1300: >> >>> Algol 60, i.e. thirty years before Fortan90, allowed general >>> expressions in array declarations, e.g. >> >>> real array A(i*2 : fcall(p,3)); >> >>> It wasn't particularly difficult to compile, since all code >>> to compile general arithmetical expressions was already >>> there. The expression (i*2) and the function call >>> (fcall(p,3)) had to be evaluated at run time but that wasn't >>> difficult either. The whole array declaration was evaluated >>> at run time as if it were a function call which resulted in >>> an area of memory being reserved on the top of the stack by >>> pointing the top of the stack pointer beyond it. >> >> Actually, the first compiled language that I used was Algol >> in 1960. > Not that it matters much but do you remember was it Algol60 > or Algol58? > The year 1960 sounds to me a bit too early for an actual > commercial implemetation of Algol60. >> The >> resulting programs on the Burrouughs 220 were so pathetically >> unoptimized and slow that I ended up using machine language >> and a primitive assembler. >> >> I never brought myself to use Algol again. It probably was the 58 version but I am not very familiar with the history of Algol. I do seem to remember that the paper tape with the compiler was gotten by a somewhat informal arrangement with the Burroughs company. -- James Silverton Potomac, Maryland Email, with obvious alterations: not.jim.silverton.at.verizon.not
From: Nick on 3 Mar 2010 15:17 "Peter T. Daniels" <grammatim(a)verizon.net> writes: > From: "Peter T. Daniels" <grammatim(a)verizon.net> > Subject: Re: The perpetual calendar > Newsgroups: sci.math, sci.physics, sci.astro, sci.lang, alt.usage.english > Date: Wed, 3 Mar 2010 04:11:33 -0800 (PST) > Organization: http://groups.google.com > > On Mar 3, 2:47 am, Nick <3-nos...(a)temporary-address.org.uk> wrote: >> Glenn Knickerbocker <N...(a)bestweb.net> writes: >> > Nick wrote: >> >> >> You're the persistent Google groups user IIRC. Â Look it up, or don't >> >> ^ >> >> Look! There's another one. Whenever you quote me there's a little >> >> underscore-like character appears where the second of my double spaces >> >> was. >> >> > Google is translating your second space into a nonbreaking space (0xA0) >> > so that it will be displayed in a Web page. >> >> Which is a perfectly sensible thing to do when displaying it - turn >> strings of spaces into alternating string and . I do it myself. >> >> But why on earth is it then sending it out. Among other things, for the >> structure of my post it's /wrong/. It's the /first/ space of a doublet >> that should be non-breaking (so it remains at the end of the previous >> line). Otherwise Google is telling people to break my sentences with a >> space at the start. >> Like this. >> >> I'm very grateful they run a Usenet archive (even if it seems to be >> impossible to search it sensibly at the moment, perhaps they can fix >> it). I'm getting FTB with them -hide quoted text- -show quoted text- >> spewing gunge all over Usenet. >> >> I>t's properly displayed as >> >> > just a space, but Emacs must be showing it to you as something else to >> > alert you that it's not a "normal" space. Google does change the data, >> > but it's your tool, not Peter's, that's changing its graphical image. >> >> > Then, when you post it, Gnus encodes it in UTF-8. My ancient Netscape >> > (which I may finally replace with Thunderbird now that a few more of the >> > missing basic functions have been added in version 3) then displays it >> > without decoding it, so I wind up quoting it as an A-circumflex followed >> > by a space (0x4120). >> >> > I still think it would be nice if mail and news tools left 8-bit data >> > unencoded when it didn't use any of the code points that differ between >> > the ISO 8859 and Windows code pages, unless some other code page was >> > specified. >> >> When I wrote it, of course, it didn't. So Google is making a post that >> I write that you can easily read and transforming it, when quoted, into >> something that's messy and that you can't easily quote. >> >> See above. > > No one but you sees "something that's messy and that you can't easily > quote." [whole post left in for context] Yes, Glenn does. See above. -- Online waterways route planner | http://canalplan.eu Plan trips, see photos, check facilities | http://canalplan.org.uk
From: John Holmes on 4 Mar 2010 05:05 PaulJK wrote: > > When I lived in Toorak, Melbourne Cup Day was definitely > a paid state holiday. I don't think so. It has only ever been a holiday in the Melbourne area, not statewide. Once you are more than about 80-100 km from Melbourne, you find they have their own country race day or agricultural show day local holidays on other dates instead. -- Regards John for mail: my initials plus a u e at tpg dot com dot au
From: Lewis on 4 Mar 2010 07:01
On 02-Mar-10 08:48, Evan Kirshenbaum wrote: > Lewis<notmyemail(a)example.com> writes: >> Current machine has 7TB of disk space and 6GB of RAM. > > That's a big disk for today, though, you have to admit. I don't think > I've seen more than about 1TB actually on a machine. Most the people I know, fellow geeks, have at least 4TB of storage, usually broken down into c.3TB for data storage and 1TB for Time Machine. I have a friend whose home server was just upgrade to 15.75TB, and another who is putting in 5x2TB drives at the end of the month, pushing his home server 22TB (but 4TB of that is 'lost' to RAID). If I had the money, I'd be bumping up to ~10TB right now as I am running 85% full. The real trouble is, there is no way to backup these drives, so the only solution is to add more drives and RAID them to mitigate against failure and backup the really important stuff to yet more drives When I dropped in my 2x1.5TB drives last year (RAID0) I thought, "well, it's going to be a good long while before I fill up 3TB!" Yeah, not so much. I have less than 100GB free of that 3TB, though I have some DVD images on it that, once I finish converting them to h264 I can delete, so that will free up 50GB or so. -- "I'm not bad; I'm just drawn that way." |