You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First of all, this is very likely not a direct issue of the biblatex crate itself, but, nevertheless, might be of interest for some users.
I'm working on an own little Rust project writing a TUI for fast and easy interaction with someones BibLaTeX database and use this great crate for parsing the input files. While testing it, a friend encountered a little problem with @Strings.
If the @String is defined in the .bib file itself, the crate can parse the entry without any errors. But there are some BibLaTeX styles which offer predefined set of @Strings in their .bst files.
Using a .bib file containing those abbreviations defined in the style file without (re)defining them in the .bib file itself leads to a panic and aborts the program:
➜ release git:(main) ./bibiman ~/@mycene/00-09_system/01_emacs/01.02_bib/auf-dem-forum-thesis.bib
thread 'main' panicked at src/backend/bib.rs:40:74:
called `Result::unwrap()` on an `Err` value: ParseError { span: 1780..1785, kind: UnknownAbbreviation("AEspA") }
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
In this case the BibLaTeX style archaeologie was used which defines a large set of @Strings.
This is very unlikely to be solved by the biblatex crate itself, since it definitely cannot source/parse all BibLaTeX style files. But it might be worth knowing for someone who wants to use the crate or Typst with a specific .bib file containing those @Strings
The text was updated successfully, but these errors were encountered:
lukeflo
changed the title
Not possible to resolve @String which are defined in style file
Not possible to resolve @String which is defined in style file
Oct 13, 2024
First of all, this is very likely not a direct issue of the
biblatex
crate itself, but, nevertheless, might be of interest for some users.I'm working on an own little Rust project writing a TUI for fast and easy interaction with someones BibLaTeX database and use this great crate for parsing the input files. While testing it, a friend encountered a little problem with
@String
s.If the
@String
is defined in the.bib
file itself, the crate can parse the entry without any errors. But there are some BibLaTeX styles which offer predefined set of@String
s in their.bst
files.Using a
.bib
file containing those abbreviations defined in the style file without (re)defining them in the.bib
file itself leads to a panic and aborts the program:In this case the BibLaTeX style
archaeologie
was used which defines a large set of@String
s.This is very unlikely to be solved by the
biblatex
crate itself, since it definitely cannot source/parse all BibLaTeX style files. But it might be worth knowing for someone who wants to use the crate or Typst with a specific.bib
file containing those@String
sThe text was updated successfully, but these errors were encountered: