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
I want to merge multiple latex projects into one and would like to use bibtex-tidy for merging the bibliographies. However, if entries are merged, only the first entry's key survives the merge and the duplicate keys are lost. It would be very helpful to have the option to output all key replacements to a file or a separate output field in the web app, so that they can be used in a find-replace script to fix the latex sources.
Example: There are two entries with keys riemann1859 and anzahlprim, both having the same title Ueber die Anzahl der Primzahlen unter einer gegebenen Grösse.. If I use the deduplication option by title, both entries will be merged and the key anzahlprim is lost. This means that all latex sources referencing anzahlprim now have an undefined reference. If I had a list of the form
I want to merge multiple latex projects into one and would like to use
bibtex-tidy
for merging the bibliographies. However, if entries are merged, only the first entry's key survives the merge and the duplicate keys are lost. It would be very helpful to have the option to output all key replacements to a file or a separate output field in the web app, so that they can be used in a find-replace script to fix the latex sources.Example: There are two entries with keys
riemann1859
andanzahlprim
, both having the same titleUeber die Anzahl der Primzahlen unter einer gegebenen Grösse.
. If I use the deduplication option by title, both entries will be merged and the keyanzahlprim
is lost. This means that all latex sources referencinganzahlprim
now have an undefined reference. If I had a list of the formI could run an easy script that replaces all references to
anzahlprim
withriemann1859
in the latex sources.Is there already a way to do this? E.g. the CLI could get a flag
--save-key-replacements <file-path>
and the web app a simple output text field.The text was updated successfully, but these errors were encountered: