Moderated Obama birth certificate CT / SSN CT / Birther discussion

Status
Not open for further replies.
I think the key word here is "render". While Pshop can interpret vector graphics, it is fundamentally unable to present them, it must perforce render them as bitmaps of some type. That is its nature, and that nature is as intended.

There is (and needs to be) some crossover in data representation among vector and raster editors. Photoshop maintains the notion of a "path" but it considers them a separate animal from Layers: the Layers, Channels, and Paths displays. Paths are tacked on to the Photoshop data model.

Similarly Illustrator allows you to fill a rectangular vector object with a sampled (i.e., raster) texture, effectively producing a pixel map "object." All that happens under the hood when you import a raster image. You see only something that looks like an image, but has traditional Illustrator object manipulation handles. Several such objects can reside in an Illustrator Layer, unlike a Photoshop Layer.

PDF has no such bias. Among its displayable objects there is no preference for data format or organization. A PDF file is a flat bag of dissimilar objects, grouped only for convenience of specifying the rendering parameters to the relevant "procedure set."
 
The basic difference...

In PDF 1.6 or 1.7 (I don't remember which) the elementary PDF rendering engine was changed to allow more transparency effects. Of course that doesn't affect the PDF 1.3 that Obama's birth certificate was written it, but it does move the modern PDF closer to the Photoshop model of a z-buffered cumulative image.

With a /ProcSet you can specify an object rendering order, but you cannot guarantee the order that /ProcSets will be rendered in. Hence the short cut I keep referring to. Specifying the text as a bitmask rather than a bitmap means that it will render the same regardless of order -- so long a the desired rendering color for "foreground" image elements is established in the graphics state.

This is radically different from Photoshop's model. In Ps you evaluate the layers in strict ascending z-order. But in PDF 1.3, you can render the pixel map and the bitmasks in any order, with the same visual result. This is, again, suggested by the "unordered bag of objects" data model in PDF.

One of the ways the optimizer chops up images is spatially, by necessary depth. It is as if one takes a printed photograph and cuts it up with an X-Acto knife according to how much pixel depth needs to be supplied to render the object with acceptable quality. Hence my scan of the magazine page, when so optimized, produced objects that provided 24 bpp where real-world images were used, 16 bpp where it was mostly black text on white background, and 8 bpp for the margins. If you instruct Ac(robat) to selectively display the objects, it looks like a jigsaw puzzle. You can render them in any order because they're spatially distinct.

And where the color is uniformly the graphics "background" you can represent it as a bitmask and let that background show through. The optimizer did that with the black nameplate text at the top of the page.

When I selected optimization for OCR, it produced one object that was the body text on its white background (although it failed to recognize any text). The photographs and diagrams on the page were separate objects. Additionally the PDF contained /PDF path objects that apparently took a stab at interpreting some of the characters on the page.

As Abbadon and I have lamented, later versions of PDF produce more and more baroque language constructs, attempting to be all things to all people. 1.3 and 1.4 seem to be good baseline standards for most static documents.
 
Told ya you would kick me around. :D

There is (and needs to be) some crossover in data representation among vector and raster editors. Photoshop maintains the notion of a "path" but it considers them a separate animal from Layers: the Layers, Channels, and Paths displays. Paths are tacked on to the Photoshop data model.
I always had the view that Pshop and illustrator were having some odd internal domestic dispute.

Similarly Illustrator allows you to fill a rectangular vector object with a sampled (i.e., raster) texture, effectively producing a pixel map "object." All that happens under the hood when you import a raster image. You see only something that looks like an image, but has traditional Illustrator object manipulation handles. Several such objects can reside in an Illustrator Layer, unlike a Photoshop Layer.
Did I mention the scars on my back? Try coding it! Yeah, you have.
Everyone wants, but no-one wants to deal with the limitations of the software. In this, the truthers ignore the way it actually works. I don't get that.

PDF has no such bias. Among its displayable objects there is no preference for data format or organization. A PDF file is a flat bag of dissimilar objects, grouped only for convenience of specifying the rendering parameters to the relevant "procedure set."
Geez, you are making me nostalgic now. :D
 
Did I mention the scars on my back? Try coding it! Yeah, you have.

Yes, although certain people here can't see beyond accusations of "technobabble." I've programmed PDF exporters as well as the systems that produced the exportable content in the first place. Our data model was a directed acyclic graph. We didn't even try to represent it in any sort of PDF object hierarchy.

Everyone wants, but no-one wants to deal with the limitations of the software. In this, the truthers ignore the way it actually works. I don't get that.

Because the way it works is not the way they need it to work for their theory. Hence the word games, "Yeah, it's labeled as 'object' and 'group' but it's really a 'layer' right? Right!?"
 
Jay,

I've really appreciated your responses. I'm curious though, would you agree that the objects in question, in Illustrator, behave somewhat like layers. You can turn them off and on. I'm assuming you could change their order. So there is some basis for an amateur to think they are the equivalent, right?

I'm a DBMS programmer but I was a graphics production manager for 7 years and have done a lot of work with Illustrator and Photoshop though to be honest I'm more than a decade behind the time on those programs. I still use Photoshop 6 and prefer my old, old extinct copy of Freehand to Illustrator. So I'll happily concede that I'm hardly an expert. :)

