*api: fix a bunch of "illegal" and "empty" tags

Apparently doxygen doesn't like XML-style empty elements.

Change-Id: I0fe8105a196fa3cf5b980f0b6f18933adf8a1d53

offapi/com/sun/star/configuration/backend/CannotConnectException.idl

@@ -35,7 +35,7 @@ module backend {
             <li>Communications link failure.</li>
             <li>Backend is unavailable temporarily or permanently.</li>
             <li>Internal failure of the backend access layer.</li>
-        <ul/>
+        </ul>
     </p>
 
     @since OOo 1.1.2

offapi/com/sun/star/form/PropertyBrowserController.idl

@@ -84,7 +84,7 @@ published service PropertyBrowserController
 
         <p>The aspects of a DataAwareControlModel which can be browsed and modified
         using this controller can be separated into 3 groups: common aspects, data-awareness
-        related aspects, and bound events.</br>
+        related aspects, and bound events.<br>
         The appearance of the visual component created by the controller is that 3 tab pages, one for
         each group, are displayed (of course if the control does not support any aspects of a given group,
         the group is omitted).<br/>

offapi/com/sun/star/form/XResetListener.idl

@@ -31,7 +31,7 @@
 /** is the interface for receiving notifications about reset events.
 
     <p>The listener is called if a component implementing the
-    XReset interface performs a reset.</br>
+    XReset interface performs a reset.<br>
     Order of events:
     <ul><li>a reset is triggered on a component</li>
         <li>the component calls XReset::approveReset() on all its listeners</li>

offapi/com/sun/star/form/binding/BindableDataAwareControlModel.idl

@@ -82,7 +82,7 @@ module com {  module sun {  module star {  module form { module binding {
             <li><b>Cloning</b><br/>
                 com::sun::star::form::FormControlModels support cloning themselves
                 via the com::sun::star::util::XCloneable interface which they
-                inherit from the com::sun::star::awt::UnoControlModel service.</br>
+                inherit from the com::sun::star::awt::UnoControlModel service.<br>
                 When a BindableDataAwareControlModel is cloned while it has an active
                 external value binding, then the clone is also bound to the same binding instance.<br/>
                 Note that this restriction is inherited from the BindableControlModel.

offapi/com/sun/star/form/component/DatabaseImageControl.idl

@@ -34,7 +34,7 @@
 
     <p>As every com::sun::star::form::DataAwareControlModel, an image control
     can be bound to a database field. This means that for instance with every record change, the content
-    of the database field is taken, interpreted as image, and displayed in the control.<br/>
+    of the database field is taken, interpreted as image, and displayed in the control.<br>
     Unlike other more text-based controls, it does not interpret the content of the field as text or double,
     but as binary stream (see com::sun::star::sdb::XColumn::getBinaryStream()).</p>
 
@@ -45,7 +45,7 @@
     com::sun::star::sdbc::DataType::OTHER,
     com::sun::star::sdbc::DataType::LONGVARCHAR</p>
 
-    <p/>
+    </p>
 
     <p>Note that besides taking the image to be displayed from the bound field, there is another option. The
     com::sun::star::awt::UnoControlImageControlModel::ImageURL property specifies
@@ -68,9 +68,9 @@
                 exchanged by URL. For example, implementations of the control service may allow the user
                 to browse for image. After this, the URL of the image is set as
                 com::sun::star::awt::UnoControlImageControlModel::ImageURL
-                property at the model.<br/>
+                property at the model.<br>
                 Now the control loads the image determined by the property value, and starts producing
-                a new data stream, which is displayed by the control (which is a consumer for this stream).<br/>
+                a new data stream, which is displayed by the control (which is a consumer for this stream).<br>
                 From now on, the control and thus the database record counts as modified. If the cursor of the
                 form is moved further, the modified record is saved, means the content of the image pointed to
                 by com::sun::star::awt::UnoControlImageControlModel::ImageURL

offapi/com/sun/star/form/control/ListBox.idl

@@ -50,7 +50,7 @@ published service ListBox
             <li>the control loses the focus</li>
             <li>the content of the control has changed, compared to the moment where it got the focus.</li>
         </ul>
-        <p/>
+        </p>
     */
     interface com::sun::star::form::XChangeBroadcaster;
 };

