*api: convert <member scope="foo">bar</member>

sed -i 's,<member scope="\([^"]*\)">\([^<]*::[a-z][^<:]\+[^)]\)</member>,\1::\2(),g'

Change-Id: I265ff28fee73a271f205294e59955b3a1c81d95a

10 files changed, 25 insertions, 25 deletions

diff --git a/udkapi/com/sun/star/bridge/oleautomation/BridgeSupplier.idl b/udkapi/com/sun/star/bridge/oleautomation/BridgeSupplier.idl
index 59e1b2c0875c..44d6a70482a9 100644
--- a/udkapi/com/sun/star/bridge/oleautomation/BridgeSupplier.idl
+++ b/udkapi/com/sun/star/bridge/oleautomation/BridgeSupplier.idl
@@ -28,7 +28,7 @@ module com { module sun { module star { module bridge { module oleautomation {
 /** maps UNO types to oleautomation types and vice versa.
     <p>
     The function
-    <member scope="com::sun::star::bridge">XBridgeSupplier2::createBridge</member>
+    com::sun::star::bridge::XBridgeSupplier2::createBridge()
     maps a value of a UNO or Automation type to the desired target type. If a UNO
     interface was mapped  to <code>IDispatch</code>, then all objects
     (interfaces, structs) and other types which are obtained from that Automation
@@ -36,7 +36,7 @@ module com { module sun { module star { module bridge { module oleautomation {
     if one provides an initial object which forms the root of all other objects,
     such as a service manager, then only that object needs to be explicitly
     mapped by a call to
-    <member scope="com::sun::star::bridge">XBridgeSupplier2::createBridge</member>.
+    com::sun::star::bridge::XBridgeSupplier2::createBridge().
     The same holds true if an automation  object is mapped to an UNO interface.
     </p>
     <p>
diff --git a/udkapi/com/sun/star/bridge/oleautomation/PropertyPutArgument.idl b/udkapi/com/sun/star/bridge/oleautomation/PropertyPutArgument.idl
index 6cd0fe2c70ac..93e6cd8455d5 100644
--- a/udkapi/com/sun/star/bridge/oleautomation/PropertyPutArgument.idl
+++ b/udkapi/com/sun/star/bridge/oleautomation/PropertyPutArgument.idl
@@ -31,13 +31,13 @@ module com {  module sun {  module star {  module bridge {  module oleautomation
     then it is accessed through the
     com::sun::star::script::XInvocation interface.
     The methods
-    <member scope="com::sun::star::script">XInvocation::setValue</member>
+    com::sun::star::script::XInvocation::setValue()
     and
-    <member scope="com::sun::star::script">XInvocation::getValue</member>
+    com::sun::star::script::XInvocation::getValue()
     are used to access properties which do not have additional
     arguments. To access a property with additional arguments, the
     method
-    <member scope="com::sun::star::script">XInvocation::invoke</member>
+    com::sun::star::script::XInvocation::invoke()
     has to be used. The method implementation must decide, if the
     property is to be written or read so it can perform the proper
     operation on the Automation object. To make this decision, the
diff --git a/udkapi/com/sun/star/io/XAsyncOutputMonitor.idl b/udkapi/com/sun/star/io/XAsyncOutputMonitor.idl
index f3f4fd7d64c6..e8363eb1e7c3 100644
--- a/udkapi/com/sun/star/io/XAsyncOutputMonitor.idl
+++ b/udkapi/com/sun/star/io/XAsyncOutputMonitor.idl
@@ -28,42 +28,42 @@ module com { module sun { module star { module io {
 /**
    An optional companion interface to
    com::sun::star::io::XOutputStream that supports scenarios
-   where <member scope="com::sun::star::io">XOutputStream::writeBytes</member>
+   where com::sun::star::io::XOutputStream::writeBytes()
    operates asynchronously and does not necessarily report any errors.
 
    <p>A typical scenario where this interface is useful is when an
    com::sun::star::io::XOutputStream is used to write to a
    file via NFS.  Normally, any calls to
-   <member scope="com::sun::star::io">XOutputStream::writeBytes</member> will
+   com::sun::star::io::XOutputStream::writeBytes() will
    execute asynchronously then, in that any potential errors might only be
    reported by later calls to
-   <member scope="com::sun::star::io">XOutputStream::writeBytes</member> or
-   <member scope="com::sun::star::io">XOutputStream::closeOutput</member>.  If
+   com::sun::star::io::XOutputStream::writeBytes() or
+   com::sun::star::io::XOutputStream::closeOutput().  If
    such an output stream shall not be closed immediately after one or more calls
-   to <member scope="com::sun::star::io">XOutputStream::writeBytes</member>, but
+   to com::sun::star::io::XOutputStream::writeBytes(), but
    the client wants to know as soon as possible whether writing was successful,
    then <member
    scope="com::sun::star::io">XAsyncOutputMonitor::waitForCompletion</member>
    should be called after the series of calls to
-   <member scope="com::sun::star::io">XOutputStream::writeBytes</member>.</p>
+   com::sun::star::io::XOutputStream::writeBytes().</p>
 
    @since OOo 2.0
 */
 interface XAsyncOutputMonitor {
     /**
        waits for the completion of any previous calls to
-       <member scope="com::sun::star::io">XOutputStream::writeBytes</member>,
+       com::sun::star::io::XOutputStream::writeBytes(),
        and reports potentially pending errors.
 
        <p>Calling this method is potentially expensive (even if the associated
        com::sun::star::io::XOutputStream represents a local
        file not accessed via NFS, for example).  This method has a similar
        description to
-       <member scope="com::sun::star::io">XOutputStream::flush</member>.
+       com::sun::star::io::XOutputStream::flush().
        However, where the semantics of <code>flush</code> are rather vague,
        <code>waitForCompletion</code> has very specific semantics&mdash;it just
        blocks long enough so that any errors encountered during previous calls
-       to <member scope="com::sun::star::io">XOutputStream::writeBytes</member>
+       to com::sun::star::io::XOutputStream::writeBytes()
        can reliably be reported.  It specificially does not guarantee that any
        data have savely been stored on a stable physical medium, like a hard
        disk (and it is completely unspecified whether <code>flush</code> should
diff --git a/udkapi/com/sun/star/java/XJavaVM.idl b/udkapi/com/sun/star/java/XJavaVM.idl
index 7e730366bf9c..43d141b7eb1a 100644
--- a/udkapi/com/sun/star/java/XJavaVM.idl
+++ b/udkapi/com/sun/star/java/XJavaVM.idl
@@ -30,7 +30,7 @@ module com {  module sun {  module star {  module java {
     A UNO interface seems to be at the wrong abstraction level for this
     functionality (also, the C++ classes <code>jvmaccess::VirtualMachine</code>
     and <code>jvmaccess::UnoVirtualMachine</code> used by
-    <member scope="com::sun::star::java">XJavaVM::getJavaVM</member> are not
+    com::sun::star::java::XJavaVM::getJavaVM() are not
     part of the public C++ UNO runtime API).  This should probably be replaced
     by an appropriate C/C++ API.
  */
diff --git a/udkapi/com/sun/star/lang/MultiServiceFactory.idl b/udkapi/com/sun/star/lang/MultiServiceFactory.idl
index ea8cb01fcb83..24e4fd4cc443 100644
--- a/udkapi/com/sun/star/lang/MultiServiceFactory.idl
+++ b/udkapi/com/sun/star/lang/MultiServiceFactory.idl
@@ -38,7 +38,7 @@ module com {  module sun {  module star {  module lang {
     interface can be supported optionally.
     If it is suported, it is possible to  enumerate all implementations that
     support the service specified with the argument of
-    <member scope="com::sun::star::container">XContentEnumerationAccess::createContentEnumeration</member>.
+    com::sun::star::container::XContentEnumerationAccess::createContentEnumeration().
     The enumerator returns interfaces. The type of the interface is not specified.
     Commonly this is XSingleComponentFactory.</p>
 */
diff --git a/udkapi/com/sun/star/lang/ServiceManager.idl b/udkapi/com/sun/star/lang/ServiceManager.idl
index bc801257df87..24f3559adf46 100644
--- a/udkapi/com/sun/star/lang/ServiceManager.idl
+++ b/udkapi/com/sun/star/lang/ServiceManager.idl
@@ -60,7 +60,7 @@ module com {  module sun {  module star {  module lang {
 
     <dt>XComponent (optional)</dt>
     <dd>The service manager calls the method
-    <member scope="com::sun::star::lang">XComponent::dispose</member>
+    com::sun::star::lang::XComponent::dispose()
     on the factory when going down (i.e. it is commonly disposed by the component context).</dd>
     </dl>
 
@@ -103,7 +103,7 @@ published service ServiceManager
         <p>
         It is possible to enumerate all implementations that support the
         service specified with the argument of the
-        <member scope="com::sun::star::container">XContentEnumerationAccess::createContentEnumeration</member> method.
+        com::sun::star::container::XContentEnumerationAccess::createContentEnumeration() method.
         The enumerator commonly returns XSingleComponentFactory
         interfaces.
         </p>
diff --git a/udkapi/com/sun/star/lang/XComponent.idl b/udkapi/com/sun/star/lang/XComponent.idl
index 31c7549b4b1a..7423937bb360 100644
--- a/udkapi/com/sun/star/lang/XComponent.idl
+++ b/udkapi/com/sun/star/lang/XComponent.idl
@@ -85,7 +85,7 @@ published interface XComponent: com::sun::star::uno::XInterface
         XComponent::addEventListener</member> is called, the call will not fail
         with a com::sun::star::lang::DisposedException, but
         the caller will be notified via the
-        <member scope="com::sun::star::lang">XEventListener::disposing</member>
+        com::sun::star::lang::XEventListener::disposing()
         callback.  This callback can occur synchronously within the
         <member scope="com::sun::star::lang">XComponent::addEventListener
         </member> call.</p>
diff --git a/udkapi/com/sun/star/lang/XConnectionPoint.idl b/udkapi/com/sun/star/lang/XConnectionPoint.idl
index cb052e45a24d..8848371130d8 100644
--- a/udkapi/com/sun/star/lang/XConnectionPoint.idl
+++ b/udkapi/com/sun/star/lang/XConnectionPoint.idl
@@ -118,7 +118,7 @@ published interface XConnectionPoint: com::sun::star::uno::XInterface
 
         <p>A few <code>add...Listener</code> methods need additional parameters
         to add listeners or throw exceptions. One of these methods is
-        <member scope="com::sun::star::beans">XPropertySet::addPropertyChangeListener</member>.
+        com::sun::star::beans::XPropertySet::addPropertyChangeListener().
         We ignore the problem in this interface. A solution must be provided
         in an additional XConnectionPoint interface.  </p>
 
@@ -143,7 +143,7 @@ published interface XConnectionPoint: com::sun::star::uno::XInterface
 
         <p>A few <code>remove...Listener</code> methods need additional
         parameters to add listeners or throw exceptions. One of these methods
-        is <member scope="com::sun::star::beans">XPropertySet::removePropertyChangeListener</member>.
+        is com::sun::star::beans::XPropertySet::removePropertyChangeListener().
         We ignore the problem in this interface. A solution must be
         provided in an additional XConnectionPoint interface.  </p>
 
diff --git a/udkapi/com/sun/star/uri/UriSchemeParser_vndDOTsunDOTstarDOTexpand.idl b/udkapi/com/sun/star/uri/UriSchemeParser_vndDOTsunDOTstarDOTexpand.idl
index aee75e8f1b77..ac9e4425cbbb 100644
--- a/udkapi/com/sun/star/uri/UriSchemeParser_vndDOTsunDOTstarDOTexpand.idl
+++ b/udkapi/com/sun/star/uri/UriSchemeParser_vndDOTsunDOTstarDOTexpand.idl
@@ -29,10 +29,10 @@ published interface XUriSchemeParser;
    URLs.
 
    <p>The argument <code>scheme</code> of method
-   <member scope="com::sun::star::uri">XUriSchemeParser::parse</member> must
+   com::sun::star::uri::XUriSchemeParser::parse() must
    always be equal to the <atom>string</atom>
    <code>"vnd.sun.star.expand"</code>, ignoring case.  The objects returned by
-   <member scope="com::sun::star::uri">XUriSchemeParser::parse</member>
+   com::sun::star::uri::XUriSchemeParser::parse()
    implement
    com::sun::star::uri::XVndSunStarExpandUrlReference.</p>
 
diff --git a/udkapi/com/sun/star/uri/UriSchemeParser_vndDOTsunDOTstarDOTscript.idl b/udkapi/com/sun/star/uri/UriSchemeParser_vndDOTsunDOTstarDOTscript.idl
index 4a70406083c9..e23b584ec445 100644
--- a/udkapi/com/sun/star/uri/UriSchemeParser_vndDOTsunDOTstarDOTscript.idl
+++ b/udkapi/com/sun/star/uri/UriSchemeParser_vndDOTsunDOTstarDOTscript.idl
@@ -29,10 +29,10 @@ published interface XUriSchemeParser;
    URLs.
 
    <p>The argument <code>scheme</code> of method
-   <member scope="com::sun::star::uri">XUriSchemeParser::parse</member> must
+   com::sun::star::uri::XUriSchemeParser::parse() must
    always be equal to the <atom>string</atom>
    <code>"vnd.sun.star.script"</code>, ignoring case.  The objects returned by
-   <member scope="com::sun::star::uri">XUriSchemeParser::parse</member>
+   com::sun::star::uri::XUriSchemeParser::parse()
    implement
    com::sun::star::uri::XVndSunStarScriptUrlReference.</p>