ETA: I forgot abaddon. I appreciate your input also and feel free to comment.
 
Last edited:
Yes, although certain people here can't see beyond accusations of "technobabble." I've programmed PDF exporters as well as the systems that produced the exportable content in the first place. Our data model was a directed acyclic graph. We didn't even try to represent it in any sort of PDF object hierarchy.
In my case, outputing a mixed bag of encoded text elements with graphics elements also.

The design meetings were all sorts of fun, and I allowed free reign. Some cracking ideas ensued.

The spec meetings were a whole other case. The most important word I discovered was "No".

Scope creep is insidious.

Because the way it works is not the way they need it to work for their theory. Hence the word games, "Yeah, it's labeled as 'object' and 'group' but it's really a 'layer' right? Right!?"
Oh well, if the facts don't work for the theory du jour, just make up some new facts.
 
I'm curious though, would you agree that the objects in question, in Illustrator, behave somewhat like layers. You can turn them off and on.

I don't consider that equivalent behavior. In any content-authoring system you can exempt any data element from rendering. That's not enough to say they are similar.

In Ai if you "turn off" a layer it's tantamount to "turning off" all the objects it contains. The Layer is a container and only a container. It serves only to aggregate metadata about the objects themselves. It is not by itself visible or renderable.

I'm assuming you could change their order. So there is some basis for an amateur to think they are the equivalent, right?

You can change the order of objects, because Illustrator's rendering model is analogous to the z-buffer method in Ps. Ai has a well-defined stacking order. And if you import a PDF into Illustrator, stacking order matters. It does not matter in the original PDF.

Again the big part of the problem is that when you import a PDF into a program that has a different native data model, you're looking at a representation (as best as can be achieved) of the data from the PDF, expressed in the native model. Once imported and thus converted, it becomes subject to the constraints and behavior of the native data model. So objects from a PDF that are imported as Ai objects will behave like Ai objects. And the whole Ai document will behave as an Ai document, not a PDF document.

That is the basis for questioning Illustrator as the tool these novices are using to "inspect the PDF." To answer your question, yes a novice could see some superficial similarities in the respective data models and wrongly (but not irrationally) conclude that the models are equivalent enough for his purpose.
 
I'm curious though, would you agree that the objects in question, in Illustrator, behave somewhat like layers. You can turn them off and on.

I don't consider that equivalent behavior. In any content-authoring system you can exempt any data element from rendering. That's not enough to say they are similar.

In Ai if you "turn off" a layer it's tantamount to "turning off" all the objects it contains. The Layer is a container and only a container. It serves only to aggregate metadata about the objects themselves. It is not by itself visible or renderable.

I'm assuming you could change their order. So there is some basis for an amateur to think they are the equivalent, right?

