On Oct 11, 2010, at 14:14, Christiaan Hofman wrote:
>
> On Oct 11, 2010, at 23:04, Maxwell, Adam R wrote:
>
>> Sadly, I think btparse might be wrong to allow this. From bibtex.web:
>>
>> "furthermore, comments may appear anywhere
>> between entries (or before the first or after the last) as long as
>> they contain no |at_sign|s" [1]
>>
>> Since @comment was an afterthought for scribe compatibility, I'm not sure
>> that it's very well defined or supported. Disallowing @ in group names is
>> might be the safest thing to do.
>>
>> I wonder if bibclean or other parsers accept this? The web code is too
>> painful for me to decipher.
>>
>> [1] http://www.tex.ac.uk/tex-archive/biblio/bibtex/distribs/bibtex.web
>>
>
> For such comments (not in @comment entries) it is natural that they can't
> contain "@", as those designate the beginning of an entry.
>
> However I'd say that @comment entries should be treated syntactically by
> bibtex similarly to other entries, except that they're ignored. And the "@"
> sign is allowed in fields, therefore they're also supposed to be allowed in
> @comment entries.
I agree that's what it should do, but I suspect it just ignores the @comment as
a type, and the comment text (including braces) is just treated as usual until
it encounters another @ token. In other words, that comment always applies,
and the {} delimiters only meaningful to btparse and human readers.
------------------------------------------------------------------------------
Beautiful is writing same markup. Internet Explorer 9 supports
standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3.
Spend less time writing and rewriting code and more time creating great
experiences on the web. Be a part of the beta today.
http://p.sf.net/sfu/beautyoftheweb
_______________________________________________
Bibdesk-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bibdesk-users
