diff options
Diffstat (limited to 'offapi/com/sun/star/document/TypeDetection.idl')
| -rw-r--r-- | offapi/com/sun/star/document/TypeDetection.idl | 32 |
1 files changed, 16 insertions, 16 deletions
diff --git a/offapi/com/sun/star/document/TypeDetection.idl b/offapi/com/sun/star/document/TypeDetection.idl index eb754e62a12e..608398873adc 100644 --- a/offapi/com/sun/star/document/TypeDetection.idl +++ b/offapi/com/sun/star/document/TypeDetection.idl @@ -48,12 +48,12 @@ module com { module sun { module star { module document { //============================================================================= -/** capsulate a type detection service and provide read/write access on it's configuration data. +/** encapsulate a type detection service and provide read/write access on it's configuration data. <p> - It's possible to make a "flat" detection wich may use internal configuration + It's possible to make a "flat" detection which may use internal configuration data only - or a "deep" detection which use special <type>ExtendedTypeDetection</type> - services to look into the document stream. Last mode can be supressed to perform the operation. + services to look into the document stream. Last mode can be suppressed to perform the operation. Of course the results can't be guaranteed then. (e.g. in case the extension was changed) </p> */ @@ -78,7 +78,7 @@ published service TypeDetection Every container item is specified as a set of properties and will be represented by a sequence< <type scope="com::sun::star::beans">PropertyValue</type> > structure. Follow properties are supported: - (But note: not all of them must be present everytimes!) + (But note: not all of them must be present every time!) <table border=1> <tr> @@ -108,12 +108,12 @@ published service TypeDetection <td><em>MediaType</em></td> <td>[string]</td> <td>It contains the MIME or content type descriptor. The differences between a MIME type and - an internal type name was made, to resolve existing ambigities.</td> + an internal type name was made, to resolve existing ambiguities.</td> </tr> <tr> <td><em>ClipboardFormat</em><strong>deprecated!</strong></td> <td>[string]</td> - <td>It was interepreted as an identifier inside clipboard. + <td>It was interpreted as an identifier inside clipboard. Please use new property ContentFormat instead of this now.</td> </tr> <tr> @@ -130,9 +130,9 @@ published service TypeDetection <td>[sequence< string >]</td> <td>This list contains different URL patterns, which identify this type. E.g. data base contents can be described by an new defined protocol like "sql://select*". - In combination with a sutable <type scope="com::sun::star::frame">FrameLoader</type> or - <type>ImportFilter</type>/<type>ExportFilter</type> it woul be possible then, to - layout a sql query output into an office frame.</td> + In combination with a suitable <type scope="com::sun::star::frame">FrameLoader</type> or + <type>ImportFilter</type>/<type>ExportFilter</type> it would be possible then, to + layout a SQL query output into an office frame.</td> </tr> <tr> <td><em>Extensions</em></td> @@ -140,8 +140,8 @@ published service TypeDetection <td>It contains a list of file extensions, which match this type. They must be specified as pure extension, without any special signs. E.g.: "doc", "html" ... but not ".doc". - Using of wildcards is allowed but not very usefull. The may resulting - ambigities with other type registrations can't be resolved anytimes.</td> + Using wild cards is allowed but not very useful. They may result in + ambiguities with other type registrations can't be resolved anytime.</td> </tr> <tr> <td><em>DocumentIconID</em></td> @@ -153,8 +153,8 @@ published service TypeDetection <p> Note:<br> - All elements of this container will be adressed by his internal name, - and it must be an unambigous value. + All elements of this container will be addressed by his internal name, + and it must be an unambiguous value. </p> */ interface com::sun::star::container::XNameAccess; @@ -179,12 +179,12 @@ published service TypeDetection <p> Because the complexness of such configuration set can be very high, - it seams not very usefull to update the undelying configuration layer - on every container change request immediatly. Another strategy can be to + it seams not very useful to update the underlying configuration layer + on every container change request immediately. Another strategy can be to make all changes (adding/changing/removing of items) and call flush at the end. That will validate the whole container and reject inconsistent data sets. Only in case all made changes was correct, they will be written back to the - configuration. Further this interface provides the possibelity, that interested + configuration. Further this interface provides the possibility, that interested changes listener can be registered too. </p> */ |