You can change the order of Ai objects, because Illustrator's rendering model is analogous to the z-buffer method in Ps. Ai has a well-defined stacking order. And if you import a PDF into Illustrator, stacking order matters. It does not matter in the original PDF.

Again the big part of the problem is that when you import a PDF into a program that has a different native data model, you're looking at a representation (as best as can be achieved) of the data from the PDF, expressed in the native model. Once imported and thus converted, it becomes subject to the constraints and behavior of the native data model. So objects from a PDF that are imported as Ai objects will behave like Ai objects. And the whole Ai document will behave as an Ai document, not a PDF document.

That is the basis for questioning Illustrator as the tool these novices are using to "inspect the PDF." To answer your question, yes a novice could see some superficial similarities in the respective data models and wrongly (but not irrationally) conclude that the models are equivalent enough for his purpose.
 
I don't consider that equivalent behavior. In any content-authoring system you can exempt any data element from rendering. That's not enough to say they are similar.
I think you misunderstand my point (emphasis on "think").

My point was that you can turn on and of the objects by selecting and deselecting them (the objects and not the layers) in the layers palatte. That behavior is very similar to the layers function, right? I'm not adept at illustrator but I would be hard pressed to tell you what the difference is from a UI standpoint or even what the functional differences would be. Conceded that could be in part to my inexperience with Illustrator and perhaps Illustrator lets you fundamentally work with layers in a way it won't let you work with objects. Sorry if you have gone over that and I missed your explanation. I've not read every post.

Let me make certain that you understand that I'm not trying to pick a fight or support RP at all. He's been out of gas for a long time.

So, let me ask you a question, give me an example of how I could use layers that I cannot use objects and that would help me understand better. But one more time, so far, from my perspective I can see how objects can seem like layers. Are you saying that to do so is a mistake no on should ever make because objects and layers have nothing in common whatsoever?

ETA:
To answer your question, yes a novice could see some superficial similarities in the respective data models and wrongly (but not irrationally) conclude that the models are equivalent enough for his purpose.
Please ignore my last question. I missed this. Sorry. I'm probably making much more of this than is warranted. I'm just not experienced enough.
 
Last edited:
My point was that you can turn on and of the objects by selecting and deselecting them (the objects and not the layers) in the layers palatte.

Yes, in the Ai Layers panel there is a visibility widget for each object.

That behavior is very similar to the layers function, right?

"The layers function" is broad and ambiguous.

In Ps each layer has a visibility widget. But then all you have in the Layers panel is layers.

In Ai, each object, object group, and layer has a visibility widget. But in that panel you have layers, groups, and objects. The visibility widget for aggregators (layers and groups) affects their subordinates.

I'm not adept at illustrator but I would be hard pressed to tell you what the difference is from UI stand point or even what the functional differences would be.

I see it as a three-way problem among PDF, Illustrator, and Photoshop. You want specifically to talk about Illustrator versus Photoshop and that's relevant to how Zebest misunderstood her information. The problem as it affects the validity of the Obama PDF is the three-way problem: Zebest claims the document was created in Photoshop, exported as a PDF, and she's now examining it in Illustrator.

I explain more below. But the similarity of the UI and the congruence of some of its widgets masks the underlying dissimilarity that defeats the Birther claims of the chain of provenance they propose. A Photoshop layer, which is itself a displayable entity, does not become a PDF object, which then becomes an Illustrator layer, which is a container only. That's a Birther fantasy.

If you look at a classic Photoshop image in the Layers dialogue you will see a flat (i.e., non-hierarchical) list of layers, which are displayable objects themselves.

If you look at a classic Illustrator document in its Layers dialog, you will see a deep hierarchy, with Layers at the outermost level.

Some of the controls seem similar and have a superficially similar function. But Adobe's desire to uniformalize the UI for Creative Suite does not mean they've made the underlying entities congruent.

Sorry if you have gone over that and I missed your explanation. I've not read every post.

