Re: [Bibdesk-users] error importing .bib file

[Michael M. <mic...@ma...>]

Unfortunately, I don't think this will happen very soon.

The problem is that we use a parsing library which treats that as an 
error,
and it doesn't return partial entries when there is an error.
We can solve this in a couple of ways, but they are all a good bit of 
work.

If this isn't currently a bug in the bug tracker, it deserves to be one 
so we can keep track of it for later.

If any lex/yacc wiz wants to work on this, we can move the discussion 
to the dev list.

Sorry,
-mike

On May 11, 2005, at 5:08 PM, Alex Montgomery wrote:

> I know this has been discussed before, but might BibDesk's parser be 
> made a little more robust to cite key errors? I occasionally forget 
> citekeys in other apps or when exporting from e.g. EndNote and BibDesk 
> removes the offending citation instead of bumping over it; could it 
> assign it a blank or generic citekey instead?
>
> -A
>
> On May 11, 2005, at 11:37 AM, Maxwell, Adam R wrote:
>
>>
>> On May 10, 2005, at 22:00, Doug Marmion wrote:
>>
>>> Hi,
>>>
>>> I'm just trying to get started using BibDesk and having a couple of 
>>> problems. Firstly, I have a large-ish bibtex file I'm trying to 
>>> import. On doing this I get the 'error reading file' message and 
>>> choose 'Edit file'. This immediately brings up a window listing many 
>>> errors, but they're all shown as being in line 1. Clicking on error 
>>> messages does not move the selection (in the window which shows the 
>>> .bib file contents) from the first reference.
>>>
>>> Also I'm getting errors of the form...
>>>
>>> found "{\o}", expected ","
>>>
>>> This seems to only ever be referring to the contents of cite keys. 
>>> Any suggestions on how to fix this?
>>
>> You're quite right, it is referring to the contents of the cite keys. 
>>  Don't use things like {\o} in cite keys, since those have special 
>> meaning for TeX/BibTeX.  Essentially, a BibTeX citekey is a TeX 
>> command, and is theoretically subject to the same restrictions; 
>> practically, citekeys are less restrictive.  Do not use one of these 
>> " '\"@,\\#}{~%" in your keys (this list includes whitespace such as 
>> tab/space).
>>
>>
>> Also, your file isn't UTF-8, it's MacOSRoman (did it come from 
>> Endnote, by chance?).
>>
>> hth,
>> Adam
>>
>>
>> -------------------------------------------------------
>> This SF.Net email is sponsored by Oracle Space Sweepstakes
>> Want to be the first software developer in space?
>> Enter now for the Oracle Space Sweepstakes!
>> http://ads.osdn.com/?ad_id=7393&alloc_id=16281&op=click
>> _______________________________________________
>> Bibdesk-users mailing list
>> Bib...@li...
>> https://lists.sourceforge.net/lists/listinfo/bibdesk-users
>>
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by Oracle Space Sweepstakes
> Want to be the first software developer in space?
> Enter now for the Oracle Space Sweepstakes!
> http://ads.osdn.com/?ad_id=7393&alloc_id=16281&op=click
> _______________________________________________
> Bibdesk-users mailing list
> Bib...@li...
> https://lists.sourceforge.net/lists/listinfo/bibdesk-users
>