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
It is common in some bibtex entry types to use a "type" field (well actually I don't know… but it's listed as a possible biblatex type in the documentation so it's reasonable to use it, even if I don't know what is the recommended usage). When parsing a document with such fields, the entry type is overwritten. Is it a desired behavior? Wouldn't it be better to export the entry type to a specific key to prevent that, or at least to have some optional parameter to specify this?
Here is an example:
julia> BibTeX.parse_bibtex("@mytype{mycoolpaper, note={Submitted to AwesomeConference} }")
("", Dict("mycoolpaper"=>Dict("note"=>"Submitted to AwesomeConference", "type"=>"mytype")))
julia> BibTeX.parse_bibtex("@mytype{mycoolpaper, type={Submitted to AwesomeConference} }")
("", Dict("mycoolpaper"=>Dict("type"=>"Submitted to AwesomeConference")))
The text was updated successfully, but these errors were encountered:
It is common in some bibtex entry types to use a "type" field (well actually I don't know… but it's listed as a possible biblatex type in the documentation so it's reasonable to use it, even if I don't know what is the recommended usage). When parsing a document with such fields, the entry type is overwritten. Is it a desired behavior? Wouldn't it be better to export the entry type to a specific key to prevent that, or at least to have some optional parameter to specify this?
Here is an example:
The text was updated successfully, but these errors were encountered: