Thanks – glad you enjoyed them.

RB

RB

A layout suggestion, however: Have you considered using 2 or more columns on each page in future pdf books you publish? I’m not a layout nazi, I swear ^^, but it would make things a lot easier to read.

Anyways, I’m enjoying all else so again, thanks for writing it.

Hey thanks. The aperture manual should really be doing your dirty work here!

It makes complete sense what you’re saying, yes.

Thanks again.

Ben

I detail the circumstances where images are moved, copied, or referenced in the PDF.

Moved being the actual image master and all versions are physically relocated to another project – typically when dragging from a project to a project.

Copied being that you are actually duplicating the master into another project and the two have nothing to do with each other any more. Also dragging from project to project but holding a modifier key.

Referenced being the image showing up in more than one place but no copies are made. This is the most typical case and depends on the drop target. Typically the drop target being some sort of album container.

RB

My library is entirely managed at present.

Ben

There IS an occasion when dragging an image to another project actually MOVES the master and associated files. I was indeed using this deliberately.

I’m wondering – is the behaviour of this a result of the relative “depths” the two projects reside in? Or is it all about Albums, and dragging the contents of these.

My work flow was this:

Create A Blue Folder. Ok fine.

Within this, I then created a number of blank projects. The first called Complete Capture (it was for a wedding). Next to this I created bridal Preparations, Formals etc etc. All within the Blue Folder (enclosing the whole single wedding).

The idea was, once EVERYTHING was in the Complete Capture project, I then selectively moved what was needed to each relevant project. I could then port out individual projects to be worked on by my colleague on another machine. And then port them back for final output blah blah.

So, my question – dropping images from one project to another in this way MOVED them. Why? What is the subtle difference in situation that would make an image not MOVE, but just “appear” without moving the master, as you so eloquently emphasise?

Thanks

Ben

Many thanks.

maybe I was too specific since it´s not only the typography but the whole layout, I like. The title page is very clear, containing all important facts, the pictures have higher resolution than for web and the article is well structured in sections (intro, main part, end notes) and subsections. I think the most important fact for me is, that it´s a real pdf guide, not just a pdf file containing a converted webpage.

Since I finished my masters thesis some weeks ago, using LaTeX exclusively, I´m entirely taken by the quality it produces. So probably I would go LaTeX when writing any article because I get frustrated everytime I have to write something in MS Office or OpenOffice with figures, references etc.

May I ask you, what kind of software did you use for writing the guide? If it´s iWork, maybe I should also give it a try

My only suggestion is to try justified text for such kind of document.

Greetings, Kamil

One other thing – what did you find so great about the typography? I didn’t spend a whole lot of time with the PDF in that respect. Just curious because I do care about that sort of thing but this is not some of my work that I consider so wonderful.

RB