On 08/21/08 12:34, "James Howison" <[EMAIL PROTECTED]> wrote:
> PLOS is publishing their bibtex in utf8 (as a downloaded .bib file). > Which is fine, if one opens the file with utf8 encoding. However when > I double click it, BibDesk (1.3.18) gives the "Unable to parse string > as BibTeX" error, which suggests editing, but not trying a different > encoding. Try dropping the file on your document's main window, which I should have suggested to JT as well. That will force BibDesk to guess the encoding, and UTF-8 will be tried if the file does not have a Unicode BOM (unless that's changed in the last few months). Double-clicking the file only uses your default encoding. > I just wondered whether bibdesk ought to be able to assess the > encoding of the file (TextMate seems to be able to), or whether this > error message might suggest trying a different encoding? TextMate always tries UTF-8; since a file can't be misinterpreted as UTF-8, this is safe (BibDesk does it as well, in the case I mentioned above). Unfortunately, to try and guess encoding when opening a BibTeX document from the Finder would be problematic with BibDesk's error display, among other things, so it has to be specified by the user. -- Adam ------------------------------------------------------------------------- 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
