Closed thelunararmy closed 5 years ago
Should be noted that the error in question comes from trying to parse bibtex records such as this:
@article{citekey,
...
author={Garc{\'\i}a-Molina, H{\'e}ctor},
...
}
This was taken from Google Scholar and fails (like many others) with a syntax error because {\'\i}
is "not a valid escape sequence".
@thelunararmy I've been wanting to do something like that for a while now, including cutting down on other unnecessary log messages. It's a pretty breaking change, but I guess I can put it behind an input option for now. See #130.
@EternalDeiwos That definitely seems like syntax that should be supported, and either way, I agree "not a valid escape sequence" should be more like "unknown escape sequence".
BTW: I am planning to do these things in a week or two.
@larsgw Thanks. Looking forward to it.
Some deadlines are getting in the way, about one more week I think.
@larsgw No problem, thank you for the feedback! Much appreciated.
Hi there,
Would it be possible to have the
Cite.add
function throw the error forward when encountering a Syntax error, rather than printing the error and then fail quietly?Would be really nice to allow the the front end to report the entire faulty entry as opposed to just displaying the syntax error without content.
i.e.
Currently this catch never triggers.