On Wed, Apr 02, 2008 at 06:04:09PM -0400, Richard Heck wrote: >> Isn't EmbeddedFile all about representing an "Embedded file"? If there >> are problems, they need to be fixed there. But I can't imagine a solution >> getting easier by requiring it to _additionally_ fit into a map<string, >> string>. > > As has been repeatedly said, "biblio", as returned by the bibliography > dialog, isn't a filename. It's just an identifier that TeX can use to FIND > the file it really wants. You can adapt EmbeddedFile so that it holds this > piece of data as "meta info", which is what Bo proposes to do. But surely > this is a hack. It has nothing to do with what an EmbeddedFile represents.
I proposed to use "link" files that are properly embedded, and whose contents is used instead of the file name. So you'd embed "biblio.lnk" with contents "mybiblio", and whenever the FileName (or whatever) class hits a ".lnk" it replaces it with its contents. So when the Bib stuff "resolves" the "file" "biblio.lnk" it will be converted to "mybiblio" which, in turn, wil be resolved by TeX to whatever mybiblio.bi file you made known to TeX. Andre'
