From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Alan E. Davis" Subject: Re: [ANN] org-bibtex.el --- convert between Org headings and bibtex entries Date: Sun, 24 Apr 2011 08:59:32 +1000 Message-ID: References: <87y6357q81.fsf@gmail.com> <027A8D96-05AB-452C-87D3-85D90D24AFB1@tsdye.com> <87vcy81xtv.fsf@gmail.com> <877hanwbyb.fsf@gmail.com> <89A178C3-C2E4-493D-BE84-12200512B766@tsdye.com> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=000e0ce0b492ad34b204a19deec9 Return-path: Received: from eggs.gnu.org ([140.186.70.92]:41063) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QDlnw-0006pM-8N for emacs-orgmode@gnu.org; Sat, 23 Apr 2011 18:59:57 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QDlnv-00083N-3Z for emacs-orgmode@gnu.org; Sat, 23 Apr 2011 18:59:56 -0400 Received: from mail-wy0-f169.google.com ([74.125.82.169]:34337) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QDlnu-00083J-Mm for emacs-orgmode@gnu.org; Sat, 23 Apr 2011 18:59:55 -0400 Received: by wyf19 with SMTP id 19so1240355wyf.0 for ; Sat, 23 Apr 2011 15:59:53 -0700 (PDT) In-Reply-To: <89A178C3-C2E4-493D-BE84-12200512B766@tsdye.com> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Eric Schulte Cc: Org Mode --000e0ce0b492ad34b204a19deec9 Content-Type: text/plain; charset=ISO-8859-1 Some notes on initially trying out this new tool. I have some reservations as to whether it use it. There are certain good reasons in its favor. This works to both store bibtex database entries and export to .bib files. I REALLY like the automagical harvesting of data using cb2Bib. It is unique, and I don't see how to recruit it to produce a database in an org file, or pipe it into this org-bibtex tool. The need to represent the bibtex database entry as a PROPERTY list would appear to me to limit its usefulness to me. A nit: I would prefer to be free to enter any optional field type I wished, when I am entering the data. Of course, the tool as it stands helped me to filter out duplicate fields and unused optional fields from the one bibtex entry I tried using org-bibtex-read: the output of org-bibtex-write was cleaner, and correctly incorporated aligning tabs where I'd carelessly left them out.) My INPUT ENTRY @INCOLLECTION{AED-IER-CR, author = {Junior Noitall}, title = {Specific disruption strategies}, booktitle = {How to annoy the teacher}, publisher = {Noitall Notes}, year = {2011}, editor = {Senior Noitall}, chapter = {13}, pages = {218--243}, address = {Concentric Orbit}, altauthor = {John Smith}, alteditor = {Carl Pumpkin}, isbn = {1-8777753-31-9}, optaddress = {Room X777}, optpages = {\frac{1}{2}} } In the following output, the isbn field is missing. OUTPUT from org-bibtex-write @incollection{AED-IER-CR, author = {Junior Noitall}, title = {Specific disruption strategies}, booktitle = {How to annoy the teacher}, publisher = {Noitall Notes}, year = 2011, editor = {Senior Noitall}, type = {incollection}, chapter = 13, pages = {218--243}, address = {Concentric Orbit} } I understand I may add to the types variable. When using org-bibtex-create, I can enter any arbitrary field as a PROPERTY; however, org-bibtex ignores anything outside of the universe it knows about. Would it be bad practice to allow the export of any arbitrary field type one has recorded? I think the emacs bibtex-mode may recognize erroneous bibtex entries. Somewhere there is code that does that. It would be a huge and excellent addition to be able to pass other types, while checking for proper formatting. Bibtex itself, and the .bst files (at least for bibtex itself; I don't know about biblatex, etc.) will cherry pick the needed fields. Am I wrong about this? I am confused by the duplication of file names, though I can see that at some point one of the two will lose. (Gauss's law of competitive exclusion, referring to the biological case of two species occupying the same ecological niche). Alan Davis --000e0ce0b492ad34b204a19deec9 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Some notes on initially trying out this new tool.=A0 I have some reservatio= ns as to whether it use it.=A0 There are certain good reasons in its favor.=

This works to both store bibtex database entries and export to .bib= files.=A0 I REALLY like the automagical harvesting of data using cb2Bib.= =A0 It is unique, and I don't see how to recruit it to produce a databa= se in an org file, or pipe it into this org-bibtex tool.=A0=A0

The need to represent the bibtex database entry as a PROPERTY list woul= d appear to me to limit its usefulness to me.=A0=A0

A nit: I would = prefer to be free to enter any optional field type I wished, when I am ente= ring the data. =A0 Of course, the tool as it stands helped me to filter out= duplicate fields and unused optional fields from the one bibtex entry I tr= ied using org-bibtex-read: the output of org-bibtex-write was cleaner, and = correctly incorporated aligning tabs where I'd carelessly left them out= .)

My INPUT ENTRY

@INCOLLECTION{A= ED-IER-CR,
=A0 author =3D {Junior Noitall},
=A0 title =3D {Specific d= isruption strategies},
=A0 booktitle =3D {How to annoy the teacher},
= =A0 publisher =3D {Noitall Notes},
=A0 year =3D {2011},
=A0 editor =3D {Senior Noitall},
=A0 chapter =3D= {13},
=A0 pages =3D {218--243},
=A0 address =3D {Concentric Orbit},<= br>=A0 altauthor =3D {John Smith},
=A0 alteditor =3D {Carl Pumpkin},
= =A0 isbn =3D {1-8777753-31-9},
=A0 optaddress =3D {Room X777},
=A0 optpages =3D {\frac{1}{2}}
}
<= /div>
In the following output, the isbn field is missing.=A0

OUTPUT from org-bibtex-write

@incolle= ction{AED-IER-CR,
=A0 author =3D=A0=A0=A0 =A0{Junior Noitall},
=A0 title =3D=A0=A0=A0 =A0{= Specific disruption strategies},
=A0 booktitle =3D=A0=A0=A0 =A0{How to a= nnoy the teacher},
=A0 publisher =3D=A0=A0=A0 =A0{Noitall Notes},
=A0= year =3D=A0=A0=A0 =A02011,
=A0 editor =3D=A0=A0=A0 =A0{Senior Noitall},=
=A0 type =3D=A0=A0=A0 =A0{incollection},
=A0 chapter =3D=A0=A0=A0 =A013,=
=A0 pages =3D=A0=A0=A0 =A0{218--243},
=A0 address =3D=A0=A0=A0 =A0{C= oncentric Orbit}
}

=A0
I understand I may add to the typ= es variable.=A0 When using org-bibtex-create, I can enter any arbitrary fie= ld as a PROPERTY; however, org-bibtex ignores anything outside of the unive= rse it knows about.=A0 Would it be bad practice to allow the export of any = arbitrary field type one has recorded?=A0 I think the emacs bibtex-mode may= recognize erroneous bibtex entries.=A0=A0 Somewhere there is code that doe= s that.=A0=A0 It would be a huge and excellent addition to be able to pass = other types, while checking for proper formatting.=A0 Bibtex itself, and th= e .bst files (at least for bibtex itself; I don't know about biblatex, = etc.) will cherry pick the needed fields.=A0=A0 Am I wrong about this?=A0 <= br>

I am confused by the duplication of file names, though I can see th= at at some point one of the two will lose.=A0 (Gauss's law of competiti= ve exclusion, referring to the biological case of two species occupying the= same ecological niche).=A0


Alan Davis
--000e0ce0b492ad34b204a19deec9--