Difference between revisions of "Filter extensions"
(→OOo Filter Extensions: Basic Principles) |
(→OOo Filter Extensions: Basic Principles) |
||
Line 7: | Line 7: | ||
Any document filter (either import or export of both in one component) can be provided as an extension. This extension will contain the filter either as a UNO component (shared library, jar file, Python module) or an xslt file. To make the filter known to OOo as usual a configuration file must be provided that bounds the filter component or xslt file to a particular file type. The configuration format is described in the [[Documentation/DevGuide/OfficeDev/Configuration | Developer's Guide]]. | Any document filter (either import or export of both in one component) can be provided as an extension. This extension will contain the filter either as a UNO component (shared library, jar file, Python module) or an xslt file. To make the filter known to OOo as usual a configuration file must be provided that bounds the filter component or xslt file to a particular file type. The configuration format is described in the [[Documentation/DevGuide/OfficeDev/Configuration | Developer's Guide]]. | ||
− | A detailed description how filters are developed can also be found in the [[Documentation/DevGuide/OfficeDev/Integrating_Import_and_Export_Filters | Developer's Guide. What you can find here is: how can I deploy my filter as an extension? | + | A detailed description how filters are developed can also be found in the [[Documentation/DevGuide/OfficeDev/Integrating_Import_and_Export_Filters | Developer's Guide]]. What you can find here is: how can I deploy my filter as an extension? |
Revision as of 19:13, 26 September 2008
OOo Extensions project
Please view the wiki usage guidelines
|
---|
Categories: Pages: |
Extensions on the main site |
Extensions in other languages: |
OOo Filter Extensions: Basic Principles
Any document filter (either import or export of both in one component) can be provided as an extension. This extension will contain the filter either as a UNO component (shared library, jar file, Python module) or an xslt file. To make the filter known to OOo as usual a configuration file must be provided that bounds the filter component or xslt file to a particular file type. The configuration format is described in the Developer's Guide.
A detailed description how filters are developed can also be found in the Developer's Guide. What you can find here is: how can I deploy my filter as an extension?