Bug#343433: bibtex2html: attemps to parse comment fields and fails

2005-12-16 Thread Jean-Christophe Filliatre

Dear bibtex2html user,

  On Thu, Dec 15, 2005 at 09:24:51AM +, Robert Hart wrote:
   Package: bibtex2html
   Version: 1.77-1
   Severity: important
   
   Some bibtex editors such as Pybliographer put comment lines like this:
   
   @comment{This file has been generated by Pybliographer}
   
   into .bib files.

The  mistake was  mine.  I  indeed introduced  this  bug recently  (in
version 1.77, while trying to fix some other bug related to unbalanced
braces in comments introduced).

I sincerely apologize for the mess.  I've just built a release 1.78 of
bibtex2html where the parsing of @comment is fixed.

Best regards,
-- 
Jean-Christophe FilliĆ¢tre (http://www.lri.fr/~filliatr)




Bug#343433: bibtex2html: attemps to parse comment fields and fails

2005-12-15 Thread Robert Hart
Package: bibtex2html
Version: 1.77-1
Severity: important


Some bibtex editors such as Pybliographer put comment lines like this:

@comment{This file has been generated by Pybliographer}

into .bib files.

AFAICT bibtex2html treats this as a regular entry, and is looking for a 
comma after @comment{This and fails to find it.

Personally, I think bibtex2html should skip over *any* entry it can't 
understand rather than bailing out with obscure error messages.


-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.14.3
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)

Versions of packages bibtex2html depends on:
ii  ocaml-base-nox [ocaml-base-no 3.09.0-3   Runtime system for ocaml bytecode 
ii  perl  5.8.7-9Larry Wall's Practical Extraction 
ii  tetex-base3.0-11 Basic library files of teTeX
ii  tetex-bin 3.0-11 The teTeX binary files
ii  tetex-extra   3.0-11 Additional library files of teTeX

bibtex2html recommends no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#343433: bibtex2html: attemps to parse comment fields and fails

2005-12-15 Thread Ralf Treinen
On Thu, Dec 15, 2005 at 09:24:51AM +, Robert Hart wrote:
 Package: bibtex2html
 Version: 1.77-1
 Severity: important

This is certainly not of severity important. Set to wishlist.

 Some bibtex editors such as Pybliographer put comment lines like this:
 
 @comment{This file has been generated by Pybliographer}
 
 into .bib files.

If some editors produce bibtex files which does not follow bibtex
syntax then this is rather a bug with these tools. Having said this,
I recognize that @comment are quite common, and that bibtex2html
should probably recognize them properly and skip them.

 Personally, I think bibtex2html should skip over *any* entry it can't 
 understand rather than bailing out with obscure error messages.

I don't think that bibtex2html should try to deal with arbitrarily
broken input.

-Ralf.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#343433: bibtex2html: attemps to parse comment fields and fails

2005-12-15 Thread Robert Hart
On Fri, 2005-12-16 at 00:06 +0100, Ralf Treinen wrote:
 On Thu, Dec 15, 2005 at 09:24:51AM +, Robert Hart wrote:
  Package: bibtex2html
  Version: 1.77-1
  Severity: important
 
 This is certainly not of severity important. Set to wishlist.

I'm not going to haggle, but this bug does have a major effect on the
usability of a package, without rendering it completely unusable to
everyone.

 If some editors produce bibtex files which does not follow bibtex
 syntax then this is rather a bug with these tools. Having said this,
 I recognize that @comment are quite common, and that bibtex2html
 should probably recognize them properly and skip them.

I never realised @comment{} wasn't part of the syntax, but you are
right.

  Personally, I think bibtex2html should skip over *any* entry it can't 
  understand rather than bailing out with obscure error messages.
 
 I don't think that bibtex2html should try to deal with arbitrarily
 broken input.

What about dealing with input that is so broken that bibtex itself
processes it fine without even issuing a warning?

BTW, I'm probably hallucinating, but isn't this bug a regression? I'm
sure I've been using both pybliographer and bibtex2html for some time,
and not had the problem.

Rob
-- 
Robert Hart [EMAIL PROTECTED]
University of Nottingham


This message has been checked for viruses but the contents of an attachment
may still contain software viruses, which could damage your computer system:
you are advised to perform your own checks. Email communications with the
University of Nottingham may be monitored as permitted by UK legislation.



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]