offapi/com/sun/star/form/control/TextField.idl

@@ -55,7 +55,7 @@ published service TextField
             <li>the control loses the focus</li>
             <li>the content of the control has changed, compared to the moment where it got the focus.</li>
         </ul>
-        <p/>
+        </p>
     */
     interface com::sun::star::form::XChangeBroadcaster;
 };

offapi/com/sun/star/i18n/CalendarDisplayCode.idl

@@ -31,7 +31,7 @@ module com { module sun { module star { module i18n {
     <p> The examples given are for an English Gregorian calendar, note
     that other calendars or locales may return completely different
     strings, for example not a four digit year but a CJK name instead.
-    <p/>
+    </p>
 
      @since OOo 1.1.2
  */

offapi/com/sun/star/i18n/XExtendedCalendar.idl

@@ -50,13 +50,13 @@ published interface XExtendedCalendar : ::com::sun::star::i18n::XCalendar
         how many digits that will have. For example, a short year
         display string will normally be two digits with a Gregorian
         calendar, but with a Jewish calendar it will have three
-        digits. <p/>
+        digits. </p>
 
         @param nCalendarDisplayCode
             One of CalendarDisplayCode
 
         @param nNativeNumberMode
-            One of NativeNumberMode. <br/>
+            One of NativeNumberMode. <br>
             This argument designates the basic transliteration mode as
             if specified for the year representation. However, depending
             on the locale, different conversions for year and month, for

offapi/com/sun/star/i18n/XTransliteration.idl

@@ -35,11 +35,11 @@ module com { module sun { module star { module i18n {
     not always a one to one mapping between characters. Transliteration
     modules are primarily used by collation, and search and replace
     modules to perform approximate search. It can also be used to format
-    the numbers in different numbering systems. <p/>
+    the numbers in different numbering systems. </p>
 
     <p> In order to select transliteration modules for different
     purposes, they are classified with attributes of
-    TransliterationType. <p/>
+    TransliterationType. </p>
 
     <p> For Western languages there would be three transliteration
     modules available to compare two mixed case strings: upper to lower,
@@ -201,11 +201,11 @@ published interface XTransliteration: com::sun::star::uno::XInterface
         TransliterationType IGNORE attribute. </p>
 
         <p> Returns the number of matched code points in any case, even if
-        strings are not equal, for example: <br/>
-        equals( "a", 0, 1, nMatch1, "aaa", 0, 3, nMatch2 ) <br/>
-        returns `FALSE` and nMatch:=1 and nMatch2:=1 <br/>
-        equals( "aab", 0, 3, nMatch1, "aaa", 0, 3, nMatch2 ) <br/>
-        returns `FALSE` and nMatch:=2 and nMatch2:=2 <br/> </p>
+        strings are not equal, for example: <br>
+        equals( "a", 0, 1, nMatch1, "aaa", 0, 3, nMatch2 ) <br>
+        returns `FALSE` and nMatch:=1 and nMatch2:=1 <br>
+        equals( "aab", 0, 3, nMatch1, "aaa", 0, 3, nMatch2 ) <br>
+        returns `FALSE` and nMatch:=2 and nMatch2:=2 <br> </p>
 
         @param aStr1
             First string to match.
@@ -233,7 +233,7 @@ published interface XTransliteration: com::sun::star::uno::XInterface
 
         @returns
             `TRUE` if the substrings are equal per this
-            transliteration <br/>
+            transliteration <br>
             `FALSE` else.
      */
 
@@ -283,8 +283,8 @@ published interface XTransliteration: com::sun::star::uno::XInterface
             Length (from offset) of the second substring.
 
         @returns
-            1 if the first substring is greater than the second substring <br/>
-            0 if the first substring is equal to the second substring <br/>
+            1 if the first substring is greater than the second substring <br>
+            0 if the first substring is equal to the second substring <br>
             -1 if the first substring is less than the second substring
     */
     long    compareSubstring(   [in] string aStr1, [in] long nOff1, [in] long nLen1,
@@ -294,8 +294,8 @@ published interface XTransliteration: com::sun::star::uno::XInterface
         strings before comparing them.
 
         @returns
-            1 if the first string is greater than the second string <br/>
-            0 if the first string is equal to the second string <br/>
+            1 if the first string is greater than the second string <br>
+            0 if the first string is equal to the second string <br>
             -1 if the first string is less than the second string
     */
     long    compareString( [in] string aStr1, [in] string aStr2 );

offapi/com/sun/star/inspection/ObjectInspector.idl

@@ -28,7 +28,7 @@ module com {  module sun {  module star {  module inspection {
     browse and modify properties of components.
 
     <p>The controller can be plugged into an com::sun::star::frame::XFrame, and will
-    provide a visual component for inspecting and modifying component properties.<br/>
+    provide a visual component for inspecting and modifying component properties.<br>
     Note that "property" here is a generic term - any aspect of a component can be considered a property,
     as long as some property handler is able to describe this aspect in a property-like way.</p>
 
@@ -48,11 +48,11 @@ module com {  module sun {  module star {  module inspection {
 
     <p>The property handlers, as well as more information about the layout of the inspector,
     are provided by a inspector model, which has to be implemented by the user of the inspector.</p>
-    <p/>
+    </p>
 
     <p>Since property handlers might have the need to raise UI, they will be created with a context
     value named "DialogParentWindow", which contains an XWindow which should be used as parent of
-    any windows to raise.<br/>
+    any windows to raise.<br>
     If the com::sun::star::uno::XComponentContext in which the ObjectInspector
     was created already contains such a value, it is not overwritten. Only if it doesn't, the inspector
     will add an own value - which contains the inspector's main window - to the context when creating

offapi/com/sun/star/inspection/XObjectInspectorModel.idl

@@ -40,11 +40,11 @@ interface XObjectInspectorModel
         <p>Every element of the sequence must contain information to create a
         XPropertyHandler instance. Two ways are currently supported:
         <ul>
-            <li>A service name:</br>
+            <li>A service name:<br>
                 If a sequence element contains a string, this string is interpreted
                 as service name, and an com::sun::star::lang::XMultiComponentFactory
                 is asked to create an instance of this service.</li>
-            <li>A factory:<br/>
+            <li>A factory:<br>
                 If a sequence element contains an instance implementing the
                 com::sun::star::lang::XSingleComponentFactory interface, this factory
                 is used to create a property handler.</li>
@@ -67,7 +67,7 @@ interface XObjectInspectorModel
 
         <p>Properties can be sorted into different categories, described by the LineDescriptor::Category
         attribute, which is filled in XPropertyHandler::describePropertyLine()
-        method of your property handler.<br/>
+        method of your property handler.<br>
         Those names provided by the handlers are programmatic names. All other information
         about categories is part of the PropertyCategoryDescriptor, and
         describeCategories() assembles information about all categories which
@@ -76,9 +76,9 @@ interface XObjectInspectorModel
         @return
             a sequence of category descriptors. Their relative ordering also describes
             the relative ordering of the categories in the ObjectInspector's
-            user interface.<br/>
-            The sequence must not contain two entries with the same programmatic name.<br/>
-            <br/>
+            user interface.<br>
+            The sequence must not contain two entries with the same programmatic name.<br>
+            <br>
             The model implementation might return an empty sequence here, in this case, the ObjectInspector
             automatically builds its category information from the categories provided by the
             property handlers.
@@ -103,7 +103,7 @@ interface XObjectInspectorModel
         <p>If for two different properties the same order index is returned, the
         ObjectInspector will assume the order in which those properties
         were provided by the respective property handler
-        (XPropertyHandler::getSupportedProperties()).<br/>
+        (XPropertyHandler::getSupportedProperties()).<br>
         If two such properties originate from different handlers, they will be ordered according
         to the order of the handlers, as provided in the #HandlerFactories attribute.</p>
 
@@ -117,7 +117,7 @@ interface XObjectInspectorModel
     /** indicates that the object inspector should have a help section.
 
         <p>The object inspector displays lines of property/values, optionally grouped
-        into categories, as described by the property handlers.<br/>
+        into categories, as described by the property handlers.<br>
         Additionally, the inspector can optionally display a section dedicated to help
         texts. Clients could use this section to display context-sensitive help, for
         instance short texts explaining the currently selected property.</p>

offapi/com/sun/star/table/TableChart.idl

@@ -31,7 +31,7 @@ module com {  module sun {  module star {  module table {
 /** represents a chart based on data in a table or spreadsheet.
 
     <p>This service does not represent the chart document model itself,
-    but the object in the table that contains this chart document.<p/>
+    but the object in the table that contains this chart document.</p>
  */
 published service TableChart
 {

offapi/com/sun/star/table/TableColumn.idl

@@ -49,7 +49,7 @@ published service TableColumn
 
     /** provides methods to access the name of the column.
 
-        <p>In spreadsheets, the name of a column cannot be changed.<p/>
+        <p>In spreadsheets, the name of a column cannot be changed.</p>
      */
     interface com::sun::star::container::XNamed;
 

offapi/com/sun/star/ui/ModuleUIConfigurationManager.idl

@@ -32,13 +32,13 @@ module com { module sun { module star { module ui {
 
     <p>
     A module user interface configuration manager supports two layers of configuration settings
-    data:<br/>
+    data:<br>
     1. Layer: A module default user interface configuration which describe all user interface
     elements settings that are used by OpenOffice. It is not possible to insert, remove or change
-    elements settings in this layer through the interfaces.</br>
+    elements settings in this layer through the interfaces.<br>
     2. Layer: A module user interface configuration which only contains customized user interface
     elements and user-defined ones. All changes on user interface element settings are done on
-    this layer.</br>
+    this layer.
     </p>
 
     @since OOo 2.0

offapi/com/sun/star/ui/XModuleUIConfigurationManager.idl

@@ -34,17 +34,17 @@ module com { module sun { module star { module ui {
     <p>
     A module user interface configuration manager supports, unlike a
     document based ui configuration manager, two layers of configuration
-    settings data:<br/>
+    settings data:<br>
     1. Layer: A module default user interface configuration which
               describe all user interface elements settings that are
               used by OpenOffice. It is not possible to insert, remove
               or change elements settings in this layer through the
-              interfaces.</br>
+              interfaces.<br>
     2. Layer: A module user interface configuration which only contains
               customized user interface elements and user-defined ones.
               All changes on user interface element settings are done on
               this layer. This layer is the same as the document ui
-              configuration manager uses.</br>
+              configuration manager uses.
     </p>
 
     @since OOo 2.0

offapi/com/sun/star/util/URL.idl

@@ -29,7 +29,7 @@ module com {  module sun {  module star {  module util {
     <p>
     If the structure represents a valid URL or not depends on prior usage of
     the functions of XURLTransformer. Only after one of the functions
-    returned `TRUE` this can be assumed.</br>
+    returned `TRUE` this can be assumed.<br>
     It is not necessary to set all of the fields; either URL::Complete
     or (some of) the others are set. Additionally, most of the other
     fields, like URL::Host, URL::Port,

udkapi/com/sun/star/bridge/OleApplicationRegistration.idl

@@ -27,7 +27,8 @@
 
 
 /** registers UNO objects as COM objects.
-    <p />
+
+    <p>
     That is, COM class factories are registered with COM at runtime. The required
     EXE server is the application which deploys this service. In order to access the
     factories by COM API functions, there need to be proper registry entries. This service
@@ -35,10 +36,11 @@
     The instantiation of the registered objects can be carried out by any ordinary mechanism
     which is used in a certain language to create COM components. For example, CreateObject
     in Visual Basic, CoCreateInstance in C++.
-    <p />
+    </p><p>
     Currently only a factory for the service com.sun.star.long.MultiServiceFactory is registered
     by this service. The CLSID is {82154420-0FBF-11d4-8313-005004526AB4} and the ProgId is
     com.sun.star.ServiceManager.
+    </p>
 
     <p>OleApplicationRegistration does not provide any particular interface because the UNO objects
     are registered while instantiating this service and deregistered

udkapi/com/sun/star/bridge/XBridgeSupplier2.idl

@@ -29,7 +29,7 @@
 
 
 /** defines the interface for creating bridges to other object models.
-    <p />
+
     <p>
     The created bridges are transparent to the user. That is, if one maps
     an interface into the target model, then the resulting target interface