I’ll deal with the last bit first
On 24 Oct 2008, at 01:16, IanB wrote:
By the way, Copy and Paste to the Save dialogue box works here, both from Intaglio and the Finder.
O.K. Thanks. It’s good to know the thing is local.
On Paste I get an alert box which says
Can’t complete this command
On copy I get no response and nothing goes into the clipboard.
Ditto on cut.
This is rather strange since I would suspect that Intaglio 3.0.1 is programmed using Cocoa, XCode and Interface Builder and therefore will call up the standard Save panel NSSavePanel which I believe to be the component used in all cocoa based saves all of which appear to provide a copy and paste facility as default.
For instance if I run XCode and create a new document based application this creates all the save etc facilities for me as default. If I now, without doing anything further, run this skeleton program, I am able to bring up the save panel and copy and paste into it just like that.
It is possible though I don’t know enough about it that 3.0.1 is written in Carbon and I believe OS 10.5 leopard has or is withdrawing support for Carbon because of it representing the start of apple’s move with Intel to 64 bit computing (the length of each machine code instruction which previously was either 16 bit or 32 and even 48 bit)
My references to these Mac programming software and tools are technical but save me writing lots of words.
But as I know to my cost, it having taken me about a year’s hard slog to get up to modest speed with Cocoa programming
Cocoa is hard to get to know and so full of pitfalls that the cocoa mailing list goes out about 4 or 5 times a day with about ten or more messages each time. But all of the above is just guesswork.
That’s intriguing stuff, Julius, but your comments pose yet more questions!
As I’m not a programmer, the Wikipedia pages are tough going. ‘PDF…is a sub-set of the Postscript page description language…’; ‘The graphics commands that are output by the PostScript code are collected and tokenized;…’ It’s all very mysterious.
Ok. sorry to point you at technical speak and using it myself in my previous comments.
I’ll try to clarify as briefly as I can.
When a program sends a page to the printer for printing it first encodes it into a set of numbers which instruct the printer as to where to print black, or a colour and where not. That encoding is performed using a set of machine interpretable conventions that are referred to as a language, in this case a “page description language”. Some of these conventions aka languages are Postscript, EDS and PDF.
One feature of computer languages is that in the decoding process, statements in those languages tend to be translated into statements in other, simpler languages. More or less like when as I am doing now, I try to translate the computereese of the wiki page into something more human readable for this list. During this translation process the various grammatical units of the statements become replaced by other units sometimes refered to as tokes.
Now hopefully to convert the wiki sentence into english:
Often, the PostScript-like PDF code is generated from a source PostScript file. The graphics commands that are output by the PostScript code are collected and tokenized; any files, graphics, or fonts to which the document refers also are collected; then, everything is compressed to a single file. Therefore, the entire PostScript world (fonts, layout, measurements) remains intact.
PostScript-like PDF code = the statements written in the PDF language
generated from a source PostScript file = the input file written in Postscript
The graphics commands = the computer instructions used to generate a picture (on screen) or instruct a printer
are collected and tokenized = are translated into the common set of conventions being used but without loss of information, ie. one can in this instance translate both ways, reproducing the original in each case.
everything is compressed to a single file = compressed is just that, e.g. jpeg is a compressed graphic, .zip is a compressed text or binary file.
Therefore, the entire PostScript world (fonts, layout, measurements) remains intact. = the file still contains all the information contained in the original Postscript file.
In summary: A PDF file is an amalgam of data obtained from various sources including a Postcript file whose contents are included without loss of information, i.e. we can generate the original Postscript file from the PDF file.
Sorry. Can’t go on. This will have to do. Just hope it could be understood.
In future I’ll try to use standard English in my comments.