Bo Peng wrote:
I have to say that it seems messy to me that we're effectively storing
two sets of things that have the same significance: params["bibfiles"],
on the one hand, and the embedded file list, on the other. This makes
the logic in InsetBibtex, on which I worked a fair bit and would have
thought I understood, very complicated. Couldn't we just store the one
and have some way of looking up the necessary information when it's needed?
InsetCommand derived insets all store params strings, which can not
store all the information an EmbeddedFile need. Converson between them
have been troublesome....
Yes, I see that much, but that doesn't seem to mean we have to STORE two
copies of this data, does it? It gets constructed (here) in
createBibFiles, and it could presumably be reconstructed when necessary.
Right?
Can you explain to me what the embed parameter here is supposed to mean?
I have e.g.
\begin_inset CommandInset bibtex
LatexCommand bibtex
bibfiles "/home/rgheck/files/bibtex/biblio"
embed "./LyX.Embed.Dir.Abs//home/rgheck/files/bibtex/biblio.bib"
options "plain"
\end_inset
in one case and:
\begin_inset CommandInset bibtex
LatexCommand bibtex
bibfiles "biblio"
embed "./biblio"
options "plain"
\end_inset
in another.
rh
