export to MS Office xml with JabRef custom export layout file

Issue #1334 resolved
Former user created an issue

BibSonomy allows to upload custom export filter created with JabRef. These filters are usually in a .layout file. JabRef allows to export any database to Microsoft Office 2007 xml. So it should be easy to upload the corresponding .layout file to BibSonomy and download from BibSonomy directly in MS Office xml format.

But: Where is the JabRef layout file for MS Office xml?? I have downloaded the newest stable Jabref source code and in srcresourcelayout there are a lot of layout files, but I could not figure out which one is for export to MS Office xml.

I posted to the JabRef forum: https://sourceforge.net/projects/jabref/forums/forum/318825/topic/4061082

If you can help me and if you consider this a useful feature, maybe it makes sense to add "Export to MS Office xml" to the default BibSonomy export options here: http://www.bibsonomy.org/export/

Comments (15)

  1. Former user Account Deleted

    Commented by dbe: reply from the jabref forum:

    ok, as far as i understand it now, the export to MS Office xml is not handled by the .layout files in srcresourcelayout but it is handled by a module which can be found in srcjavanetsfjabrefmsbib Anyway, using the information available in the links below it should be possible to create a layout file for Microsoft Office xml read more here:

    https://sourceforge.net/projects/jabref/forums/forum/318824/topic/1728578 http://mahbub.wordpress.com/2007/03/22/deciphering-microsoft-office-2007-bibliography-format/ http://mahbub.wordpress.com/2007/03/24/details-of-microsoft-office-2007-bibliographic-format-compared-to-bibtex/

  2. Former user Account Deleted

    Commented by dbe: We just looked into this - as said in the Jabref forum reply, the MS Office xml export from JabRef is not done via a .layout template, but rather by a handcrafted model-converter implemented in Java. For this reason, it is not straightforward to add this export facility into our current export framework - but we are exploring further integration possibilities.

    Until then, maybe this tool can be useful for you:

    http://sites.google.com/site/sdudah/bibtex2word2007bibliographyconverter

    It basically takes a BibTeX-File as input, and converts it (using the AWK scripting language) to MS office XML.

  3. Former user Account Deleted

    have a look if you can find ways to implement it with the current jabref version in bibsonomy. Otherwise please contact Robert for changes in the old jabref code which is maybe still needed in the new jabref version.

  4. Former user Account Deleted

    Today, i comitted a first implementation to the JabRef-MSOfficeXML-Export branch, it features export to MSOfficeXML via Export-Page, the "Cite this publication"-Box and our REST-API (?format=msofficexml).

  5. Daniel Zoller
    • changed status to open

    I do not like how the JabrefMSOfficeXMLRenderer bypasses the JabrefLayoutRenderer, which should encapsulate all interaction with Jabref to render publications in various formats.

    Please integrate the MS office XML rendering into the JabrefLayoutRenderer.

  6. Former user Account Deleted

    I integrated the feature into the JabrefLayoutRenderer. It contains SelfRenderingJabrefLayouts, an extension of the standart JabrefLayout, which bypasses the "standart" rendering Process of JabrefLayouts and instead uses the MSBibDatabase and MSBibEntry of Jabref to render MSOfficeXML-Files. New SelfRenderingLayouts have to be registered in the JabrefLayouts-Class. They also need an entry in the JabrefLayouts.xml, basically to set properties like "displayed-name" and "discription" which are shown on the export page.

  7. Log in to comment