summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorlouiz’ <louiz@louiz.org>2016-12-24 16:19:35 +0100
committerlouiz’ <louiz@louiz.org>2016-12-24 16:20:50 +0100
commit94f7a18c01ab93952e3db95fb404eabd15ee47ce (patch)
tree75970dd937cd3b6cb867abf086200aaff4bbaa96
parent37200bc61ebdf6733179cf6446334c2444b0b19e (diff)
downloadbiboumi-94f7a18c01ab93952e3db95fb404eabd15ee47ce.tar.gz
biboumi-94f7a18c01ab93952e3db95fb404eabd15ee47ce.tar.bz2
biboumi-94f7a18c01ab93952e3db95fb404eabd15ee47ce.tar.xz
biboumi-94f7a18c01ab93952e3db95fb404eabd15ee47ce.zip
Update the doc to avoid using “” or "" and other chars
-rw-r--r--doc/biboumi.1.rst20
1 files changed, 10 insertions, 10 deletions
diff --git a/doc/biboumi.1.rst b/doc/biboumi.1.rst
index 06f32ff..592643b 100644
--- a/doc/biboumi.1.rst
+++ b/doc/biboumi.1.rst
@@ -83,13 +83,13 @@ fixed_irc_server
If this option contains the hostname of an IRC server (for example
irc.example.org), then biboumi will enforce the connexion to that IRC
-server only. This means that a JID like "#chan@biboumi.example.com" must
-be used instead of "#chan%irc.example.org@biboumi.example.com". In that
+server only. This means that a JID like ``#chan@biboumi.example.com`` must
+be used instead of ``#chan%irc.example.org@biboumi.example.com``. In that
mode, the virtual channel (see `Connect to an IRC server`_) is not
-available. The '%' character loses any meaning in the JIDs. It can appear
+available. The `%` character loses any meaning in the JIDs. It can appear
in the JID but will not be interpreted as a separator (thus the JID
-"#channel%hello@biboumi.example.com" points to the channel named
-"#channel%hello" on the configured IRC server) This option can for example
+``#channel%hello@biboumi.example.com`` points to the channel named
+``#channel%hello`` on the configured IRC server) This option can for example
be used by an administrator that just wants to let their users join their own
IRC server using an XMPP client, while forbidding access to any other IRC
server.
@@ -200,8 +200,8 @@ Addressing
----------
IRC entities are represented by XMPP JIDs. The domain part of the JID is
-the domain served by biboumi (the part after the ``@``, biboumi.example.com in
-the examples), and the local part (the part before the ``@``) depends on the
+the domain served by biboumi (the part after the `@`, biboumi.example.com in
+the examples), and the local part (the part before the `@`) depends on the
concerned entity.
IRC channels and IRC users have a local part formed like this:
@@ -521,11 +521,11 @@ arbitrary IRC message, biboumi forwards any XMPP message received on an IRC
Server JID (see *ADDRESSING*) as a raw command to that IRC server.
For example, to WHOIS the user Foo on the server irc.example.com, a user can
-send the message “WHOIS Foo” to “irc.example.com@biboumi.example.com”.
+send the message “WHOIS Foo” to ``irc.example.com@biboumi.example.com``.
The message will be forwarded as is, without any modification appart from
-adding "\r\n" at the end (to make it a valid IRC message). You need to have
-a little bit of understanding of the IRC protocol to use this feature.
+adding ``\r\n`` at the end (to make it a valid IRC message). You need to
+have a little bit of understanding of the IRC protocol to use this feature.
Security
========