*api: convert <member>method</member> to method()

Doxygen will only recognize a un-qualified method name as such if it is
followed by "()".

sed -i "s,<member>\([a-z][^<]\+[^)]\)</member>,\1(),g"

Change-Id: I69bc17849e76f3a3d91c6daf0f1be8168a83cfc5

5 files changed, 8 insertions, 8 deletions

diff --git a/offapi/com/sun/star/form/XBoundComponent.idl b/offapi/com/sun/star/form/XBoundComponent.idl
index 4f3bd6dc8221..c1bc3249af5d 100644
--- a/offapi/com/sun/star/form/XBoundComponent.idl
+++ b/offapi/com/sun/star/form/XBoundComponent.idl
@@ -29,7 +29,7 @@
 /** specifies a (form) component which is bound to a data source.
 
     <p>The interface provides the possibility of committing its respective
-    data to a data source it is bound to. A <member>commit</member> will be
+    data to a data source it is bound to. A commit() will be
     performed by the environment (usually, a FormController).<br/>
     For example, suppose you have a data-bound control that is connected
     to a database field. Each time the control loses its focus, the
diff --git a/offapi/com/sun/star/form/XFormsSupplier2.idl b/offapi/com/sun/star/form/XFormsSupplier2.idl
index 1d7efaf1e582..2483ed81bdb9 100644
--- a/offapi/com/sun/star/form/XFormsSupplier2.idl
+++ b/offapi/com/sun/star/form/XFormsSupplier2.idl
@@ -33,11 +33,11 @@ interface XFormsSupplier2: XFormsSupplier
     /** determines whether there are currently forms available at all
 
         <p>If you need read access to the forms collection, then you might check
-        the existence of forms using <member>hasForms</member>, and if it returns
+        the existence of forms using hasForms(), and if it returns
         <FALSE/>, you can do as if <member>XFormsSupplier::getForms</member> would
         have returned an empty container.</p>
 
-        <p>Semantically, <member>hasForms</member> is equivalent to calling
+        <p>Semantically, hasForms() is equivalent to calling
         <member>XElementAccess::hasElements</member> on the container returned by
         <member>XFormsSupplier::getForms</member>. But when using the latter, the
         implementation is forced to create a empty container, which might be potentially
diff --git a/offapi/com/sun/star/form/binding/XValueBinding.idl b/offapi/com/sun/star/form/binding/XValueBinding.idl
index 83e9689e3afa..e3c1276f1897 100644
--- a/offapi/com/sun/star/form/binding/XValueBinding.idl
+++ b/offapi/com/sun/star/form/binding/XValueBinding.idl
@@ -42,7 +42,7 @@ interface XValueBinding : com::sun::star::uno::XInterface
 
     /** determines whether a given type is supported by this binding for value exchange
 
-        <p>Calling this method is equal to calling <member>getSupportedValueTypes</member>,
+        <p>Calling this method is equal to calling getSupportedValueTypes(),
         and looking up the given type in the resulting type sequence.</p>
 
         @see getSupportedValueTypes
diff --git a/offapi/com/sun/star/form/runtime/XFormOperations.idl b/offapi/com/sun/star/form/runtime/XFormOperations.idl
index c01332788b88..ac14fb4ceac6 100644
--- a/offapi/com/sun/star/form/runtime/XFormOperations.idl
+++ b/offapi/com/sun/star/form/runtime/XFormOperations.idl
@@ -61,7 +61,7 @@ interface XFeatureInvalidation;
     com::sun::star::form::component::DataForm.</p>
 
     <p>If you agree that this is ugly to do and maintain, then <code>XFormOperations</code>
-    is for you. It provides a <member>execute</member> method, which will do all of the above
+    is for you. It provides a execute() method, which will do all of the above
     for you; plus some similar convenient wrappers for similar functionality.</p>
 
     @see FormFeature
@@ -107,7 +107,7 @@ interface XFormOperations : ::com::sun::star::lang::XComponent
 
     /** determines whether a feature is currently enabled.
 
-        <p>Calling this is equivalent to calling <member>getState</member>, and evaluating the
+        <p>Calling this is equivalent to calling getState(), and evaluating the
         <member>FeatureState::Enabled</member> member.</p>
 
         @param Feature
@@ -235,7 +235,7 @@ interface XFormOperations : ::com::sun::star::lang::XComponent
         whenever the state of any supported feature might have changed.</p>
 
         <p>For instance, imagine a form whose current row has just been moved to another
-        record, using the <member>execute</member> method. This means that potentially, the state
+        record, using the execute() method. This means that potentially, the state
         of all movement-related features might have changed.</p>
 
         <p>Note that the instance does not actually notify changes in the feature states, but only
diff --git a/offapi/com/sun/star/form/validation/XValidatableFormComponent.idl b/offapi/com/sun/star/form/validation/XValidatableFormComponent.idl
index a1c332a86f85..90f5466a5435 100644
--- a/offapi/com/sun/star/form/validation/XValidatableFormComponent.idl
+++ b/offapi/com/sun/star/form/validation/XValidatableFormComponent.idl
@@ -59,7 +59,7 @@ interface XValidatableFormComponent : XValidatable
         at the validator.
 
         <p>Calling this is equal to calling <member>XValidator::isValid</member> with
-        the current value (see <member>getCurrentValue</member>) of the component, where
+        the current value (see getCurrentValue()) of the component, where
         the validator is obtained via <member>XValidatable::getValidator</member>.</p>
 
         <p>If no validator has been set (<member>XValidatable::setValidator</member>), this method