This is an automated email from the ASF dual-hosted git repository.
mseidel pushed a commit to branch AOO42X
in repository https://gitbox.apache.org/repos/asf/openoffice.git
The following commit(s) were added to refs/heads/AOO42X by this push:
new 68ea09259d Fixed typos
68ea09259d is described below
commit 68ea09259ddf3752a07e09418da905914e36ec09
Author: mseidel <msei...@apache.org>
AuthorDate: Tue Sep 10 23:15:22 2024 +0200
Fixed typos
(cherry picked from commit 341b93848998051a4360ac5c6edba28fdeb619ef)
---
.../star/document/ExtendedTypeDetectionFactory.idl | 19 +++++++-------
.../offapi/com/sun/star/document/FilterFactory.idl | 25 +++++++++----------
.../offapi/com/sun/star/document/TypeDetection.idl | 29 +++++++++++-----------
3 files changed, 35 insertions(+), 38 deletions(-)
diff --git a/main/offapi/com/sun/star/document/ExtendedTypeDetectionFactory.idl
b/main/offapi/com/sun/star/document/ExtendedTypeDetectionFactory.idl
index d0daffee1b..c5bc07fc23 100644
--- a/main/offapi/com/sun/star/document/ExtendedTypeDetectionFactory.idl
+++ b/main/offapi/com/sun/star/document/ExtendedTypeDetectionFactory.idl
@@ -1,5 +1,5 @@
/**************************************************************
- *
+ *
* Licensed to the Apache Software Foundation (ASF) under one
* or more contributor license agreements. See the NOTICE file
* distributed with this work for additional information
@@ -7,19 +7,18 @@
* to you under the Apache License, Version 2.0 (the
* "License"); you may not use this file except in compliance
* with the License. You may obtain a copy of the License at
- *
+ *
* http://www.apache.org/licenses/LICENSE-2.0
- *
+ *
* Unless required by applicable law or agreed to in writing,
* software distributed under the License is distributed on an
* "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
* KIND, either express or implied. See the License for the
* specific language governing permissions and limitations
* under the License.
- *
+ *
*************************************************************/
-
#ifndef __com_sun_star_document_ExtendedTypeDetectionFactory_idl__
#define __com_sun_star_document_ExtendedTypeDetectionFactory_idl__
@@ -68,7 +67,7 @@ published service ExtendedTypeDetectionFactory
<ul>
<li>sequence< Any >[0] contains a sequence< <type
scope="com::sun::star::beans">PropertyValue</type> >,
which represent the configuration data set of this detector
component. The used properties are the same, as
- they are available at the container interface of this factoyr
service. (see below)</li>
+ they are available at the container interface of this factory
service. (see below)</li>
<li>Every following item of the argument list sequence< Any
>[1..n] contains the copied argument of the
corresponding createInstanceWithArguments() call. That means:
Item 0 or the original list was copied as
item 1 of the destination list ... etc.
@@ -84,7 +83,7 @@ published service ExtendedTypeDetectionFactory
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!)
</p>
<table border=1>
<tr>
@@ -130,13 +129,13 @@ published service ExtendedTypeDetectionFactory
/** can be used to perform container changes.
<p>
- Because the complexness of such configuration set can be very high,
- it does not seem very useful to update the undelying configuration
layer
+ Because the complexity of such configuration set can be very high,
+ it does not seem 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>
*/
diff --git a/main/offapi/com/sun/star/document/FilterFactory.idl
b/main/offapi/com/sun/star/document/FilterFactory.idl
index 83d25ef385..896ca1e54c 100644
--- a/main/offapi/com/sun/star/document/FilterFactory.idl
+++ b/main/offapi/com/sun/star/document/FilterFactory.idl
@@ -1,5 +1,5 @@
/**************************************************************
- *
+ *
* Licensed to the Apache Software Foundation (ASF) under one
* or more contributor license agreements. See the NOTICE file
* distributed with this work for additional information
@@ -7,19 +7,18 @@
* to you under the Apache License, Version 2.0 (the
* "License"); you may not use this file except in compliance
* with the License. You may obtain a copy of the License at
- *
+ *
* http://www.apache.org/licenses/LICENSE-2.0
- *
+ *
* Unless required by applicable law or agreed to in writing,
* software distributed under the License is distributed on an
* "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
* KIND, either express or implied. See the License for the
* specific language governing permissions and limitations
* under the License.
- *
+ *
*************************************************************/
-
#ifndef __com_sun_star_document_FilterFactory_idl__
#define __com_sun_star_document_FilterFactory_idl__
@@ -65,7 +64,7 @@ published service FilterFactory
/** factory interface to create and initialize filter components.
<p>
- <strong>Current behaviour</strong><p>
+ <strong>Current behavior</strong><p>
The methods createInstance() or createInstanceWithArguments() of this
interface must be
called with an internal type name!. This name is used internally to
search a suitable
(mostly the default) filter for this type then. The found filter will
be created, initialized
@@ -91,7 +90,7 @@ published service FilterFactory
</p>
<p>
- <strong>Proposed behaviour</strong><p>
+ <strong>Proposed behavior</strong><p>
Searching of a suitable filter for a given internal type name, must be
done by the new interface
<type scope="com::sun::star::container">XContainerQuery</type>,
available on this factory too.
The factory interface can be used to create filter components by its
internal filter name only.
@@ -99,7 +98,7 @@ published service FilterFactory
<p>
<strong>How it can be distinguished?</strong><p>
- The new prosposed implementation will throw an <type
scope="com::sun::star::container">NoSuchElementException</type>
+ The new proposed implementation will throw an <type
scope="com::sun::star::container">NoSuchElementException</type>
if the first parameter of createInstance() or
createInstanceWithArguments() does not match to a valid container (means
filter) item. Further it will throw an <type
scope="com::sun::star::lang">IllegalArgumentException</type> if the optional
parameter "FilterName" could not be detected inside the argument list
of call createInstanceWithArguments().
@@ -130,7 +129,7 @@ published service FilterFactory
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!)
</p>
<table border=1>
<tr>
@@ -160,7 +159,7 @@ published service FilterFactory
<td><em>Type</em></td>
<td>[string]</td>
<td>Every filter is registered for a type. This value contains
the internal name of it.
- (see service <type>TypeDetection</type> for further
informations)</td>
+ (see service <type>TypeDetection</type> for further
information)</td>
</tr>
<tr>
<td><em>DocumentService</em></td>
@@ -203,7 +202,7 @@ published service FilterFactory
<p>
Note:<br>
All elements of this container will be addressed by its internal name,
- and it must be an unambigous value.
+ and it must be an unambiguous value.
</p>
*/
interface com::sun::star::container::XNameAccess;
@@ -227,13 +226,13 @@ published service FilterFactory
/** can be used to perform container changes.
<p>
- Because the complexness of such configuration set can be very high,
+ Because the complexity of such configuration set can be very high,
it does not seem 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>
*/
diff --git a/main/offapi/com/sun/star/document/TypeDetection.idl
b/main/offapi/com/sun/star/document/TypeDetection.idl
index 5f60f1fc5e..b3a7ffd825 100644
--- a/main/offapi/com/sun/star/document/TypeDetection.idl
+++ b/main/offapi/com/sun/star/document/TypeDetection.idl
@@ -1,5 +1,5 @@
/**************************************************************
- *
+ *
* Licensed to the Apache Software Foundation (ASF) under one
* or more contributor license agreements. See the NOTICE file
* distributed with this work for additional information
@@ -7,19 +7,18 @@
* to you under the Apache License, Version 2.0 (the
* "License"); you may not use this file except in compliance
* with the License. You may obtain a copy of the License at
- *
+ *
* http://www.apache.org/licenses/LICENSE-2.0
- *
+ *
* Unless required by applicable law or agreed to in writing,
* software distributed under the License is distributed on an
* "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
* KIND, either express or implied. See the License for the
* specific language governing permissions and limitations
* under the License.
- *
+ *
*************************************************************/
-
#ifndef __com_sun_star_document_TypeDetection_idl__
#define __com_sun_star_document_TypeDetection_idl__
@@ -44,7 +43,7 @@
module com { module sun { module star { module document {
//=============================================================================
-/** capsulate a type detection service and provide read/write access on it's
configuration data.
+/** capsulate a type detection service and provide read/write access on its
configuration data.
<p>
It's possible to make a "flat" detection which may use internal
configuration
@@ -74,7 +73,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>
@@ -104,12 +103,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>
@@ -126,7 +125,7 @@ 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
+ In combination with a suitable <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>
</tr>
@@ -137,7 +136,7 @@ published service TypeDetection
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 useful. The may
resulting
- ambigities with other type registrations can't be resolved
anytimes.</td>
+ ambiguities with other type registrations can't be
resolved any time.</td>
</tr>
<tr>
<td><em>DocumentIconID</em></td>
@@ -150,7 +149,7 @@ published service TypeDetection
<p>
Note:<br>
All elements of this container will be addressed by his internal name,
- and it must be an unambigous value.
+ and it must be an unambiguous value.
</p>
*/
interface com::sun::star::container::XNameAccess;
@@ -165,7 +164,7 @@ published service TypeDetection
<p>
Against simple property search it provides some complex algorithms too.
- For further informations please read the SDK documentation.
+ For further information please read the SDK documentation.
</p>
*/
[optional] interface com::sun::star::container::XContainerQuery;
@@ -174,13 +173,13 @@ published service TypeDetection
/** can be used to perform container changes.
<p>
- Because the complexness of such configuration set can be very high,
+ Because the complexity of such configuration set can be very high,
it does not seem 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>
*/
