Johannes Wilm wrote: > >> You can already choose custom processors. > > yes, but in this case it would have to be automatically chosen when a > certain biblatex option is chosen.
No, vice versa. A proper biblatex implementation will have to set the correct option depending on the selected processor. > > Of course, I don't know the source code as well. it just seems like a > > > >> gigantic project to me to make all this user configurabel and to allow > >> for any other possible citation system. > >> > >> We strive to make it as flexible as we can, within reason. Worst case, > >> > > you define BibLaTeX as a new cite engine within the existing system. > > yes, that is what I am afraid it has to come down to. Additionally, a lot > of gui-elements will have to get two versions -- one used if > natbib/jurabib are in use and one if biblatex is in use. For example if > one clicks on a bibliography somewhere in the document, two very different > dialogs have to be shown. And for the biblatex version there needs to be > some easily accessible place where one can specify all the databases in > use. This is a global setting, so I'm not sure where this can be put, > really. Why? You still can use the current elements. You set a bibtex inset (as now), and it will just be output as preamble element in case biblatex is selected. The user will not need to notice this. The current bibtex dialog can very well capture this. The same applies to the citation dialog. You might need to add some additional widgets, but in practice, you can simply use the current dialog. I really do not see where the problem is. Jürgen
