A scientific user feedback

[Curtis Clifton]

On Dec 6, 2004, at 10:55 PM, Timothy J.Wood wrote:

> On Sunday, December 5, 2004, at 08:51  PM, Curtis Clifton wrote:
>> 1. In-line typesetting with ES in OO3 creates a TIFF attachment 
>> instead of a PDF.  Note that this isn't unique to OO3; the same 
>> behavior happens with TextEdit.  However, in-line typesetting and 
>> untypesetting work fine in OmniGraffle.  I'm guessing that ES puts 
>> both a TIFF and a PDF on the pasteboard and lets the application 
>> choose which to use.  OG takes the PDF; OO3 and TextEdit take the 
>> TIFF.  It would be nice if OO3 took the PDF; it would print better, 
>> because it's scalable.
>
>   Fixed for the next release.  This is a bug in Cocoa (or missing 
> feature).  It was reading the PDF, actually, but then turning into 
> TIFF at the last second.  OO3 now overrides the AppKit code to 
> preserve the PDF data all the way to the printer output.
>
>> 2. OO3 treats an ES-generated PDF file (which has type ESPD) as a 
>> movie attachment.  Such an attachment in TextEdit or OmniGraffle is 
>> treated correctly (i.e., not as a movie).  This seems to be a bug in 
>> OO3.
>
>   "Fixed" in the sense that we now special case the (seemingly) bogus 
> type code on the dragged file.  As far as I can see, there is no good 
> reason for this to have a custom type code (we were obeying it -- 
> noticing that it was *not* anything that NSImage said it could read 
> and moving on to QT as a second choice).  We really don't want to do 
> data-sniffing since that is error prone and expensive in some cases; 
> we'd rather trust that the data vendor will give us the correct type 
> if we possibly can.
>
>   Anyway, since this was a two-line fix once I had the PDF stuff above 
> fixed, I figured I'd go ahead and put it in instead of sitting on any 
> elevated equines :)

Awesome!  Thanks, Tim.

-- Curt