On 27 Oct 2008, at 12:54 AM, Justin C. Walker wrote: > > On Oct 26, 2008, at 16:25 , Christiaan Hofman wrote: >> On 26 Oct 2008, at 10:35 PM, Justin C. Walker wrote: >>> >>> On Oct 25, 2008, at 14:24 , Adam M. Goldstein wrote: > [snip] >>> 1) This is probably an Apple issue, but if anyone can provide >>> clarification it will help in the bug report: On 10.5.5, I have >>> BibDesk assigned to one Space. If I have the separate preview >>> window >>> (SHFT-CMD-T) open, and switch Spaces, and then try to switch back to >>> BibDesk (CMD-TAB or the Dock), the preview window shows up in the >>> current Space. Closing that window lets me switch to BibDesk with >>> CMD-TAB/Dock. >>> >>> So: should the preview window stay in BibDesk's assigned Space, and >>> if >>> so, is this under BibDesk's control? > [snip] >> I've often had problems with spaces, even more serious ones like a >> sheet being associated to a space different from the window it's >> attached to. So lots of child diseases. Generally, almost nothing >> about spaces is made public by Apple, so individual apps have >> virtually no control about how this behaves. Certainly, BD does not >> modify any default behavior, in particular the tex preview window has >> the standard behavior (whatever that is). So this sounds like an >> Apple >> bug. > > Thanks; I'll file with Apple. > >>> 2) Next, a preview glitch: I have 537 entries in my .bib file. If I >>> select them all, a preview is generated in the "integrated" preview >>> window, without fuss. >> >> What do you mean by the integrated window? If you're just talking >> about templated text preview, that's completely unrelated, as it has >> absolutely nothing to do with TeX. > > I mean the TeX preview window in the main panel (the lower one, > selected by the sunglasses icon :-}). I assume that has something to > do with TeX because when a (real) TeX error crops up, the yellow > warning triangle shows up there, along with the note that TeX preview > generation failed. > >>> However, if I have the floating preview window >>> open, it shows a TeX error (the integrated window still makes no >>> complaint). >> >>> The TeX log shows no errors (a bunch of TeX warnings >>> about under/overfill, and bibtex warnings about missing fields, but >>> no >>> errors). I tried a binary search to see where the problem might be, >>> but the results were a bit perplexing. >>> >> >> It must be a TeX error, and that's not under BD's control. I guess >> there's some item that breaks TeX. > > Checking as Adam suggested I see no errors reported in the pdflatex/ > bibtex/pdflatex/pdflatex sequence; and the log message shows only > warnings (no "!"s in the TeX part; and no errors in the bibtex part). > Is there another way that something not under BibDesk's control can > sneak in here? How would I isolate that. > >>> If I isolate 463 of the 537 items in a static group, I always get >>> the >>> error. Depending on the selections making up the group, the error >>> goes away after deselecting some small number of items (1, 2, >>> 3, ..). >>> >> >> Confirms that it's probably just a few items incompatible with TeX. > > Not really, but only because my description of the problem lacked a > few details (sorry about that; I edited too many times before > sending). > > Specifically, it seems that the "463 out of 531" number is important. > Again, though I have not done an exhaustive study, it appears that 463 > is the smallest number of entries from this .bib that causes the > problem, and additionally, *none* of the entries which seem to be > critical (as I described in an earlier reply) show this problem. > > To restate, if I just select those entries, in the groups in question, > whose presence seems to be needed to cause the error, I get no error. > > Truly perplexing, at least to me. > > Justin > > -- > Justin C. Walker, Curmudgeon-At-Large > Director > Institute for the Enhancement of the Director's Income > -------- > "Weaseling out of things is what separates us from the animals. > Well, except the weasel." > - Homer J Simpson > -------- >
The only difference between the two is the RTF preview that's generated for the separate window, but not for the preview pane. So it's probably a problem with latex2rtf. Christiaan ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Bibdesk-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bibdesk-users
