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
In the beginning (some 20 years ago) the XML files for CrossRef data upload were produced by a series of sed+awk+perl scripts on recipes that got passed around. About 10 years ago Boris Veytsman, placed this under a more solid framework with the script ltx2crossrefxml.pl... But alas it works with bbl produced by bibtex, but not with the ones produced by biber.
A lot of people are building kludges on their workflows by creating dummy tex files that can produce the XML with the help of Boris suite, but this is way less than optimal. Biber would be able to produce much better quality XML files because the bbl contains detailed information about each entry.
It also would help make biblatex more palatable to publishers.
The text was updated successfully, but these errors were encountered:
In the beginning (some 20 years ago) the XML files for CrossRef data upload were produced by a series of sed+awk+perl scripts on recipes that got passed around. About 10 years ago Boris Veytsman, placed this under a more solid framework with the script ltx2crossrefxml.pl... But alas it works with bbl produced by bibtex, but not with the ones produced by biber.
A lot of people are building kludges on their workflows by creating dummy tex files that can produce the XML with the help of Boris suite, but this is way less than optimal. Biber would be able to produce much better quality XML files because the bbl contains detailed information about each entry.
It also would help make biblatex more palatable to publishers.
The text was updated successfully, but these errors were encountered: