On Mar 2, 2005, at 18:18, Maxwell, Adam R wrote:
> On 3/2/05 6:59 AM, "Simon Spiegel" <simon@...> wrote:
>> Hi everybody,
>> I just made a new build of BibDesk with the newest checkins and I'm
>> seeing big problems here: When using the "old" parser BibDesk
>> beachballs when opening my library. Eventually, it will open the file,
>> but it takes forever. With the Unicode parser things work, but they
>> take much longer as they used to. I just checked back with .98.1 and
>> there the speed is ok.
> CVS builds are supposed to be slow and buggy :). Seriously,
> optimizing at
> such an early stage would be dangerous, although Christiaan's idea for
> notifications sounds plausible.
>> There also seems to be a problem with the newest additions when it
>> comes to the character # . I guess this has to do with macro support.
>> had # in some abstracts before without any problems. The newest build
>> of BibDesk seems to strip the opening (but not the closing) bracket
>> from the field containing the #, the result is that BiBDesk writes a
>> file it cannot read.
> What parser are you using when this occurs? I need to figure out what
> to do
> in this case for the Unicode parser; technically, I think you should
> have \#
> everywhere, since # is special to LaTeX. I know, I know... we're not
> supposed to write files we can't read...
It should be a problem for any parser. At the moment the complex string
is buggy for # inside a quoted string, as it always interprets it as a