Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
As discussed in #148 a biblatex entry of type
@incollectionis recognized as hayagriva typeAnthosof anAnthology.#72 (PR #74) claims that
Anthosis recognized as being a CSL typechapter. However #148 (comment) produced a CSL style for debugging this issue which shows, that@incollectionsources are not recognized aschapters.ashprice@49d88b2 proposes a solution for this problem, however i could not find a final resolution/verdict or a related PR.
Since I am affected by this problem and it appears to persist I want to propose my solution with a slightly more strict matcher than proposed by ashprice@49d88b2.
I hope I did not miss a verdict somewhere else and am open to further opinions on this matter since I am neither an expert in Rust nor in the semantics of citation source types.