In article <[EMAIL PROTECTED]>, [EMAIL PROTECTED] wrote: > I raised this issue several months ago, but don't think I made myself clear. > > A problem I've run into is that if I import a reference with > non-plain-text (Unicode?) character (an en-dash, an em-dash, an open or > closed quote) in the abstract, it will require a "save as" in a different > file format with a different file name. This occurs when using the default > Western ASCII file format. > > I frequently recommend BibDesk to students and fellow scholars. However, I > am loath to do so with anyone but the most technical -- this is a serious > frustration for the average user, who will be confused by the issue.
Would it reduce the confusion to just save as UTF-8 by default? As long as TeX conversion is enabled, that should (usually) be fine for TeX users who work with ASCII exclusively. I save my files as UTF-8 just to avoid this problem, since the odd characters are almost exclusively in abstracts which never get printed in TeX anyway. -- adam ------------------------------------------------------------------------- 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
