You are viewing an old version of this page. Return to the latest version.
Difference between revisions of "Reference:BlueSpiceUEModuleDOCX"
Extension: BlueSpiceUEModuleDOCX
| Overview | |||
|---|---|---|---|
| Description: | |||
| State: | stable | Dependency: | BlueSpice |
| Developer: | HalloWelt | License: | - |
| Type: | Category: | Export | |
| Edition: | BlueSpice pro | ||
Features[edit source]
Export books to DOCX format
This module allows the UniversalExport wiki article to output as Microsoft Word Office Open XML . The content is inserted in a user-defined, freely selectable template. The conversion is done via an external tool, which is subject to license .
Functionality[edit | edit source]
-
conditions
- If possible, the conversion should be based on HTML template
- CSS / inline-styles should be supported. Here is the floating in pictures a bit critical.
- Running headers and footers are necessary
-
Images are embedded. Attachments are not possible
- The template is a docx file. The generated content from the wiki is inserted into the template at the place where the variable "$ WIKICONTENT $" is located.
- Meta information is stored in the docx document (author, generator, etc)
- The module works with articles and books
{{BSExtensionInfobox
|status=stable
|developer=HalloWelt
|type=BlueSpice
|edition=BlueSpice pro
|active=Yes
|compatible=BlueSpice
|package=Bookmaker
|category=Export
}}
Export books to DOCX format
[[en:{{FULLPAGENAME}}]][[de:UEModuleDOCX]]
[[Category:Extension]]
This module allows the [https://wiki.hallowelt.com/wiki/Functional_Design/UniversalExport UniversalExport] wiki article to output as Microsoft Word [http://en.wikipedia.org/wiki/Office_Open_XML Office Open XML] . The content is inserted in a user-defined, freely selectable template. The conversion is done via an external tool, which is '''subject to license''' .
====<span id="Funktionsweise" class="mw-headline">Functionality</span>====
* conditions
** If possible, the conversion should be based on HTML template
** CSS / inline-styles should be supported. Here is the floating in pictures a bit critical.
** Running headers and footers are necessary
* Images are embedded. Attachments are not possible<br />
** The template is a docx file. The generated content from the wiki is inserted into the template at the place where the variable "$ WIKICONTENT $" is located.
* Meta information is stored in the docx document (author, generator, etc)
* The module works with articles and books| Line 15: | Line 15: | ||
This module allows the [https://wiki.hallowelt.com/wiki/Functional_Design/UniversalExport UniversalExport] wiki article to output as Microsoft Word [http://en.wikipedia.org/wiki/Office_Open_XML Office Open XML] . The content is inserted in a user-defined, freely selectable template. The conversion is done via an external tool, which is '''subject to license''' . | This module allows the [https://wiki.hallowelt.com/wiki/Functional_Design/UniversalExport UniversalExport] wiki article to output as Microsoft Word [http://en.wikipedia.org/wiki/Office_Open_XML Office Open XML] . The content is inserted in a user-defined, freely selectable template. The conversion is done via an external tool, which is '''subject to license''' . | ||
| + | |||
| + | |||
| + | ====<span id="Funktionsweise" class="mw-headline">Functionality</span>==== | ||
| + | * conditions | ||
| + | ** If possible, the conversion should be based on HTML template | ||
| + | ** CSS / inline-styles should be supported. Here is the floating in pictures a bit critical. | ||
| + | ** Running headers and footers are necessary | ||
| + | * Images are embedded. Attachments are not possible<br /> | ||
| + | ** The template is a docx file. The generated content from the wiki is inserted into the template at the place where the variable "$ WIKICONTENT $" is located. | ||
| + | * Meta information is stored in the docx document (author, generator, etc) | ||
| + | * The module works with articles and books | ||