On 28 Jan 2008, at 1:36 AM, Adam M. Goldstein wrote: > On Jan 27, 2008, at 7:22 PM, Cloy Tobola wrote: > >> >> 1. I understand the change to the Local File column. When that column >> is set to be very narrow, would it be better to have the number of >> linked files appear [rather than just a paper clip]? After all, the >> paperclip already appears in the column at the top. Just a thought. >> > > But then you'd have to look up at the top of the column to see what > the number was for. There is a links column too, and you'd have to > distinguish it from that. >
I also think it's probably better to clip than to word-wrap, so the number is visible when the "items" does not fit. That's also what mail does on Tiger (if that's changed on Leopard IMHO I think it's a regression). >> 2. I frequently recommend BibDesk to students and fellow scholars. >> However, one of the problems I've run into is that if I get a >> reference with a gremlin in the abstract, it will change the file >> format and require a "save as." > > You mean, the reference has the wrong encoding, or that there are some > non-TeX compatible quotation marks? It seems like you must mean the > former. > > When this happens, I usually hunt down the offending reference and > delete whatever the problem is. A dialogue will come up saying > something like "This file cannot be saved because such-and-such > reference has a problem." > >> that can be confusing. When I first >> started using BibDesk, I lost a bibliography because of the confusion >> this caused. Are there any workarounds or other options when this >> occurs... or settings to avoid this problem? I get it -- but I'm >> hoping for an easy fix that ensures people have a good first >> experience with this application. (I do tell potential users to >> backup their work.) >> > You can choose to "texify" accented characters (i.e. turn them into TeX sequences for saving, which will be reversed on loading). If there are characters we don't handle by default you may add them from the Files preferences. There cannot be any other workaround: when a character cannot be saved in some encoding it simply cannot be saved (without data loss). You'll have to fix it. The only thing we can do it (better?) warnings. Christiaan > > -Adam G. > ================================= > Adam M. Goldstein PhD MSLIS > Assistant Professor of Philosophy > Iona College > -- > email: [EMAIL PROTECTED] > web: http://www.iona.edu/faculty/agoldstein/ > tel: (914) 637-2717 > post: Iona College > Department of Philosophy > 715 North Avenue > New Rochelle, NY 10801 ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Bibdesk-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bibdesk-users
