Removed the old tmpl files
authorMikael Hallendal <micke@imendio.com>
Sat, 21 Jun 2008 16:49:33 +0200
changeset 418 a8af09193258
parent 417 364c17252e5f
child 419 d865cbe1309d
Removed the old tmpl files
docs/reference/tmpl/lm-connection.sgml
docs/reference/tmpl/lm-error.sgml
docs/reference/tmpl/lm-message-handler.sgml
docs/reference/tmpl/lm-message-node.sgml
docs/reference/tmpl/lm-message.sgml
docs/reference/tmpl/lm-proxy.sgml
docs/reference/tmpl/lm-result.sgml
docs/reference/tmpl/lm-ssl.sgml
docs/reference/tmpl/lm-utils.sgml
docs/reference/tmpl/loudmouth-unused.sgml
--- a/docs/reference/tmpl/lm-connection.sgml	Sat Jun 21 13:19:21 2008 +0200
+++ /dev/null	Thu Jan 01 00:00:00 1970 +0000
@@ -1,458 +0,0 @@
-<!-- ##### SECTION Title ##### -->
-LmConnection
-
-<!-- ##### SECTION Short_Description ##### -->
-A client connection to the server
-
-<!-- ##### SECTION Long_Description ##### -->
-<para>
-An example of how to use Loudmouth with the synchronous API.
-<informalexample><programlisting>
-int
-main (int argc, char **argv)
-{
-        LmConnection *connection;
-        GError       *error = NULL;
-        gint          i;
-	LmMessage    *m;
-
-        connection = lm_connection_new ("myserver");
-
-        if (!lm_connection_open_and_block (connection, &amp;error)) {
-                g_error ("Failed to open: &percnt;s\n", error->message);
-        }
-
-	if (!lm_connection_authenticate_and_block (connection,
-						   "username", "password", 
-						   "resource",
-						   &amp;error)) {
-		g_error ("Failed to authenticate: &percnt;s\n", error->message);
-	}
-	
-	m = lm_message_new ("recipient", LM_MESSAGE_TYPE_MESSAGE);
-	lm_message_node_add_child (m->node, "body", "message");
-	
-	if (!lm_connection_send (connection, m, &amp;error)) {
-		g_error ("Send failed: &percnt;s\n", error->message);
-	}
-
-	lm_message_unref (m);
-
-	lm_connection_close (connection, NULL);
-	lm_connection_unref (connection);
-	
-        return 0;
-}
-</programlisting></informalexample>
-</para>
-
-<!-- ##### SECTION See_Also ##### -->
-<para>
-
-</para>
-
-<!-- ##### SECTION Stability_Level ##### -->
-
-
-<!-- ##### MACRO LM_CONNECTION ##### -->
-<para>
-Convenience macro used to cast a pointer to a #LmConnection.
-</para>
-
-@o: pointer to cast
-
-
-<!-- ##### MACRO LM_CONNECTION_DEFAULT_PORT ##### -->
-<para>
-Default jabber client port.
-</para>
-
-
-
-<!-- ##### MACRO LM_CONNECTION_DEFAULT_PORT_SSL ##### -->
-<para>
-Default jabber client port when using SSL encryption.
-</para>
-
-
-
-<!-- ##### STRUCT LmConnection ##### -->
-<para>
-This should not be accessed directly. Use the accessor functions as described below.
-</para>
-
-
-<!-- ##### ENUM LmHandlerResult ##### -->
-<para>
-The return type of an LmMessageHandler. This determines whether more message handlers should be called.
-</para>
-
-@LM_HANDLER_RESULT_REMOVE_MESSAGE: Stop calling message handlers. The message handler returning this declares the message has been handled and should be removed.
-@LM_HANDLER_RESULT_ALLOW_MORE_HANDLERS: Return to continue the calling handlers from the handler list. This declares that another handlers should handle the message.
-
-<!-- ##### ENUM LmHandlerPriority ##### -->
-<para>
-Since the handlers decide whether to stop the calling chain with there return values it's sometimes decirable to be able to set priority. For example a handler that only logs all incoming messages and then pass the message on to another handler wants to have priority %LM_HANDLER_PRIORITY_FIRST. An handler that should take all messages that wasn't handled by anything else would want to have priority %LM_HANDLER_PRIORITY_LAST. If several handlers have the same priority nothing can be said about the order the handlers will be called in.
-</para>
-
-@LM_HANDLER_PRIORITY_LAST: Call the handler after all handlers with #NORMAL and #FIRST priority.
-@LM_HANDLER_PRIORITY_NORMAL: Called before handlers with priority #LAST and after those with #FIRST.
-@LM_HANDLER_PRIORITY_FIRST: These are called before all other handlers.
-
-<!-- ##### ENUM LmDisconnectReason ##### -->
-<para>
-Sent with #LmDisconnectFunction to describe why a connection was closed.
-</para>
-
-@LM_DISCONNECT_REASON_OK: 
-@LM_DISCONNECT_REASON_PING_TIME_OUT: Connection to the server timed out.
-@LM_DISCONNECT_REASON_HUP: The socket emitted that the connection was hung up.
-@LM_DISCONNECT_REASON_ERROR: A generic error somewhere in the transport layer.
-@LM_DISCONNECT_REASON_RESOURCE_CONFLICT: 
-@LM_DISCONNECT_REASON_INVALID_XML: 
-@LM_DISCONNECT_REASON_UNKNOWN: An unknown error.
-
-<!-- ##### ENUM LmConnectionState ##### -->
-<para>
-Describes the current state of an #LmConnection.
-</para>
-
-@LM_CONNECTION_STATE_CLOSED: The connection is closed.
-@LM_CONNECTION_STATE_OPENING: The connection is in the process of opening.
-@LM_CONNECTION_STATE_OPEN: The connection is open.
-@LM_CONNECTION_STATE_AUTHENTICATING: The connection is in the process of authenticating.
-@LM_CONNECTION_STATE_AUTHENTICATED: The connection is authenticated and is ready to start sending/receiving messages.
-
-<!-- ##### USER_FUNCTION LmResultFunction ##### -->
-<para>
-Callback for informing if an asynchronous operation was successful.
-</para>
-
-@connection: an #LmConnection
-@success: the result, %TRUE if operation succeeded, otherwise %FALSE
-@user_data: User data passed when function being called.
-
-
-<!-- ##### USER_FUNCTION LmDisconnectFunction ##### -->
-<para>
-Callback called when a connection is closed.
-</para>
-
-@connection: an #LmConnection
-@reason: the reason the connection was closed.
-@user_data: User data passed when function being called.
-
-
-<!-- ##### FUNCTION lm_connection_new ##### -->
-<para>
-
-</para>
-
-@server: 
-@Returns: 
-
-
-<!-- ##### FUNCTION lm_connection_new_with_context ##### -->
-<para>
-
-</para>
-
-@server: 
-@context: 
-@Returns: 
-
-
-<!-- ##### FUNCTION lm_connection_open ##### -->
-<para>
-
-</para>
-
-@connection: 
-@function: 
-@user_data: 
-@notify: 
-@error: 
-@Returns: 
-
-
-<!-- ##### FUNCTION lm_connection_open_and_block ##### -->
-<para>
-
-</para>
-
-@connection: 
-@error: 
-@Returns: 
-
-
-<!-- ##### FUNCTION lm_connection_close ##### -->
-<para>
-
-</para>
-
-@connection: 
-@error: 
-@Returns: 
-
-
-<!-- ##### FUNCTION lm_connection_authenticate ##### -->
-<para>
-
-</para>
-
-@connection: 
-@username: 
-@password: 
-@resource: 
-@function: 
-@user_data: 
-@notify: 
-@error: 
-@Returns: 
-
-
-<!-- ##### FUNCTION lm_connection_authenticate_and_block ##### -->
-<para>
-
-</para>
-
-@connection: 
-@username: 
-@password: 
-@resource: 
-@error: 
-@Returns: 
-
-
-<!-- ##### FUNCTION lm_connection_get_keep_alive_rate ##### -->
-<para>
-
-</para>
-
-@connection: 
-@Returns: 
-
-
-<!-- ##### FUNCTION lm_connection_set_keep_alive_rate ##### -->
-<para>
-
-</para>
-
-@connection: 
-@rate: 
-
-
-<!-- ##### FUNCTION lm_connection_is_open ##### -->
-<para>
-
-</para>
-
-@connection: 
-@Returns: 
-
-
-<!-- ##### FUNCTION lm_connection_is_authenticated ##### -->
-<para>
-
-</para>
-
-@connection: 
-@Returns: 
-
-
-<!-- ##### FUNCTION lm_connection_get_server ##### -->
-<para>
-
-</para>
-
-@connection: 
-@Returns: 
-
-
-<!-- ##### FUNCTION lm_connection_set_server ##### -->
-<para>
-
-</para>
-
-@connection: 
-@server: 
-
-
-<!-- ##### FUNCTION lm_connection_get_jid ##### -->
-<para>
-
-</para>
-
-@connection: 
-@Returns: 
-
-
-<!-- ##### FUNCTION lm_connection_set_jid ##### -->
-<para>
-
-</para>
-
-@connection: 
-@jid: 
-
-
-<!-- ##### FUNCTION lm_connection_get_port ##### -->
-<para>
-
-</para>
-
-@connection: 
-@Returns: 
-
-
-<!-- ##### FUNCTION lm_connection_set_port ##### -->
-<para>
-
-</para>
-
-@connection: 
-@port: 
-
-
-<!-- ##### FUNCTION lm_connection_get_ssl ##### -->
-<para>
-
-</para>
-
-@connection: 
-@Returns: 
-
-
-<!-- ##### FUNCTION lm_connection_set_ssl ##### -->
-<para>
-
-</para>
-
-@connection: 
-@ssl: 
-
-
-<!-- ##### FUNCTION lm_connection_get_proxy ##### -->
-<para>
-
-</para>
-
-@connection: 
-@Returns: 
-
-
-<!-- ##### FUNCTION lm_connection_set_proxy ##### -->
-<para>
-
-</para>
-
-@connection: 
-@proxy: 
-
-
-<!-- ##### FUNCTION lm_connection_send ##### -->
-<para>
-
-</para>
-
-@connection: 
-@message: 
-@error: 
-@Returns: 
-
-
-<!-- ##### FUNCTION lm_connection_send_with_reply ##### -->
-<para>
-
-</para>
-
-@connection: 
-@message: 
-@handler: 
-@error: 
-@Returns: 
-
-
-<!-- ##### FUNCTION lm_connection_send_with_reply_and_block ##### -->
-<para>
-
-</para>
-
-@connection: 
-@message: 
-@error: 
-@Returns: 
-
-
-<!-- ##### FUNCTION lm_connection_register_message_handler ##### -->
-<para>
-
-</para>
-
-@connection: 
-@handler: 
-@type: 
-@priority: 
-
-
-<!-- ##### FUNCTION lm_connection_unregister_message_handler ##### -->
-<para>
-
-</para>
-
-@connection: 
-@handler: 
-@type: 
-
-
-<!-- ##### FUNCTION lm_connection_set_disconnect_function ##### -->
-<para>
-
-</para>
-
-@connection: 
-@function: 
-@user_data: 
-@notify: 
-
-
-<!-- ##### FUNCTION lm_connection_send_raw ##### -->
-<para>
-
-</para>
-
-@connection: 
-@str: 
-@error: 
-@Returns: 
-
-
-<!-- ##### FUNCTION lm_connection_get_state ##### -->
-<para>
-
-</para>
-
-@connection: 
-@Returns: 
-
-
-<!-- ##### FUNCTION lm_connection_ref ##### -->
-<para>
-
-</para>
-
-@connection: 
-@Returns: 
-
-
-<!-- ##### FUNCTION lm_connection_unref ##### -->
-<para>
-
-</para>
-
-@connection: 
-
-
-y<
-
-
--- a/docs/reference/tmpl/lm-error.sgml	Sat Jun 21 13:19:21 2008 +0200
+++ /dev/null	Thu Jan 01 00:00:00 1970 +0000
@@ -1,45 +0,0 @@
-<!-- ##### SECTION Title ##### -->
-LmError
-
-<!-- ##### SECTION Short_Description ##### -->
-Error reporting.
-
-<!-- ##### SECTION Long_Description ##### -->
-<para>
-
-</para>
-
-<!-- ##### SECTION See_Also ##### -->
-<para>
-
-</para>
-
-<!-- ##### SECTION Stability_Level ##### -->
-
-
-<!-- ##### FUNCTION lm_error_quark ##### -->
-<para>
--
-</para>
-
-@Returns: 
-
-
-<!-- ##### ENUM LmError ##### -->
-<para>
-Describes the problem of the error.
-</para>
-
-@LM_ERROR_CONNECTION_NOT_OPEN: Connection not open when trying to send a message
-@LM_ERROR_CONNECTION_OPEN: Connection is already open when trying to open it again.
-@LM_ERROR_AUTH_FAILED: Authentication failed while opening connection
-@LM_ERROR_CONNECTION_FAILED: 
-
-<!-- ##### MACRO LM_ERROR ##### -->
-<para>
-Macro for getting the error quark.
-
-</para>
-
-
-
--- a/docs/reference/tmpl/lm-message-handler.sgml	Sat Jun 21 13:19:21 2008 +0200
+++ /dev/null	Thu Jan 01 00:00:00 1970 +0000
@@ -1,76 +0,0 @@
-<!-- ##### SECTION Title ##### -->
-LmMessageHandler
-
-<!-- ##### SECTION Short_Description ##### -->
-A handler for incoming messages.
-
-<!-- ##### SECTION Long_Description ##### -->
-<para>
- A handler can be registered to listen to incoming messages with lm_connection_register_message_handler(). When a message is recieved the handlers of the correct type will be called.
-</para>
-
-<!-- ##### SECTION See_Also ##### -->
-<para>
-
-</para>
-
-<!-- ##### SECTION Stability_Level ##### -->
-
-
-<!-- ##### USER_FUNCTION LmHandleMessageFunction ##### -->
-<para>
-The actual callback function in an #LmMessageHandler. This function is called when an incoming message arrives that haven't been handled by an handler with higher priority.
-</para>
-
-@handler: an #LmMessageHandler
-@connection: an #LmConnection
-@message: an #LmMessage
-@user_data: user data set when creating the handler
-@Returns: #LM_HANDLER_RESULT_REMOVE_MESSAGE to indicate that message has been handled, otherwise #LM_HANDLER_RESULT_ALLOW_MORE_HANDLERS.
-
-
-<!-- ##### FUNCTION lm_message_handler_new ##### -->
-<para>
-
-</para>
-
-@function: 
-@user_data: 
-@notify: 
-@Returns: 
-
-
-<!-- ##### FUNCTION lm_message_handler_invalidate ##### -->
-<para>
-
-</para>
-
-@handler: 
-
-
-<!-- ##### FUNCTION lm_message_handler_is_valid ##### -->
-<para>
-
-</para>
-
-@handler: 
-@Returns: 
-
-
-<!-- ##### FUNCTION lm_message_handler_ref ##### -->
-<para>
-
-</para>
-
-@handler: 
-@Returns: 
-
-
-<!-- ##### FUNCTION lm_message_handler_unref ##### -->
-<para>
-
-</para>
-
-@handler: 
-
-
--- a/docs/reference/tmpl/lm-message-node.sgml	Sat Jun 21 13:19:21 2008 +0200
+++ /dev/null	Thu Jan 01 00:00:00 1970 +0000
@@ -1,155 +0,0 @@
-<!-- ##### SECTION Title ##### -->
-LmMessageNode
-
-<!-- ##### SECTION Short_Description ##### -->
-A node in the message tree
-
-<!-- ##### SECTION Long_Description ##### -->
-<para>
-
-</para>
-
-<!-- ##### SECTION See_Also ##### -->
-<para>
-
-</para>
-
-<!-- ##### SECTION Stability_Level ##### -->
-
-
-<!-- ##### STRUCT LmMessageNode ##### -->
-<para>
-A struct representing a node in a message. 
-</para>
-
-@name: the name of the node
-@value: value of the node, can be NULL
-@raw_mode: if true, don't escape the content of the message. The content must be valid XML.
-@next: next sibling
-@prev: previous sibling
-@parent: node parent
-@children: pointing to first child
-
-<!-- ##### FUNCTION lm_message_node_get_value ##### -->
-<para>
-
-</para>
-
-@node: 
-@Returns: 
-
-
-<!-- ##### FUNCTION lm_message_node_set_value ##### -->
-<para>
-
-</para>
-
-@node: 
-@value: 
-
-
-<!-- ##### FUNCTION lm_message_node_add_child ##### -->
-<para>
-
-</para>
-
-@node: 
-@name: 
-@value: 
-@Returns: 
-
-
-<!-- ##### FUNCTION lm_message_node_set_attributes ##### -->
-<para>
-
-</para>
-
-@node: 
-@name: 
-@Varargs: 
-
-
-<!-- ##### FUNCTION lm_message_node_get_attribute ##### -->
-<para>
-
-</para>
-
-@node: 
-@name: 
-@Returns: 
-
-
-<!-- ##### FUNCTION lm_message_node_set_attribute ##### -->
-<para>
-
-</para>
-
-@node: 
-@name: 
-@value: 
-
-
-<!-- ##### FUNCTION lm_message_node_get_child ##### -->
-<para>
-
-</para>
-
-@node: 
-@child_name: 
-@Returns: 
-
-
-<!-- ##### FUNCTION lm_message_node_find_child ##### -->
-<para>
-
-</para>
-
-@node: 
-@child_name: 
-@Returns: 
-
-
-<!-- ##### FUNCTION lm_message_node_get_raw_mode ##### -->
-<para>
-
-</para>
-
-@node: 
-@Returns: 
-
-
-<!-- ##### FUNCTION lm_message_node_set_raw_mode ##### -->
-<para>
-
-</para>
-
-@node: 
-@raw_mode: 
-
-
-<!-- ##### FUNCTION lm_message_node_ref ##### -->
-<para>
-
-</para>
-
-@node: 
-@Returns: 
-
-
-<!-- ##### FUNCTION lm_message_node_unref ##### -->
-<para>
-
-</para>
-
-@node: 
-
-
-<!-- ##### FUNCTION lm_message_node_to_string ##### -->
-<para>
-
-</para>
-
-@node: 
-@Returns: 
-
-
--- a/docs/reference/tmpl/lm-message.sgml	Sat Jun 21 13:19:21 2008 +0200
+++ /dev/null	Thu Jan 01 00:00:00 1970 +0000
@@ -1,135 +0,0 @@
-<!-- ##### SECTION Title ##### -->
-LmMessage
-
-<!-- ##### SECTION Short_Description ##### -->
-A message is built up like a tree of message nodes.
-
-<!-- ##### SECTION Long_Description ##### -->
-<para>
-Represents a message that can be sent with lm_connection_send(), lm_connection_send_with_reply() or lm_connection_send_with_reply_and_block(). Either use lm_message_new() or lm_message_new_with_subtype() to create a message. You need to call lm_message_unref() when are finished with it.
-
-</para>
-
-<!-- ##### SECTION See_Also ##### -->
-<para>
-
-</para>
-
-<!-- ##### SECTION Stability_Level ##### -->
-
-
-<!-- ##### STRUCT LmMessage ##### -->
-<para>
-Struct 
-</para>
-
-@node: 
-@priv: 
-
-<!-- ##### ENUM LmMessageType ##### -->
-<para>
-Describes what type of message a message is. This maps directly to top level elements in the jabber protocol.
-</para>
-
-@LM_MESSAGE_TYPE_MESSAGE: a message, <message/>
-@LM_MESSAGE_TYPE_PRESENCE: a presence element, <presence/>
-@LM_MESSAGE_TYPE_IQ: an info/query element, <iq/>
-@LM_MESSAGE_TYPE_STREAM: the stream:stream element, you probably don't need to create a message of this type.
-@LM_MESSAGE_TYPE_STREAM_ERROR: a stream:error element
-@LM_MESSAGE_TYPE_STREAM_FEATURES: 
-@LM_MESSAGE_TYPE_AUTH: 
-@LM_MESSAGE_TYPE_CHALLENGE: 
-@LM_MESSAGE_TYPE_RESPONSE: 
-@LM_MESSAGE_TYPE_SUCCESS: 
-@LM_MESSAGE_TYPE_FAILURE: 
-@LM_MESSAGE_TYPE_PROCEED: 
-@LM_MESSAGE_TYPE_STARTTLS: 
-@LM_MESSAGE_TYPE_UNKNOWN: incoming message is of some unknown type.
-
-<!-- ##### ENUM LmMessageSubType ##### -->
-<para>
-Describes the sub type of a message. This is equal to the "type" attribute in the jabber protocol. What sub type a message can have is depending on the type of the message.
-</para>
-
-@LM_MESSAGE_SUB_TYPE_NOT_SET: the default. No "type" attribute will be sent.
-@LM_MESSAGE_SUB_TYPE_AVAILABLE: presence is available, applies to message type "presence"
-@LM_MESSAGE_SUB_TYPE_NORMAL: 
-@LM_MESSAGE_SUB_TYPE_CHAT: message is a chat message, applies to message type "message"
-@LM_MESSAGE_SUB_TYPE_GROUPCHAT: message is a group chat message, applies to message type "message"
-@LM_MESSAGE_SUB_TYPE_HEADLINE: message is a headline message, applies to message type "message"
-@LM_MESSAGE_SUB_TYPE_UNAVAILABLE: presence is unavailable, applies to message type "presence"
-@LM_MESSAGE_SUB_TYPE_PROBE: a probe presence, applies to message type "presence"
-@LM_MESSAGE_SUB_TYPE_SUBSCRIBE: try to subscribe to another jids presence, applies to message type "presence"
-@LM_MESSAGE_SUB_TYPE_UNSUBSCRIBE: unsubscribes from another jids presence, applies to message type "presence"
-@LM_MESSAGE_SUB_TYPE_SUBSCRIBED: reply from a subscribe message, informs that the subscription was successful. Applies to message type "presence"
-@LM_MESSAGE_SUB_TYPE_UNSUBSCRIBED: reply from subscribe or unsubscribe message. If it's a reply from a subscribe message it notifies that the subscription failed. Applies to message type "presence"
-@LM_MESSAGE_SUB_TYPE_GET: used to get information from an IQ query, applies to message type "iq"
-@LM_MESSAGE_SUB_TYPE_SET: used to set information in a IQ call, applised to message type "iq"
-@LM_MESSAGE_SUB_TYPE_RESULT: message is an IQ reply, applies to message type "iq"
-@LM_MESSAGE_SUB_TYPE_ERROR: messages is an error, applies to all message types.
-
-<!-- ##### FUNCTION lm_message_new ##### -->
-<para>
-
-</para>
-
-@to: 
-@type: 
-@Returns: 
-
-
-<!-- ##### FUNCTION lm_message_new_with_sub_type ##### -->
-<para>
-
-</para>
-
-@to: 
-@type: 
-@sub_type: 
-@Returns: 
-
-
-<!-- ##### FUNCTION lm_message_get_type ##### -->
-<para>
-
-</para>
-
-@message: 
-@Returns: 
-
-
-<!-- ##### FUNCTION lm_message_get_sub_type ##### -->
-<para>
-
-</para>
-
-@message: 
-@Returns: 
-
-
-<!-- ##### FUNCTION lm_message_get_node ##### -->
-<para>
-
-</para>
-
-@message: 
-@Returns: 
-
-
-<!-- ##### FUNCTION lm_message_ref ##### -->
-<para>
-
-</para>
-
-@message: 
-@Returns: 
-
-
-<!-- ##### FUNCTION lm_message_unref ##### -->
-<para>
-
-</para>
-
-@message: 
-
-
--- a/docs/reference/tmpl/lm-proxy.sgml	Sat Jun 21 13:19:21 2008 +0200
+++ /dev/null	Thu Jan 01 00:00:00 1970 +0000
@@ -1,170 +0,0 @@
-<!-- ##### SECTION Title ##### -->
-LmProxy
-
-<!-- ##### SECTION Short_Description ##### -->
-API for the proxy support in Loudmouth
-
-<!-- ##### SECTION Long_Description ##### -->
-<para>
-Use this together with an #LmConnection to get the connection to use connect through a proxy. Example of how to use the #LmProxy API.
-<informalexample><programlisting><![CDATA[
-LmConnection *connection;
-LmProxy      *proxy;
-
-connection = lm_connection_new ("myserver");
-proxy = lm_proxy_new_with_server (LM_PROXY_TYPE_HTTP,
-				  "myproxyserver",
-				  8080);
-lm_connection_set_proxy (connection, proxy);
-...]]></programlisting></informalexample>
-</para>
-
-<!-- ##### SECTION See_Also ##### -->
-<para>
-
-</para>
-
-<!-- ##### SECTION Stability_Level ##### -->
-
-
-<!-- ##### STRUCT LmProxy ##### -->
-<para>
-This should not be accessed directly. Use the accessor functions as described below.
-</para>
-
-
-<!-- ##### ENUM LmProxyType ##### -->
-<para>
-The type of the proxy.
-</para>
-
-@LM_PROXY_TYPE_NONE: Unused
-@LM_PROXY_TYPE_HTTP: An HTTP proxy.
-
-<!-- ##### FUNCTION lm_proxy_new ##### -->
-<para>
-
-</para>
-
-@type: 
-@Returns: 
-
-
-<!-- ##### FUNCTION lm_proxy_new_with_server ##### -->
-<para>
-
-</para>
-
-@type: 
-@server: 
-@port: 
-@Returns: 
-
-
-<!-- ##### FUNCTION lm_proxy_get_type ##### -->
-<para>
-
-</para>
-
-@proxy: 
-@Returns: 
-
-
-<!-- ##### FUNCTION lm_proxy_set_type ##### -->
-<para>
-
-</para>
-
-@proxy: 
-@type: 
-
-
-<!-- ##### FUNCTION lm_proxy_get_server ##### -->
-<para>
-
-</para>
-
-@proxy: 
-@Returns: 
-
-
-<!-- ##### FUNCTION lm_proxy_set_server ##### -->
-<para>
-
-</para>
-
-@proxy: 
-@server: 
-
-
-<!-- ##### FUNCTION lm_proxy_get_port ##### -->
-<para>
-
-</para>
-
-@proxy: 
-@Returns: 
-
-
-<!-- ##### FUNCTION lm_proxy_set_port ##### -->
-<para>
-
-</para>
-
-@proxy: 
-@port: 
-
-
-<!-- ##### FUNCTION lm_proxy_get_username ##### -->
-<para>
-
-</para>
-
-@proxy: 
-@Returns: 
-
-
-<!-- ##### FUNCTION lm_proxy_set_username ##### -->
-<para>
-
-</para>
-
-@proxy: 
-@username: 
-
-
-<!-- ##### FUNCTION lm_proxy_get_password ##### -->
-<para>
-
-</para>
-
-@proxy: 
-@Returns: 
-
-
-<!-- ##### FUNCTION lm_proxy_set_password ##### -->
-<para>
-
-</para>
-
-@proxy: 
-@password: 
-
-
-<!-- ##### FUNCTION lm_proxy_ref ##### -->
-<para>
-
-</para>
-
-@proxy: 
-@Returns: 
-
-
-<!-- ##### FUNCTION lm_proxy_unref ##### -->
-<para>
-
-</para>
-
-@proxy: 
-
-
--- a/docs/reference/tmpl/lm-result.sgml	Sat Jun 21 13:19:21 2008 +0200
+++ /dev/null	Thu Jan 01 00:00:00 1970 +0000
@@ -1,18 +0,0 @@
-<!-- ##### SECTION Title ##### -->
-lm-result
-
-<!-- ##### SECTION Short_Description ##### -->
-
-
-<!-- ##### SECTION Long_Description ##### -->
-<para>
-
-</para>
-
-
-<!-- ##### SECTION See_Also ##### -->
-<para>
-
-</para>
-
-
--- a/docs/reference/tmpl/lm-ssl.sgml	Sat Jun 21 13:19:21 2008 +0200
+++ /dev/null	Thu Jan 01 00:00:00 1970 +0000
@@ -1,121 +0,0 @@
-<!-- ##### SECTION Title ##### -->
-LmSSL
-
-<!-- ##### SECTION Short_Description ##### -->
-SSL struct for SSL support in Loudmouth
-
-<!-- ##### SECTION Long_Description ##### -->
-<para>
-Use this together with an #LmConnection to get the connection to use SSL. Example of how to use the #LmSSL API.
-</para>
-<informalexample><programlisting><![CDATA[
-LmConnection *connection;
-LmSSL        *ssl;
-
-connection = lm_connection_new ("myserver");
-ssl = lm_ssl_new (NULL, my_ssl_func, NULL, NULL);
-lm_connection_set_ssl (connection, ssl);
-...
-]]></programlisting></informalexample>
-
-<!-- ##### SECTION See_Also ##### -->
-<para>
-
-</para>
-
-<!-- ##### SECTION Stability_Level ##### -->
-
-
-<!-- ##### STRUCT LmSSL ##### -->
-<para>
-This should not be accessed directly. Use the accessor functions as described below.
-</para>
-
-
-<!-- ##### ENUM LmCertificateStatus ##### -->
-<para>
-Provides information of the status of a certain certificate.
-</para>
-
-@LM_CERT_INVALID: The certificate is invalid.
-@LM_CERT_ISSUER_NOT_FOUND: The issuer of the certificate is not found.
-@LM_CERT_REVOKED: The certificate has been revoked.
-
-<!-- ##### ENUM LmSSLStatus ##### -->
-<para>
-Provides information about something gone wrong when trying to setup the SSL connection.
-</para>
-
-@LM_SSL_STATUS_NO_CERT_FOUND: The server doesn't provide a certificate.
-@LM_SSL_STATUS_UNTRUSTED_CERT: The certification can not be trusted.
-@LM_SSL_STATUS_CERT_EXPIRED: The certificate has expired.
-@LM_SSL_STATUS_CERT_NOT_ACTIVATED: The certificate has not been activated.
-@LM_SSL_STATUS_CERT_HOSTNAME_MISMATCH: The server hostname doesn't match the one in the certificate.
-@LM_SSL_STATUS_CERT_FINGERPRINT_MISMATCH: The fingerprint doesn't match your expected.
-@LM_SSL_STATUS_GENERIC_ERROR: Some other error.
-
-<!-- ##### ENUM LmSSLResponse ##### -->
-<para>
-Used to inform #LmConnection if you want to stop due to an error reported or if you want to continue to connect.
-</para>
-
-@LM_SSL_RESPONSE_CONTINUE: Continue to connect.
-@LM_SSL_RESPONSE_STOP: Stop the connection.
-
-<!-- ##### USER_FUNCTION LmSSLFunction ##### -->
-<para>
-This function is called if something goes wrong during the connecting phase.
-</para>
-
-@ssl: An #LmSSL.
-@status: The status informing what went wrong.
-@user_data: User data provided in the callback.
-@Returns: User should return #LM_SSL_RESPONSE_CONTINUE if connection should proceed and otherwise #LM_SSL_RESPONSE_STOP.
-
-
-<!-- ##### FUNCTION lm_ssl_new ##### -->
-<para>
-
-</para>
-
-@expected_fingerprint: 
-@ssl_function: 
-@user_data: 
-@notify: 
-@Returns: 
-
-
-<!-- ##### FUNCTION lm_ssl_is_supported ##### -->
-<para>
-
-</para>
-
-@Returns: 
-
-
-<!-- ##### FUNCTION lm_ssl_get_fingerprint ##### -->
-<para>
-
-</para>
-
-@ssl: 
-@Returns: 
-
-
-<!-- ##### FUNCTION lm_ssl_ref ##### -->
-<para>
-
-</para>
-
-@ssl: 
-@Returns: 
-
-
-<!-- ##### FUNCTION lm_ssl_unref ##### -->
-<para>
-
-</para>
-
-@ssl: 
-
-
--- a/docs/reference/tmpl/lm-utils.sgml	Sat Jun 21 13:19:21 2008 +0200
+++ /dev/null	Thu Jan 01 00:00:00 1970 +0000
@@ -1,28 +0,0 @@
-<!-- ##### SECTION Title ##### -->
-Miscellaneous Utility Functions
-
-<!-- ##### SECTION Short_Description ##### -->
-
-
-<!-- ##### SECTION Long_Description ##### -->
-<para>
-Functions to help application developers when writing XMPP applications using Loudmouth.
-</para>
-
-<!-- ##### SECTION See_Also ##### -->
-<para>
-
-</para>
-
-<!-- ##### SECTION Stability_Level ##### -->
-
-
-<!-- ##### FUNCTION lm_utils_get_localtime ##### -->
-<para>
-
-</para>
-
-@stamp: 
-@Returns: 
-
-
--- a/docs/reference/tmpl/loudmouth-unused.sgml	Sat Jun 21 13:19:21 2008 +0200
+++ /dev/null	Thu Jan 01 00:00:00 1970 +0000
@@ -1,93 +0,0 @@
-<!-- ##### SECTION ./tmpl/lm-result.sgml:Long_Description ##### -->
-<para>
-
-</para>
-
-
-<!-- ##### SECTION ./tmpl/lm-result.sgml:See_Also ##### -->
-<para>
-
-</para>
-
-
-<!-- ##### SECTION ./tmpl/lm-result.sgml:Short_Description ##### -->
-
-
-
-<!-- ##### SECTION ./tmpl/lm-result.sgml:Title ##### -->
-lm-result
-
-
-<!-- ##### USER_FUNCTION MessageNodeFunc ##### -->
-<para>
-
-</para>
-
-@attribute: 
-@value: 
-@user_data: 
-
-<!-- ##### FUNCTION lm_connection_get_use_ssl ##### -->
-<para>
-
-</para>
-
-@connection: 
-@Returns: 
-
-<!-- ##### FUNCTION lm_connection_set_use_ssl ##### -->
-<para>
-
-</para>
-
-@connection: 
-@use_ssl: 
-
-<!-- ##### FUNCTION lm_connection_supports_ssl ##### -->
-<para>
-
-</para>
-
-@Returns: 
-
-<!-- ##### FUNCTION lm_message_node_add_child_message_node ##### -->
-<para>
-
-</para>
-
-@message_node: 
-@child: 
-
-<!-- ##### FUNCTION lm_message_node_foreach_attribute ##### -->
-<para>
-
-</para>
-
-@message_node: 
-@func: 
-@user_data: 
-
-<!-- ##### FUNCTION lm_message_node_new ##### -->
-<para>
-
-</para>
-
-@name: 
-@Returns: 
-
-<!-- ##### FUNCTION lm_message_node_set_child_value ##### -->
-<para>
-
-</para>
-
-@message_node: 
-@child_name: 
-@value: 
-
-<!-- ##### FUNCTION lm_message_node_unlink ##### -->
-<para>
-
-</para>
-
-@message_node: 
-