Citations are exported to MS-Word & LaTeX

[Joeran]

Would be great if the MS-Word Export would also export citations. Not sure though, how we could implement this.

a) We add some placeholders, and once the Document is opened with MS-Word and Docear4Word, Docear4Word replaces the placeholders with the correct citations.

b) We add the real citation data. However, this would probably be a lot of work for us to implement

[stlanger]

same for LaTeX

[Joeran]

the latex export should include citations. here, an email from a user

Ok, I think most important are text and citations. For citations there are a lot of commands and options, but the very basics is that there should be a \cite{key} command at the required positions in the text. At the end of the latex document you need two commands: \bibliographystyle{plain} \bibliography{bibtexfile}

I attach a template to illustrate how the export would be useful for article writing. You would compile it using the pdflatex and bibtex programs.

see also #180 (pdf export)

[stth1998]

I have some work for that, see https://github.com/Docear/Desktop/pull/433

€: ah i see there's automatic referencing...

the "import" meant importing the file in the repos, actually it exports latex ;)

[stth1998]

Some further ideas for the mm2latex*-xslts:

The content extracted from the nodes should be mostly the same. But it is reimplemented in all 3 existing xslts. Here is a trick:

• parameterize the content-xslt with num-layers, sec-name_layer-one, sec-name_layer-two, etc.
• let the scrbook-xslt and srcartkl-xslt export only document-header and footer, include the content-xsl, set the layer-name parameters, and let the imported one do the rest

[stlanger]

Hello stth1998,

just to have all necessary information in this ticket as well and to clear things up (there was some confusion in our team): I have already merged your work into our code base on Aug 4th - thanks again for your efforts. :) If you have any ideas on how to further improve the feature and would want to implement the necessary changes, your help will be very much appreciated! ;)

[stth1998]

Hi,

yes I could provide some work on the xsl transformations. But I would like to avoid the integration into the GUI :)

Do you have any Feedback of users who used the old transformations? Where are the test cases (mind maps) you spoke of? Also I would need some information with which engine and how the xsl translations are invoked by Docear.

As I already wrote somewhere else, there should be a way of telling the user what an export function does and what input it expects (what it translates and what it ignores) the information I can provide. Question is, where to tell the user.

Cheers

[Joeran]

As I already wrote somewhere else, there should be a way of telling the user what an export function does and what input it expects (what it translates and what it ignores) the information I can provide. Question is, where to tell the user.

If you send me the text by email (or as html, or just here in the comments), I will gladly add the text to http://www.docear.org/support/user-manual/#Export_mind_maps

[stth1998]

i consider doing some changes before writing that text.

Before I proceed, I need to know to things:

ATM it only exports as scrbook. If you had the option run the XSLT for different latex document classes, how would the user tell which? Or is it ok to only have one document class?

€: this is mainly because some dc's know chapter and have 4 structure levels and some don't and have 3 structure levels-

And whow could docear tell the transformation?

Also I would need some information with which engine and how the xsl translations are invoked by Docear.

€ ah I now see, that I did the correct integration accidentially by myself :) but the method yields, that there is no way of passing different options to the transformation. Or am I wrong with that?

[stth1998]

The export crashes due to XSLT Version in Docear 1.1.0.1. The active variant requires XSLT 2.0.

€ the easy solution is in the comments at the beginning of the file.

[stth1998]

doc:

The export filter "latex input with cites and details" needs an input mind map that has a structure like a document. It will put out a complete latex document structure containing headings and content structured in headwords as well as text from the node's details. That file(s) has to be included in your document template using \input{content}.

The mind map has to be hierarchical. All items which are numbered will become headings of the corresponding layer (e.g. direct sub nodes of the root node become chapters, their direct sub nodes will create sections, and so on). Sub nodes without numbering directly under a numbered one (no matter in which layer) become Paragraphs with a headline. All other structures are put in (nested) \description{} environments. Detail text of a node is put into the description items. Cites will result in a \cite{} at any place and thus put your notes from its sub nodes into a description environment. Notes will be a \todo{} annotation which requires the package todonotes.

[Joeran]

thank you very much, i added the text to the manual http://www.docear.org/support/user-manual/#Export_mind_maps

now, we only need to include your changes and release a new version :-)

[stth1998]

before i change it to sth. impossible: will there be xslt2.0 export by docear or only xslt1.0?

[Joeran]

@stth1998 sorry for not getting back to you earlier. Unfortunately, Stefan has been extremely busy during the past weeks, and he will probably also be busy for the next couple of weeks. Hence, I hope that you answers your question as soon as possible but it might take a while.