2007-08-14 16:50:51 +00:00
|
|
|
// -*- C++ -*-
|
|
|
|
/**
|
2007-08-20 17:04:36 +00:00
|
|
|
* \file BiblioInfo.h
|
2007-08-14 16:50:51 +00:00
|
|
|
* This file is part of LyX, the document processor.
|
|
|
|
* Licence details can be found in the file COPYING.
|
|
|
|
*
|
|
|
|
* \author Angus Leeming
|
2008-11-14 15:58:50 +00:00
|
|
|
* \author Herbert Voß
|
2007-08-20 16:30:02 +00:00
|
|
|
* \author Richard Heck
|
2013-01-07 14:51:19 +00:00
|
|
|
* \author Julien Rioux
|
2007-08-14 16:50:51 +00:00
|
|
|
*
|
|
|
|
* Full author contact details are available in file CREDITS.
|
|
|
|
*/
|
|
|
|
|
2008-04-20 15:00:11 +00:00
|
|
|
#ifndef BIBLIOINFO_H
|
|
|
|
#define BIBLIOINFO_H
|
2007-08-14 16:50:51 +00:00
|
|
|
|
2007-08-20 16:30:02 +00:00
|
|
|
#include "support/docstring.h"
|
2007-08-14 16:50:51 +00:00
|
|
|
|
2017-01-03 12:11:11 +00:00
|
|
|
#include "BufferParams.h"
|
2008-04-20 15:00:11 +00:00
|
|
|
#include "Citation.h"
|
|
|
|
|
2007-08-20 16:30:02 +00:00
|
|
|
#include <map>
|
|
|
|
#include <set>
|
2014-05-23 14:59:12 +00:00
|
|
|
#include <vector>
|
2007-08-20 16:30:02 +00:00
|
|
|
|
2007-08-14 16:50:51 +00:00
|
|
|
|
|
|
|
namespace lyx {
|
2011-12-03 22:15:11 +00:00
|
|
|
|
2007-08-20 16:30:02 +00:00
|
|
|
class Buffer;
|
2007-08-14 16:50:51 +00:00
|
|
|
|
2008-04-20 15:00:11 +00:00
|
|
|
/// \param latex_str a LaTeX command, "cite", "Citep*", etc
|
2017-01-03 12:11:11 +00:00
|
|
|
CitationStyle citationStyleFromString(std::string const & latex_str,
|
|
|
|
BufferParams const &);
|
2008-11-19 03:58:20 +00:00
|
|
|
/// the other way round
|
2017-01-03 12:11:11 +00:00
|
|
|
std::string citationStyleToString(CitationStyle const &, bool const latex = false);
|
2007-08-14 16:50:51 +00:00
|
|
|
|
|
|
|
|
2007-08-20 16:30:02 +00:00
|
|
|
/// Class to represent information about a BibTeX or
|
|
|
|
/// bibliography entry.
|
2008-11-19 04:16:12 +00:00
|
|
|
/// This class basically wraps a std::map, and many of its
|
|
|
|
/// methods simply delegate to the corresponding methods of
|
|
|
|
/// std::map.
|
2008-02-14 05:00:54 +00:00
|
|
|
class BibTeXInfo {
|
2007-08-20 16:30:02 +00:00
|
|
|
public:
|
2011-12-03 22:15:11 +00:00
|
|
|
/// The keys are BibTeX fields (e.g., author, title, etc),
|
2008-11-19 03:58:20 +00:00
|
|
|
/// and the values are the associated field values.
|
2008-02-14 05:00:54 +00:00
|
|
|
typedef std::map<docstring, docstring>::const_iterator const_iterator;
|
2008-04-25 20:03:03 +00:00
|
|
|
///
|
Improve info display for biblatex databases, part II
In addition to the classic crossref, biblatex introduces xdata
references in order to source-out common data of entries. Entries
that have "xdata = {somekey}" just inherit all fields from the
respective @xdata entry, if the field is not already defined in
the entry itself (just like crossref, with the exception that @xdata
entries themselves are _never_ output on their own). @xdata entries can
themselves inherit to other @xdata entries (ad infinitum). So you can,
for instance, setup an xdata entry for a book series with series name
that inherits an xdata entry with information of the publisher
(publisher, address). Any book of that series would just need to refer
to the series xdata and add the number.
BiblioInfo now checks, in addition to crossrefs, for such xdata
references and inherits missing fields.
Nte that biblatex also introduces an "xref" field as an alternative to
crossref. We must not care about that, since the point of xref is that
it does not inherit fields from the target (just cites that one if a
given number of refs to it exist)
2016-09-18 10:44:12 +00:00
|
|
|
typedef std::vector<BibTeXInfo const *> const BibTeXInfoList;
|
|
|
|
///
|
2013-05-13 18:26:46 +00:00
|
|
|
BibTeXInfo() : is_bibtex_(true), modifier_(0) {}
|
2008-02-14 05:00:54 +00:00
|
|
|
/// argument sets isBibTeX_, so should be false only if it's coming
|
|
|
|
/// from a bibliography environment
|
2013-05-13 18:26:46 +00:00
|
|
|
BibTeXInfo(bool ib) : is_bibtex_(ib), modifier_(0) {}
|
2008-02-14 05:00:54 +00:00
|
|
|
/// constructor that sets the entryType
|
|
|
|
BibTeXInfo(docstring const & key, docstring const & type);
|
2017-01-07 16:32:45 +00:00
|
|
|
/// \return the an authorlist (short form by default),
|
|
|
|
/// used for sorting.
|
|
|
|
/// This will be translated to the UI language if buf is null
|
2016-07-18 02:50:17 +00:00
|
|
|
/// otherwise, it will be translated to the buffer language.
|
2017-01-07 16:32:45 +00:00
|
|
|
docstring const getAuthorList(Buffer const * buf = 0, bool full = false,
|
|
|
|
bool forceshort = false) const;
|
2011-12-03 22:15:11 +00:00
|
|
|
///
|
2007-08-20 16:30:02 +00:00
|
|
|
docstring const getYear() const;
|
2008-11-19 03:58:20 +00:00
|
|
|
/// \return formatted BibTeX data suitable for framing.
|
Improve info display for biblatex databases, part II
In addition to the classic crossref, biblatex introduces xdata
references in order to source-out common data of entries. Entries
that have "xdata = {somekey}" just inherit all fields from the
respective @xdata entry, if the field is not already defined in
the entry itself (just like crossref, with the exception that @xdata
entries themselves are _never_ output on their own). @xdata entries can
themselves inherit to other @xdata entries (ad infinitum). So you can,
for instance, setup an xdata entry for a book series with series name
that inherits an xdata entry with information of the publisher
(publisher, address). Any book of that series would just need to refer
to the series xdata and add the number.
BiblioInfo now checks, in addition to crossrefs, for such xdata
references and inherits missing fields.
Nte that biblatex also introduces an "xref" field as an alternative to
crossref. We must not care about that, since the point of xref is that
it does not inherit fields from the target (just cites that one if a
given number of refs to it exist)
2016-09-18 10:44:12 +00:00
|
|
|
/// \param vector of pointers to crossref/xdata information
|
|
|
|
docstring const & getInfo(BibTeXInfoList const xrefs,
|
2017-01-07 16:12:08 +00:00
|
|
|
Buffer const & buf, CiteItem const & ci) const;
|
2012-03-01 00:41:30 +00:00
|
|
|
/// \return formatted BibTeX data for a citation label
|
Improve info display for biblatex databases, part II
In addition to the classic crossref, biblatex introduces xdata
references in order to source-out common data of entries. Entries
that have "xdata = {somekey}" just inherit all fields from the
respective @xdata entry, if the field is not already defined in
the entry itself (just like crossref, with the exception that @xdata
entries themselves are _never_ output on their own). @xdata entries can
themselves inherit to other @xdata entries (ad infinitum). So you can,
for instance, setup an xdata entry for a book series with series name
that inherits an xdata entry with information of the publisher
(publisher, address). Any book of that series would just need to refer
to the series xdata and add the number.
BiblioInfo now checks, in addition to crossrefs, for such xdata
references and inherits missing fields.
Nte that biblatex also introduces an "xref" field as an alternative to
crossref. We must not care about that, since the point of xref is that
it does not inherit fields from the target (just cites that one if a
given number of refs to it exist)
2016-09-18 10:44:12 +00:00
|
|
|
docstring const getLabel(BibTeXInfoList const xrefs,
|
2017-01-07 16:12:08 +00:00
|
|
|
Buffer const & buf, docstring const & format,
|
|
|
|
CiteItem const & ci, bool next = false, bool second = false) const;
|
2008-02-14 05:00:54 +00:00
|
|
|
///
|
|
|
|
const_iterator find(docstring const & f) const { return bimap_.find(f); }
|
|
|
|
///
|
|
|
|
const_iterator end() const { return bimap_.end(); }
|
2008-11-19 04:16:12 +00:00
|
|
|
/// \return value for field f
|
|
|
|
/// note that this will create an empty field if it does not exist
|
2011-12-03 22:15:11 +00:00
|
|
|
docstring & operator[](docstring const & f)
|
2008-02-14 05:00:54 +00:00
|
|
|
{ return bimap_[f]; }
|
2008-11-19 04:16:12 +00:00
|
|
|
/// \return value for field f
|
|
|
|
/// this one, since it is const, will simply return docstring() if
|
|
|
|
/// we don't have the field and will NOT create an empty field
|
|
|
|
docstring const & operator[](docstring const & field) const;
|
|
|
|
///
|
|
|
|
docstring const & operator[](std::string const & field) const;
|
2008-02-14 05:00:54 +00:00
|
|
|
///
|
2008-02-14 17:00:40 +00:00
|
|
|
docstring const & allData() const { return all_data_; }
|
2008-02-14 05:00:54 +00:00
|
|
|
///
|
2008-02-14 17:00:40 +00:00
|
|
|
void setAllData(docstring const & d) { all_data_ = d; }
|
2008-02-14 05:00:54 +00:00
|
|
|
///
|
2009-06-11 20:29:37 +00:00
|
|
|
void label(docstring const & d) { label_= d; }
|
|
|
|
///
|
2012-03-01 00:41:30 +00:00
|
|
|
void key(docstring const & d) { bib_key_= d; }
|
|
|
|
///
|
2009-06-11 20:29:37 +00:00
|
|
|
docstring const & label() const { return label_; }
|
|
|
|
///
|
|
|
|
docstring const & key() const { return bib_key_; }
|
2010-01-11 16:11:55 +00:00
|
|
|
/// numerical key for citing this entry. currently used only
|
|
|
|
/// by XHTML output routines.
|
|
|
|
docstring citeNumber() const { return cite_number_; }
|
2009-06-11 20:29:37 +00:00
|
|
|
///
|
2010-01-11 16:11:55 +00:00
|
|
|
void setCiteNumber(docstring const & num) { cite_number_ = num; }
|
2011-12-03 22:15:11 +00:00
|
|
|
/// a,b,c, etc, for author-year. currently used only by XHTML
|
2010-01-11 16:11:55 +00:00
|
|
|
/// output routines.
|
|
|
|
char modifier() const { return modifier_; }
|
2010-01-08 18:19:13 +00:00
|
|
|
///
|
2010-01-11 16:11:55 +00:00
|
|
|
void setModifier(char c) { modifier_ = c; }
|
2010-01-08 18:19:13 +00:00
|
|
|
///
|
2008-02-14 17:00:40 +00:00
|
|
|
docstring entryType() const { return entry_type_; }
|
2011-12-03 22:15:11 +00:00
|
|
|
///
|
2009-12-03 19:54:12 +00:00
|
|
|
bool isBibTeX() const { return is_bibtex_; }
|
2008-02-14 05:00:54 +00:00
|
|
|
private:
|
2009-04-09 12:55:47 +00:00
|
|
|
/// like operator[], except, if the field is empty, it will attempt
|
Improve info display for biblatex databases, part II
In addition to the classic crossref, biblatex introduces xdata
references in order to source-out common data of entries. Entries
that have "xdata = {somekey}" just inherit all fields from the
respective @xdata entry, if the field is not already defined in
the entry itself (just like crossref, with the exception that @xdata
entries themselves are _never_ output on their own). @xdata entries can
themselves inherit to other @xdata entries (ad infinitum). So you can,
for instance, setup an xdata entry for a book series with series name
that inherits an xdata entry with information of the publisher
(publisher, address). Any book of that series would just need to refer
to the series xdata and add the number.
BiblioInfo now checks, in addition to crossrefs, for such xdata
references and inherits missing fields.
Nte that biblatex also introduces an "xref" field as an alternative to
crossref. We must not care about that, since the point of xref is that
it does not inherit fields from the target (just cites that one if a
given number of refs to it exist)
2016-09-18 10:44:12 +00:00
|
|
|
/// to get the data from xref BibTeXInfo objects, which would normally
|
|
|
|
/// be the one referenced in the crossref or xdata field.
|
2013-01-14 14:25:26 +00:00
|
|
|
docstring getValueForKey(std::string const & key, Buffer const & buf,
|
2017-01-07 16:12:08 +00:00
|
|
|
CiteItem const & ci, BibTeXInfoList const xrefs, size_t maxsize = 4096) const;
|
2010-03-27 12:58:26 +00:00
|
|
|
/// replace %keys% in a format string with their values
|
|
|
|
/// called from getInfo()
|
|
|
|
/// format strings may contain:
|
|
|
|
/// %key%, which represents a key
|
|
|
|
/// {%key%[[format]]}, which prints format if key is non-empty
|
|
|
|
/// the latter may optionally contain an `else' clause as well:
|
|
|
|
/// {%key%[[if format]][[else format]]}
|
2013-01-08 14:35:50 +00:00
|
|
|
/// Material intended only for rich text (HTML) output should be
|
|
|
|
/// wrapped in "{!" and "!}". These markers are to be postprocessed
|
|
|
|
/// by processRichtext(); this step is left as a separate routine since
|
|
|
|
/// expandFormat() is recursive while postprocessing should be done
|
|
|
|
/// only once on the final string (just like convertLaTeXCommands).
|
2010-03-29 20:21:30 +00:00
|
|
|
/// a simple macro facility is also available. keys that look like
|
|
|
|
/// "%!key%" are substituted with their definition.
|
|
|
|
/// moreover, keys that look like "%_key%" are treated as translatable
|
|
|
|
/// so that things like "pp." and "vol." can be translated.
|
2013-07-20 14:05:52 +00:00
|
|
|
docstring expandFormat(docstring const & fmt,
|
Improve info display for biblatex databases, part II
In addition to the classic crossref, biblatex introduces xdata
references in order to source-out common data of entries. Entries
that have "xdata = {somekey}" just inherit all fields from the
respective @xdata entry, if the field is not already defined in
the entry itself (just like crossref, with the exception that @xdata
entries themselves are _never_ output on their own). @xdata entries can
themselves inherit to other @xdata entries (ad infinitum). So you can,
for instance, setup an xdata entry for a book series with series name
that inherits an xdata entry with information of the publisher
(publisher, address). Any book of that series would just need to refer
to the series xdata and add the number.
BiblioInfo now checks, in addition to crossrefs, for such xdata
references and inherits missing fields.
Nte that biblatex also introduces an "xref" field as an alternative to
crossref. We must not care about that, since the point of xref is that
it does not inherit fields from the target (just cites that one if a
given number of refs to it exist)
2016-09-18 10:44:12 +00:00
|
|
|
BibTeXInfoList const xrefs, int & counter,
|
2017-01-07 16:12:08 +00:00
|
|
|
Buffer const & buf, CiteItem const & ci,
|
|
|
|
bool next = false, bool second = false) const;
|
2008-02-14 05:14:22 +00:00
|
|
|
/// true if from BibTeX; false if from bibliography environment
|
2008-02-14 17:00:40 +00:00
|
|
|
bool is_bibtex_;
|
2007-08-20 16:30:02 +00:00
|
|
|
/// the BibTeX key for this entry
|
2008-02-14 17:00:40 +00:00
|
|
|
docstring bib_key_;
|
2009-06-11 20:29:37 +00:00
|
|
|
/// the label that will appear in citations
|
|
|
|
/// this is easily set from bibliography environments, but has
|
|
|
|
/// to be calculated for entries we get from BibTeX
|
|
|
|
docstring label_;
|
2007-08-20 16:30:02 +00:00
|
|
|
/// a single string containing all BibTeX data associated with this key
|
2008-02-14 17:00:40 +00:00
|
|
|
docstring all_data_;
|
2007-08-20 16:30:02 +00:00
|
|
|
/// the BibTeX entry type (article, book, incollection, ...)
|
2008-02-14 17:00:40 +00:00
|
|
|
docstring entry_type_;
|
2009-01-16 23:40:37 +00:00
|
|
|
/// a cache for getInfo()
|
|
|
|
mutable docstring info_;
|
2013-01-08 15:20:52 +00:00
|
|
|
/// a cache for getInfo(richtext = true)
|
|
|
|
mutable docstring info_richtext_;
|
2011-12-03 22:15:11 +00:00
|
|
|
///
|
2010-01-11 16:11:55 +00:00
|
|
|
docstring cite_number_;
|
|
|
|
///
|
|
|
|
char modifier_;
|
2008-02-14 05:00:54 +00:00
|
|
|
/// our map: <field, value>
|
|
|
|
std::map <docstring, docstring> bimap_;
|
2007-08-20 16:30:02 +00:00
|
|
|
};
|
|
|
|
|
|
|
|
|
|
|
|
/// Class to represent a collection of bibliographical data, whether
|
|
|
|
/// from BibTeX or from bibliography environments.
|
2008-02-14 05:14:22 +00:00
|
|
|
class BiblioInfo {
|
2007-08-20 16:30:02 +00:00
|
|
|
public:
|
Improve info display for biblatex databases, part II
In addition to the classic crossref, biblatex introduces xdata
references in order to source-out common data of entries. Entries
that have "xdata = {somekey}" just inherit all fields from the
respective @xdata entry, if the field is not already defined in
the entry itself (just like crossref, with the exception that @xdata
entries themselves are _never_ output on their own). @xdata entries can
themselves inherit to other @xdata entries (ad infinitum). So you can,
for instance, setup an xdata entry for a book series with series name
that inherits an xdata entry with information of the publisher
(publisher, address). Any book of that series would just need to refer
to the series xdata and add the number.
BiblioInfo now checks, in addition to crossrefs, for such xdata
references and inherits missing fields.
Nte that biblatex also introduces an "xref" field as an alternative to
crossref. We must not care about that, since the point of xref is that
it does not inherit fields from the target (just cites that one if a
given number of refs to it exist)
2016-09-18 10:44:12 +00:00
|
|
|
///
|
|
|
|
typedef std::vector<BibTeXInfo const *> BibTeXInfoList;
|
2008-11-19 03:52:22 +00:00
|
|
|
/// bibliography key --> data for that key
|
2008-02-14 05:14:22 +00:00
|
|
|
typedef std::map<docstring, BibTeXInfo>::const_iterator const_iterator;
|
Improve info display for biblatex databases, part II
In addition to the classic crossref, biblatex introduces xdata
references in order to source-out common data of entries. Entries
that have "xdata = {somekey}" just inherit all fields from the
respective @xdata entry, if the field is not already defined in
the entry itself (just like crossref, with the exception that @xdata
entries themselves are _never_ output on their own). @xdata entries can
themselves inherit to other @xdata entries (ad infinitum). So you can,
for instance, setup an xdata entry for a book series with series name
that inherits an xdata entry with information of the publisher
(publisher, address). Any book of that series would just need to refer
to the series xdata and add the number.
BiblioInfo now checks, in addition to crossrefs, for such xdata
references and inherits missing fields.
Nte that biblatex also introduces an "xref" field as an alternative to
crossref. We must not care about that, since the point of xref is that
it does not inherit fields from the target (just cites that one if a
given number of refs to it exist)
2016-09-18 10:44:12 +00:00
|
|
|
/// Get a vector with all external data (crossref, xdata)
|
|
|
|
std::vector<docstring> const getXRefs(BibTeXInfo const & data,
|
|
|
|
bool const nested = false) const;
|
2008-11-19 03:58:20 +00:00
|
|
|
/// \return a sorted vector of bibliography keys
|
2007-08-20 16:30:02 +00:00
|
|
|
std::vector<docstring> const getKeys() const;
|
2008-11-19 03:58:20 +00:00
|
|
|
/// \return a sorted vector of present BibTeX fields
|
2007-08-20 16:30:02 +00:00
|
|
|
std::vector<docstring> const getFields() const;
|
2008-11-19 03:58:20 +00:00
|
|
|
/// \return a sorted vector of BibTeX entry types in use
|
2007-08-20 16:30:02 +00:00
|
|
|
std::vector<docstring> const getEntries() const;
|
2017-01-07 16:32:45 +00:00
|
|
|
/// \return authorlist (abbreviated form by default)
|
|
|
|
docstring const getAuthorList(docstring const & key, Buffer const & buf) const;
|
2010-01-11 16:11:55 +00:00
|
|
|
/// \return the year from the bibtex data record for \param key
|
|
|
|
/// if \param use_modifier is true, then we will also append any
|
|
|
|
/// modifier for this entry (e.g., 1998b).
|
Improve info display for biblatex databases, part II
In addition to the classic crossref, biblatex introduces xdata
references in order to source-out common data of entries. Entries
that have "xdata = {somekey}" just inherit all fields from the
respective @xdata entry, if the field is not already defined in
the entry itself (just like crossref, with the exception that @xdata
entries themselves are _never_ output on their own). @xdata entries can
themselves inherit to other @xdata entries (ad infinitum). So you can,
for instance, setup an xdata entry for a book series with series name
that inherits an xdata entry with information of the publisher
(publisher, address). Any book of that series would just need to refer
to the series xdata and add the number.
BiblioInfo now checks, in addition to crossrefs, for such xdata
references and inherits missing fields.
Nte that biblatex also introduces an "xref" field as an alternative to
crossref. We must not care about that, since the point of xref is that
it does not inherit fields from the target (just cites that one if a
given number of refs to it exist)
2016-09-18 10:44:12 +00:00
|
|
|
/// If no legacy year field is present, check for date (common in
|
|
|
|
/// biblatex) and extract the year from there.
|
|
|
|
/// Note further that this will get the year from the crossref or xdata
|
|
|
|
/// if it's not present in the record itself.
|
2010-01-11 16:11:55 +00:00
|
|
|
docstring const getYear(docstring const & key,
|
2013-01-14 14:25:26 +00:00
|
|
|
bool use_modifier = false) const;
|
|
|
|
/// \return the year from the bibtex data record for \param key
|
|
|
|
/// if \param use_modifier is true, then we will also append any
|
|
|
|
/// modifier for this entry (e.g., 1998b).
|
Improve info display for biblatex databases, part II
In addition to the classic crossref, biblatex introduces xdata
references in order to source-out common data of entries. Entries
that have "xdata = {somekey}" just inherit all fields from the
respective @xdata entry, if the field is not already defined in
the entry itself (just like crossref, with the exception that @xdata
entries themselves are _never_ output on their own). @xdata entries can
themselves inherit to other @xdata entries (ad infinitum). So you can,
for instance, setup an xdata entry for a book series with series name
that inherits an xdata entry with information of the publisher
(publisher, address). Any book of that series would just need to refer
to the series xdata and add the number.
BiblioInfo now checks, in addition to crossrefs, for such xdata
references and inherits missing fields.
Nte that biblatex also introduces an "xref" field as an alternative to
crossref. We must not care about that, since the point of xref is that
it does not inherit fields from the target (just cites that one if a
given number of refs to it exist)
2016-09-18 10:44:12 +00:00
|
|
|
/// If no legacy year field is present, check for date (common in
|
|
|
|
/// biblatex) and extract the year from there.
|
|
|
|
/// Note further that this will get the year from the crossref or xdata
|
|
|
|
/// if it's not present in the record itself.
|
2013-01-14 14:25:26 +00:00
|
|
|
/// If no year is found, \return "No year" translated to the buffer
|
|
|
|
/// language.
|
|
|
|
docstring const getYear(docstring const & key, Buffer const & buf,
|
|
|
|
bool use_modifier = false) const;
|
2010-01-11 16:11:55 +00:00
|
|
|
///
|
|
|
|
docstring const getCiteNumber(docstring const & key) const;
|
2008-11-19 03:58:20 +00:00
|
|
|
/// \return formatted BibTeX data associated with a given key.
|
2011-12-03 22:15:11 +00:00
|
|
|
/// Empty if no info exists.
|
Improve info display for biblatex databases, part II
In addition to the classic crossref, biblatex introduces xdata
references in order to source-out common data of entries. Entries
that have "xdata = {somekey}" just inherit all fields from the
respective @xdata entry, if the field is not already defined in
the entry itself (just like crossref, with the exception that @xdata
entries themselves are _never_ output on their own). @xdata entries can
themselves inherit to other @xdata entries (ad infinitum). So you can,
for instance, setup an xdata entry for a book series with series name
that inherits an xdata entry with information of the publisher
(publisher, address). Any book of that series would just need to refer
to the series xdata and add the number.
BiblioInfo now checks, in addition to crossrefs, for such xdata
references and inherits missing fields.
Nte that biblatex also introduces an "xref" field as an alternative to
crossref. We must not care about that, since the point of xref is that
it does not inherit fields from the target (just cites that one if a
given number of refs to it exist)
2016-09-18 10:44:12 +00:00
|
|
|
/// Note that this will retrieve data from the crossref or xdata as needed.
|
2017-01-07 16:12:08 +00:00
|
|
|
/// \param ci contains further context information, such as if it should
|
|
|
|
/// output any richtext tags marked in the citation format and escape < and >
|
|
|
|
/// elsewhere, and the general output context.
|
2010-03-29 18:37:25 +00:00
|
|
|
docstring const getInfo(docstring const & key, Buffer const & buf,
|
2017-01-07 16:12:08 +00:00
|
|
|
CiteItem const & ci) const;
|
2012-03-01 00:41:30 +00:00
|
|
|
/// \return formatted BibTeX data for citation labels.
|
|
|
|
/// Citation labels can have more than one key.
|
2017-01-07 16:12:08 +00:00
|
|
|
docstring const getLabel(std::vector<docstring> keys, Buffer const & buf,
|
|
|
|
std::string const & style, CiteItem const & ci) const;
|
2010-02-12 16:08:30 +00:00
|
|
|
/// Is this a reference from a bibtex database
|
|
|
|
/// or from a bibliography environment?
|
2010-02-13 15:22:30 +00:00
|
|
|
bool isBibtex(docstring const & key) const;
|
2012-03-01 00:41:30 +00:00
|
|
|
/// Translates the available citation styles into strings for a given
|
|
|
|
/// list of keys, using either numerical or author-year style depending
|
|
|
|
/// upon the active engine.
|
|
|
|
std::vector<docstring> const getCiteStrings(std::vector<docstring> const & keys,
|
2014-05-23 14:59:12 +00:00
|
|
|
std::vector<CitationStyle> const & styles, Buffer const & buf,
|
2017-01-07 16:12:08 +00:00
|
|
|
CiteItem const & ci) const;
|
2010-01-08 16:40:41 +00:00
|
|
|
/// A list of BibTeX keys cited in the current document, sorted by
|
|
|
|
/// the last name of the author.
|
2011-12-03 22:15:11 +00:00
|
|
|
/// Make sure you have called collectCitedEntries() before you try to
|
2010-01-11 16:11:55 +00:00
|
|
|
/// use this. You should probably call it just before you use this.
|
2011-12-03 22:15:11 +00:00
|
|
|
std::vector<docstring> const & citedEntries() const
|
2010-01-11 16:11:55 +00:00
|
|
|
{ return cited_entries_; }
|
2008-02-14 05:14:22 +00:00
|
|
|
///
|
2010-01-08 18:19:13 +00:00
|
|
|
void makeCitationLabels(Buffer const & buf);
|
|
|
|
///
|
2008-02-14 05:14:22 +00:00
|
|
|
const_iterator begin() const { return bimap_.begin(); }
|
|
|
|
///
|
|
|
|
void clear() { bimap_.clear(); }
|
|
|
|
///
|
|
|
|
bool empty() const { return bimap_.empty(); }
|
|
|
|
///
|
|
|
|
const_iterator end() const { return bimap_.end(); }
|
|
|
|
///
|
|
|
|
const_iterator find(docstring const & f) const { return bimap_.find(f); }
|
|
|
|
///
|
2008-04-25 20:03:03 +00:00
|
|
|
void mergeBiblioInfo(BiblioInfo const & info);
|
|
|
|
///
|
2008-02-14 05:14:22 +00:00
|
|
|
BibTeXInfo & operator[](docstring const & f) { return bimap_[f]; }
|
|
|
|
///
|
2008-02-14 17:00:40 +00:00
|
|
|
void addFieldName(docstring const & f) { field_names_.insert(f); }
|
2008-02-14 05:14:22 +00:00
|
|
|
///
|
2008-02-14 17:00:40 +00:00
|
|
|
void addEntryType(docstring const & f) { entry_types_.insert(f); }
|
2008-02-14 05:14:22 +00:00
|
|
|
private:
|
2014-08-22 15:17:36 +00:00
|
|
|
/// Collects the cited entries from buf.
|
|
|
|
void collectCitedEntries(Buffer const & buf);
|
2008-02-14 05:28:59 +00:00
|
|
|
///
|
2008-02-14 17:00:40 +00:00
|
|
|
std::set<docstring> field_names_;
|
2008-02-14 05:28:59 +00:00
|
|
|
///
|
2008-02-14 17:00:40 +00:00
|
|
|
std::set<docstring> entry_types_;
|
2008-02-14 05:28:59 +00:00
|
|
|
/// our map: keys --> BibTeXInfo
|
|
|
|
std::map<docstring, BibTeXInfo> bimap_;
|
2010-01-08 16:40:41 +00:00
|
|
|
/// a possibly sorted list of entries cited in our Buffer.
|
|
|
|
/// do not try to make this a vector<BibTeXInfo *> or anything of
|
2011-12-03 22:15:11 +00:00
|
|
|
/// the sort, because reloads will invalidate those pointers.
|
2010-01-08 16:40:41 +00:00
|
|
|
std::vector<docstring> cited_entries_;
|
2007-08-20 16:30:02 +00:00
|
|
|
};
|
2007-08-14 16:50:51 +00:00
|
|
|
|
|
|
|
} // namespace lyx
|
2008-04-20 15:00:11 +00:00
|
|
|
|
|
|
|
#endif // BIBLIOINFO_H
|