Well I've given the equivalent of about two days of college-level lectures in recent days, so I'm sure not everyone has read all of them.

So, let me ask you a question, give me an example of how I could use layers that I cannot use objects and that would help me understand better. But one more time, so far, from my perspective I can see how objects can seem like layers. Are you saying that to do so is a mistake no on should ever make because objects and layers have nothing in common whatsoever?

In Photoshop a Layer is a displayable data object. You create a fresh new document and before you can put any content into it you have to create a layer in which to put it. The layer here does not contain data objects, it is the data object. The content-specific bits live there. A Photoshop image is a list of layers arranged in order.

In Illustrator a Layer is merely a container. It serves only to group objects together so that they can be treated similarly. The objects themselves are the displayable entities. The Layer is just a convenience for moving and controlling them as a group. They are ordered at the document level and contained ordered objects. Similarly you get a default Layer when you open a new Illustrator document. But rather than manipulating the layer as a displayable object itself, you add displayable objects to it -- objects that can be moved among layers.

Objects (either PDF or Illustrator) are atomic, meaning they cannot be further decomposed into meaningful entities in the data model. Photoshop layers are similarly atomic only in that they cannot easily be taken apart in the program and manipulated as decomposed parts. Layers in Illustrator are not atomic; they are aggregates or composites. They exist only to provide a single reference for their constituents.
 
Yes, in the Ai Layers panel there is a visibility widget for each object.

"The layers function" is broad and ambiguous.

In Ps each layer has a visibility widget. But then all you have in the Layers panel is layers.

In Ai, each object, object group, and layer has a visibility widget. But in that panel you have layers, groups, and objects. The visibility widget for aggregators (layers and groups) affects their subordinates.

I see it as a three-way problem among PDF, Illustrator, and Photoshop. You want specifically to talk about Illustrator versus Photoshop and that's relevant to how Zebest misunderstood her information. The problem as it affects the validity of the Obama PDF is the three-way problem: Zebest claims the document was created in Photoshop, exported as a PDF, and she's now examining it in Illustrator.

I explain more below. But the similarity of the UI and the congruence of some of its widgets masks the underlying dissimilarity that defeats the Birther claims of the chain of provenance they propose. A Photoshop layer, which is itself a displayable entity, does not become a PDF object, which then becomes an Illustrator layer, which is a container only. That's a Birther fantasy.

If you look at a classic Photoshop image in the Layers dialogue you will see a flat (i.e., non-hierarchical) list of layers, which are displayable objects themselves.

If you look at a classic Illustrator document in its Layers dialog, you will see a deep hierarchy, with Layers at the outermost level.

Some of the controls seem similar and have a superficially similar function. But Adobe's desire to uniformalize the UI for Creative Suite does not mean they've made the underlying entities congruent.


Well I've given the equivalent of about two days of college-level lectures in recent days, so I'm sure not everyone has read all of them.

In Photoshop a Layer is a displayable data object. You create a fresh new document and before you can put any content into it you have to create a layer in which to put it. The layer here does not contain data objects, it is the data object. The content-specific bits live there. A Photoshop image is a list of layers arranged in order.

In Illustrator a Layer is merely a container. It serves only to group objects together so that they can be treated similarly. The objects themselves are the displayable entities. The Layer is just a convenience for moving and controlling them as a group. They are ordered at the document level and contained ordered objects. Similarly you get a default Layer when you open a new Illustrator document. But rather than manipulating the layer as a displayable object itself, you add displayable objects to it -- objects that can be moved among layers.

Objects (either PDF or Illustrator) are atomic, meaning they cannot be further decomposed into meaningful entities in the data model. Photoshop layers are similarly atomic only in that they cannot easily be taken apart in the program and manipulated as decomposed parts. Layers in Illustrator are not atomic; they are aggregates or composites. They exist only to provide a single reference for their constituents.
Thanks Jay. I really appreciate it. BTW: I edited my last post as I had made an error in that you had already answered one of my questions.
 
