We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
This came up in http://tex.stackexchange.com/q/353722/35864
It seems as though overwrite=true has no effect when used in a fieldsource/fieldtarget combination.
overwrite=true
fieldsource
fieldtarget
In the MWE below I would expect both notes to show 'foo', yet in worman the original value 'bar' is not overwritten.
worman
\documentclass{article} \usepackage{filecontents} \usepackage[ backend=biber, style=authoryear-comp, ]{biblatex} \DeclareSourcemap{ \maps[datatype=bibtex]{ \map[overwrite=true]{ \step[fieldsource=keywords, fieldtarget=note] } } } \begin{filecontents}{\jobname.bib} @book{worman, author = {Worman, Nancy}, title = {The Cast of Character}, date = 2002, keyword = {foo}, note = {bar}, } @book{wilde, author = {Wilde, Oscar}, title = {The Importance of Being Earnest}, year = 1899, keywords = {foo}, } \end{filecontents} \addbibresource{\jobname.bib} \begin{document} \nocite{*} \printbibliography \end{document}
The text was updated successfully, but these errors were encountered:
Fix for plk/biblatex#535
67edfc0
This was a bug, now fixed in 2.8 DEV version.
Sorry, something went wrong.
Thank you for the swift reply. It works like a charm with the 2.8 DEV version from sourceforge.
Yes, you need the DEV 2.8 version of biber which needs the DEV 3.8 version of biblatex.
plk
No branches or pull requests
This came up in http://tex.stackexchange.com/q/353722/35864
It seems as though
overwrite=true
has no effect when used in afieldsource
/fieldtarget
combination.In the MWE below I would expect both notes to show 'foo', yet in
worman
the original value 'bar' is not overwritten.The text was updated successfully, but these errors were encountered: