On Jun 27, 2011, at 09:47, Christiaan Hofman wrote: > ...of course, only if you have enabled character (TeX) conversion.
True! Of course, if you're saving in ASCII without that, you might as well edit the BibTeX directly with a text editor :). > Basically, I'd either save in UTF-8, or in ASCII with TeX conversion enabled. > If you save in ASCII without TeX conversion, you're basically telling us to > do strict character checking, which can be useful, and is exactly what you > say you're getting. The tack I've taken is to save in UTF-8 with TeX conversion enabled, which gives broadest compatibility with TeX, but doesn't give me warnings on oddball characters in annote/abstract fields that can't be converted. Of course, I'll have problems in TeX if someone ever uses one of those in a title field, but cleaning annote/abstract is too tedious. YMMV. -- Adam ------------------------------------------------------------------------------ All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 _______________________________________________ Bibdesk-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bibdesk-users
