summaryrefslogtreecommitdiff
path: root/offapi/com/sun/star/document/ExportFilter.idl
diff options
context:
space:
mode:
Diffstat (limited to 'offapi/com/sun/star/document/ExportFilter.idl')
-rw-r--r--offapi/com/sun/star/document/ExportFilter.idl14
1 files changed, 7 insertions, 7 deletions
diff --git a/offapi/com/sun/star/document/ExportFilter.idl b/offapi/com/sun/star/document/ExportFilter.idl
index 91fdd650ef96..5653a0ea5ff7 100644
--- a/offapi/com/sun/star/document/ExportFilter.idl
+++ b/offapi/com/sun/star/document/ExportFilter.idl
@@ -31,7 +31,7 @@ module com { module sun { module star { module document {
<p>
Such filters can be used for exporting a content.
- Of course it's possible to combine it with the service <type>ImportFilter</type>
+ Of course it's possible to combine it with the service ImportFilter
if import functionality should be available at same implementation too.
</p>
@@ -53,15 +53,15 @@ published service ExportFilter
<p>
It's used to filter a document at saving time.
The source document should be already set by using another interface
- <type>XExporter</type> which is supported by this service too.
+ XExporter which is supported by this service too.
</p>
<p>
Tip:<br>
- If same implementation provides the service <type>ImportFilter</type> too,
+ If same implementation provides the service ImportFilter too,
code must distinguish between filtering from a source document (for export) or
filtering to a target document (for import). This can be recognized by saving
- state of used interfaces <type>XExporter</type> or <type>XImporter</type>!
+ state of used interfaces XExporter or XImporter!
Otherwise it's not clear which action is required here.
</p>
*/
@@ -70,14 +70,14 @@ published service ExportFilter
/** support initialization of filter with its own configuration
<p>
- A filter object must be created by global service <type>FilterFactory</type>.
+ A filter object must be created by global service FilterFactory.
If filter supports this optional interface, he will be initialized by the factory directly
after creation. The factory will pass the following information to this new instance:
<ul>
<li>first item will be a set of configuration data of the filter</li>
<li>after that will follow may given optional parameters of call
<member scope="com::sun::star::lang">XMultiServiceFactory::createInstanceWithArguments()</member>
- of service <type>FilterFactory</type>.
+ of service FilterFactory.
</li>
</ul>
See description of service <member>FilterFactory::XNameContainer</member> for a description of
@@ -89,7 +89,7 @@ published service ExportFilter
/** provides access to the internal name of this filter
<p>
- This internal filter name can be used on service <type>FilterFactory</type>
+ This internal filter name can be used on service FilterFactory
to get further information about it (e.g. his registration for mime types or extensions etc.)
It's important that returned string is the "internal name" of the filter which must be
unambiguous against all other registered filters in current installation.