Last edited:
Thanks Jay. I really appreciate it. BTW: I edited my last post as I had made an error in that you had already answered one of my questions.

Yes, your revised question deserved an answer, in my opinion. Adobe markets the Creative Suite, which is a suite of formerly standalone products adapted well to different tasks. In organizing them as a suite, they made several changes to program function (e.g., blurring the distinction between raster and vector tools) and to program appearance. One of those changes is uniformalizing controls for document structure, even if the separate products structure their documents differently.

Both Photoshop and Illustrator data models fit the UI model of the suite, at least as far as tree controls etc. go. But that doesn't mean the underlying data models have been changed. They have simply been presented in the UI in a visually similar manner. If you use both Photoshop and Illustrator (as I do), you realize that the widgets are the same, but the control actions are not.

It is a mistake to present dissimilar concepts in a visually similar form. Hence I criticize Adobe's software engineering practice on this point. In interaction design, it leads to the type of error Zebest made. To a certain extent the Ai and Ps UIs behave similarly and offer identical controls. But that extent is not sufficient to establish the underlying data model as equivalent.

My car has two steering wheel stems. They have similar controls and motions. However, noting that each has a set of detents and a similar shape does not mean that the task of operating the windshield wipers has the same underlying semantic as the task of activating the turn signal.

In a more esoteric example, Boeing employs a set of 7-segment displays connected to a knob that changes the displayed value. The BCD or analog representation of that quantity can be accessed on pins from the assembly. If you turn the knob clockwise, the displayed value increases. If you turn it counterclockwise, it decreases. The digital and analog outputs change accordingly. Boeing builds many control panels out of this basic component, such as the "ALT HOLD" setting on the autopilot. That doesn't mean that "ALT HOLD" is the same underlying quantity as the transponder code. Setting ALT HOLD to 7700 has one effect. Setting the transponder to 7700 has a dramatically different effect. Same user interface; different underlying concept.
 
I fail to see what is difficult about this.

Because you understand the underlying concepts. To Robert and the other Birthers it's just "Ermagerd!! Layrrs!!" That is, if something says "layer" then it must mean exactly the same thing as every other case in which the word "layer" is used -- so they say. Adobe doesn't help when they try to cram different semantics into the same UI.

A Photoshop layer is not the same as a PDF object.
A PDF object is not a layer, nor resides in layers.
A Photoshop layer is not the same as an Illustrator layer.
A PDF object is not an Illustrator layer.
An Illustrator object is not an Illustrator layer.
 
Because you understand the underlying concepts. To Robert and the other Birthers it's just "Ermagerd!! Layrrs!!" That is, if something says "layer" then it must mean exactly the same thing as every other case in which the word "layer" is used -- so they say. Adobe doesn't help when they try to cram different semantics into the same UI.

A Photoshop layer is not the same as a PDF object.
A PDF object is not a layer, nor resides in layers.
A Photoshop layer is not the same as an Illustrator layer.
A PDF object is not an Illustrator layer.
An Illustrator object is not an Illustrator layer.

ALl that darn techno babbble you god forsaken eddicated people use....

*Joke Alert*
 
Meanwhile, in Topeka, KS(where I live, btw) the clown show continues:

http://cjonline.com/legislature/2012-09-13/kansas-panel-delays-ballot-decision-obama
Three of the state's top elected Republicans on Thursday determined they lacked sufficient evidence of President Barack Obama's birth records to decide whether to remove the Democratic nominee from the November ballot in Kansas.


Joe Montgomery, who filed the challenge with the all-Republican panel, said Obama should be removed from the Kansas ballot. The president's father was from Kenya and that raised questions about whether Obama was eligible to run for the nation's highest office, he said.


Somebody save me...
 
ALl that darn techno babbble you god forsaken eddicated people use....

*Joke Alert*

I have said it before, and I will no doubt say it again. The OP did not expect subject matter experts to be present in this thread. I can actually see this malarkey fly, if nobody understands the technology. that's a little scary.
 
Status
Not open for further replies.

Back
Top Bottom