The value of the starting position for any useful work would be such a large number that simply expressing the number would in almost all cases take far more bytes than to store the work itself (barring some infinitesimally unlikely occurrence, which is just as unlikely as finding the work randomly occurring in any other form in nature, such as twigs falling from a tree and arranging, just by random luck, into letters and spelling a message). In fact, since the stream of digits of pi is infinitely long, not only can every work that has ever, does, and will ever exist be found in it, but every single work must lie buried an infinite number of times! For any work, you could come up with as many numbers as you want to describe its position.
Small numbers indicating a quantity cannot be copyrighted, but the numbers necessary to express these digit positions would be far beyond any useful quantity imaginable. Just as all digital data is reducible to a long number, these digit positions are encoded data, not useful quantities, and therefore would be protected by copyright as just a representation of the works they are "pointing" to in the digits of pi.
For Windows, Total Recorder will record to disk the sound output of any program. It can either play it through the sound card also, or remain silent. It can also be scheduled to start and stop at a specific time, using command-line parameters or its built-in scheduler. You can schedule RealPlayer or any other media player to start a minute or so after the time Total Recorder has been scheduled to start to create a completely automatic system to record recurring broadcasts.
One thing that is often forgotten about HTML is that it is intended to define the structure of a document, not its presentation. That is why elements and attributes controlling appearance (color, alignment, etc.) have been deprecated in the HTML 4 standard. All aspects of a page's presentation should be in style sheets. This maximizes accessibility. (See http://www.w3.org/TR/html4/intro/intro.html#h-2.3) With this design system, if I don't like the wasted space of a 3-inch column of text going down my 12-inch wide monitor, I can disable the style sheets and view the text from one side of the screen to the other.
Another thing that really bugs me is the now-popular trend to make web pages look like printed pages; for example, with columns down the left and right of EVERY page of a web site with the standard menu of links. (Slashdot does this.) These should be in frames, so the body is a page in the middle frame with nothing but the body text in that HTML file. Again, accessibility is sacrificed for appearance, and in a portable, small-screen text-based device, it will be unreadable. A text-to-speech reader will not work on the page without reading the entire left menu column on every page.
I would never trust web design advice from www.lynda.com with their design philosophy. They don't understand the purpose of HTML, and make the types of mistakes I pointed out. (Of course, they wouldn't regard them as mistakes, they do it intentionally.) Also, look in the source of the front page; there's a script with a comment reading
THIS IS A WONDERFUL LITTLE SCRIPT IT WILL BREAK ANY PAGE OUT OF FRAMES
All that does on the front page is reduce accessibility ON PURPOSE. What the hell is the point of that??
If a web page is supposed to have an exact appearance that will work only on desktop computers with large graphical displays, HTML is not the proper tool. You might as well make a big GIF imagemap with all the text and hyperlinks with only the minimal HTML needed to operate the imagemap.
I wish more web sites would use HTML properly. The increase in accessibility would make possible such browser features as automatic table of contents generators (from the H1..H6 tags), collapsible outlines (from the OL, UL, and LI tags), and resizable tables. But they would choke on most major sites today because they abuse HTML. Perhaps the only way that web designers will change is when HTML software actually starts to take full advantage of the HTML elements.
Slashdot Mirror
The value of the starting position for any useful work would be such a large number that simply expressing the number would in almost all cases take far more bytes than to store the work itself (barring some infinitesimally unlikely occurrence, which is just as unlikely as finding the work randomly occurring in any other form in nature, such as twigs falling from a tree and arranging, just by random luck, into letters and spelling a message). In fact, since the stream of digits of pi is infinitely long, not only can every work that has ever, does, and will ever exist be found in it, but every single work must lie buried an infinite number of times! For any work, you could come up with as many numbers as you want to describe its position.
Small numbers indicating a quantity cannot be copyrighted, but the numbers necessary to express these digit positions would be far beyond any useful quantity imaginable. Just as all digital data is reducible to a long number, these digit positions are encoded data, not useful quantities, and therefore would be protected by copyright as just a representation of the works they are "pointing" to in the digits of pi.
For Windows, Total Recorder will record to disk the sound output of any program. It can either play it through the sound card also, or remain silent. It can also be scheduled to start and stop at a specific time, using command-line parameters or its built-in scheduler. You can schedule RealPlayer or any other media player to start a minute or so after the time Total Recorder has been scheduled to start to create a completely automatic system to record recurring broadcasts.
One thing that is often forgotten about HTML is that it is intended to define the structure of a document, not its presentation. That is why elements and attributes controlling appearance (color, alignment, etc.) have been deprecated in the HTML 4 standard. All aspects of a page's presentation should be in style sheets. This maximizes accessibility. (See http://www.w3.org/TR/html4/intro/intro.html#h-2.3) With this design system, if I don't like the wasted space of a 3-inch column of text going down my 12-inch wide monitor, I can disable the style sheets and view the text from one side of the screen to the other.
Another thing that really bugs me is the now-popular trend to make web pages look like printed pages; for example, with columns down the left and right of EVERY page of a web site with the standard menu of links. (Slashdot does this.) These should be in frames, so the body is a page in the middle frame with nothing but the body text in that HTML file. Again, accessibility is sacrificed for appearance, and in a portable, small-screen text-based device, it will be unreadable. A text-to-speech reader will not work on the page without reading the entire left menu column on every page.
I would never trust web design advice from www.lynda.com with their design philosophy. They don't understand the purpose of HTML, and make the types of mistakes I pointed out. (Of course, they wouldn't regard them as mistakes, they do it intentionally.) Also, look in the source of the front page; there's a script with a comment reading
THIS IS A WONDERFUL LITTLE SCRIPT
IT WILL BREAK ANY PAGE OUT OF FRAMES
All that does on the front page is reduce accessibility ON PURPOSE. What the hell is the point of that??
If a web page is supposed to have an exact appearance that will work only on desktop computers with large graphical displays, HTML is not the proper tool. You might as well make a big GIF imagemap with all the text and hyperlinks with only the minimal HTML needed to operate the imagemap.
I wish more web sites would use HTML properly. The increase in accessibility would make possible such browser features as automatic table of contents generators (from the H1..H6 tags), collapsible outlines (from the OL, UL, and LI tags), and resizable tables. But they would choke on most major sites today because they abuse HTML. Perhaps the only way that web designers will change is when HTML software actually starts to take full advantage of the HTML elements.