Re: 1Re: Problems with the radio carbon dating of the Newport Tower

Eric Stevens wrote:
On Sat, 08 Dec 2007 22:47:32 GMT, "David B." <tronospamchos@xxxxxxxxx>
wrote [concerning the Chronognostic pdf plan of the Newport Tower]:

You can magnify an image a dozen pixels across so that it is hundreds of "screen pixels" across, but the software will still measure it as 12 pixels.

That's interesting. To count the image pixels you have to enlarge the
image to above the size at which it is displayed on the screen. When I
tried enlarging it as the original PDF I found that the lines marking
the edge of the tower image remained sharp: all I could see were the
pixels on the screen. When I tried looking at it with other software
(including photoshop) I found the file was password protected. How did
you manage it?

I used the Print Screen key (and I've checked that this method does not create image distortion on my system by overlaying a Print Screen capture of a plain line-drawn shape on the original file of the same image). However, it turns out that's all rather irrelevant, because- look what you get if you use Print Screen the instant the pdf file starts being drawn:
http://homepages.tesco.net/~trochos/nt-drawn-plan-53pc.jpg
Yes folks, it's layered, and the bottom layer is a digital photo of a hand-drawn plan. The extra details on the hand-drawn plan (which I will be deleting in 24 hours' time) are interesting, but the fact that it's a digital photo means that, indeed, this pdf cannot be used for accurate measurement. Hey ho.

David B.
.

Relevant Pages

  • Re: 1Re: Problems with the radio carbon dating of the Newport Tower
    ... wrote [concerning the Chronognostic pdf plan of the Newport Tower]: ... You can magnify an image a dozen pixels ...
    (sci.archaeology)
  • Re: 1Re: Problems with the radio carbon dating of the Newport Tower
    ... wrote [concerning the Chronognostic pdf plan of the Newport Tower]: ... measure it as 12 pixels. ...
    (sci.archaeology)
  • Re: Forthcoming 2nd ed. of _The Ruby Way_
    ... >> definitely buy a beta copy in PDF form for a hard copy final ... > I don't think the publisher has any plan of such. ... They get a chance to read it before it goes to press (and many of them ...
    (comp.lang.ruby)
  • Re: Chopped up bitmaps in PDF files
    ... it usually manifests, in my experience, as lines of pixels not chunks. ... The chances of it going wrong are greatly enhanced by importing the PDF into Quark/Corel/wherever than postscripting from there. ... When I first started to complain about this on this board years ago, I was usually told "it is Corel's fault"...but I would respond that6 I get the same from Qualr and even adobe apps. ... Each of the PDF files had bitmaps that were broken up into thousands of single line bitmap images each one pixel high by the width of the image. ...
    (comp.publish.prepress)
  • Re: Is 5.0 megapixels enough?
    ... Is 5mp enough to get these size enlargements without too much ... I am not looking for studio quality prints, just pictures ... increase number of pixels in graphic program (like paint shop pro-->resize ... this is usable if you plan to make some images and period. ...
    (rec.photo.digital)