Ignore:
Timestamp:
2008-04-02T13:28:23Z (16 years ago)
Author:
Jelmer Vernooij <jelmer@…>
Branches:
master
Children:
6ff51ff, 85d7b85
Parents:
0db75ad (diff), fa75134 (diff)
Note: this is a merge changeset, the changes displayed below correspond to the merge itself.
Use the (diff) links above to see all the changes relative to each parent.
Message:

merge trunk.

File:
1 edited

Legend:

Unmodified
Added
Removed
  • doc/user-guide/commands.xml

    r0db75ad rdd34575  
    163163
    164164                        <para>
    165                                 If you want, you can also tell BitlBee what nick to give the new contact. Of course you can also use the <emphasis>rename</emphasis> command for that, but sometimes this might be more convenient.
    166                         </para>
    167                        
    168                         <para>
    169                                 Adding -tmp adds the buddy to the internal BitlBee structures only, not to the real contact list (like done by <emphasis>set handle_unknown add</emphasis>). This allows you to talk to people who are not in your contact list.
     165                                If you want, you can also tell BitlBee what nick to give the new contact. The -tmp option adds the buddy to the internal BitlBee structures only, not to the real contact list (like done by <emphasis>set handle_unknown add</emphasis>). This allows you to talk to people who are not in your contact list. This normally won't show you any presence notifications.
    170166                        </para>
    171167                </description>
     
    383379
    384380        <bitlbee-setting name="charset" type="string" scope="global">
    385                 <default>iso8859-1</default>
     381                <default>utf-8</default>
    386382                <possible-values>you can get a list of all possible values by doing 'iconv -l' in a shell</possible-values>
    387383
    388384                <description>
    389385                        <para>
    390                                 The charset setting enables you to use different character sets in BitlBee. These get converted to UTF-8 before sending and from UTF-8 when receiving.
    391                         </para>
    392 
    393                         <para>
    394                                 If you don't know what's the best value for this, at least iso8859-1 is the best choice for most Western countries. You can try to find what works best for you on http://czyborra.com/charsets/iso8859.html
     386                                This setting tells BitlBee what your IRC client sends and expects. It should be equal to the charset setting of your IRC client if you want to be able to send and receive non-ASCII text properly.
     387                        </para>
     388
     389                        <para>
     390                                Most systems use UTF-8 these days. On older systems, an iso8859 charset may work better. For example, iso8859-1 is the best choice for most Western countries. You can try to find what works best for you on http://www.unicodecharacter.com/charsets/iso8859.html
    395391                        </para>
    396392                </description>
     
    677673                <description>
    678674                        <para>
    679                                 Sends you a /notice when a user starts typing a message (if the protocol supports it, MSN for example). This is a bug, not a feature. (But please don't report it.. ;-) You don't want to use it. Really. In fact the typing-notification is just one of the least useful 'innovations' ever. It's just there because some guy will probably ask me about it anyway. ;-)
     675                                Sends you a /notice when a user starts typing a message (if supported by the IM protocol and the user's client). To use this, you most likely want to use a script in your IRC client to show this information in a more sensible way.
    680676                        </para>
    681677                </description>
     
    830826                <short-description>Change friendly name, nick</short-description>
    831827                <syntax>nick &lt;connection&gt; [&lt;new nick&gt;]</syntax>
    832                 <syntax>nick</syntax>
    833 
    834                 <description>
    835                         <para>
    836                                 This command allows to set the friendly name of an im account. If no new name is specified the command will report the current name. When the name contains spaces, don't forget to quote the whole nick in double quotes. Currently this command is only supported by the MSN protocol.
    837                         </para>
    838 
    839                         <para>
    840                                 It is recommended to use the per-account <emphasis>display_name</emphasis> setting to read and change this information. The <emphasis>nick</emphasis> command is deprecated.
     828                <syntax>nick &lt;connection&gt;</syntax>
     829
     830                <description>
     831                        <para>
     832                                Deprecated: Use the per-account <emphasis>display_name</emphasis> setting to read and change this information.
    841833                        </para>
    842834                </description>
    843835
    844836                <ircexample>
    845                         <ircline nick="wouter">nick 1 "Wouter Paesen"</ircline>
    846                         <ircline nick="root">Setting your name on connection 1 to `Wouter Paesen'</ircline>
     837                        <ircline nick="wouter">account set 1/display_name "The majestik møøse"</ircline>
     838                        <ircline nick="root">display_name = `The majestik møøse'</ircline>
    847839                </ircexample>
    848840
Note: See TracChangeset for help on using the changeset viewer.