On Monday, November 18, 2013 7:41:28 PM UTC-8, Jacob Peck wrote: > > > Interesting thoughts. Here's my take on your points.
> Bibtex.py autolookups -- this should be trivial, and could probably be > baked into the bibtex.py plugin at somepoint. > > The CrossRef service to convert DOI to bibtex is pretty straightforward, the partial bibliography lookup is a bit more involved. I like that bibtex.py keeps an external database updated. It makes it handy to add records from external tools. > Citations -- don't forget Chicago and Turabian! > Too true. I haven't run across them as a requirement, yet. > > Notes & references -- potentially handled by @url nodes? Depends on what > you mean by references... in-text, or simply in-outline links. The > latter case is a perfect use for @url nodes. > > bibtex records can be created for pretty much every piece of anything, even things that the user creates for them self. Being able to authoritatively cite an idea as being originally mine would be worth the extra bit of overhead to me. :-). A big part of my flow now is to attach clones of the bibtex record to the document where the ideas which are cited inline resides. From that record I create the MLA or APA bibliography entries by hand using the style guide. > PDFs -- this one is perhaps the hardest task. This would require a > great deal of work. > > Yup. I spent a couple of days a while back examining the problem that Docear is facing. The only solution I could come up with was to allow the use of only one pdf reader and customize the Leo end to fit, or to use poppler or XPDF to roll our own. Both avenues have problems. > As a side note, I use Leo to write. I have a pretty slick setup that > uses Leo as an editor and outliner, GNU Make as a build system, ConTeXt > as my document preparer, and git as version control. Four simple tools > that work so well together. Here's my bare-bones setup: > https://github.com/gatesphere/context-leo-make This could easily work > with BibTeX, and with a bit of work would be just fine for LaTeX work as > well. It's a far cry from what you've indicated, but it's a step in the > right direction. > > -->Jake > Thanks. I have checked it out and will be reading up on ConText. It has been a couple of years since I have looked at the Latex side of things. Chris -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/groups/opt_out.
