root/branches/licq/website/faqs.php

Revision 4124, 31.1 kB (checked in by emostar, 4 years ago)

Initial revision

  • Property svn:eol-style set to native
  • Property svn:executable set to *
  • Property svn:keywords set to Author Date Id Revision
Line 
1<?
2  include "header.php";
3
4  if (file_exists("/home/groups/l/li/licq/htdocs/zorbstats/zorblogs.php"))
5    include("/home/groups/l/li/licq/htdocs/zorbstats/zorblogs.php");
6  if (file_exists("/home/groups/l/li/licq/htdocs/zorbstats/zorblogspages.php"))
7  {
8    include ("/home/groups/l/li/licq/htdocs/zorbstats/zorblogspages.php");
9    $pagename = substr($PHP_SELF, 1);
10    $dispname = substr($PHP_SELF, 1, -4);
11    countpage($pagename, $dispname);
12  }
13?>
14     
15      <div id="content" >
16
17      <div id="main"><img src="images/main_title_faqs.gif" alt="Faqs" /></div>
18        <div id="maincontent">
19          <div id="subcontent">
20
21            <!-- News Item Begin-->
22            <div class="news">
23              <h2>Licq FAQ</h2>
24              <h3>September 30, 2004</h3>
25             
26              <p>
27              Originally written by Graham Roff<br>
28              Rewritten by Jon Keating
29              </p>
30              <div class="footer">
31                <div class="footer_right"></div>
32              </div>
33            </div>
34            <!-- News Item End-->
35           
36            <!-- News Item Begin-->
37            <div class="news">
38              <h2>Section 1: Basics</h2>
39                <p>
40                <blockquote>
41                <A HREF="#1_1">1.1: Who wrote Licq?</A><BR>
42                <A HREF="#1_2">1.2: What does Licq stand for anyway?</A><BR>
43                <A HREF="#1_3">1.3: Is Licq based on micq code like many of the other clones?</A><BR>
44                </blockquote>
45                </p>
46               
47            <h3>Section 2: Compiling / Installing</h3>
48                <blockquote>
49                <A HREF="#2_1">2.1: What is needed to compile Licq?</A><BR>
50                <A HREF="#2_2">2.2: How do I get Licq working through a SOCKS5 server?</A><BR>
51               
52                <A HREF="#2_3">2.3: How do I do a manual install (ie I have a binary distribution)?</A><BR>
53                <A HREF="#2_4">2.4: I am trying to compile with Solaris and the compilation freezes at the "moc" line.</A><BR>
54                <A HREF="#2_5">2.5: I am compiling under Solaris and I get an internal error.</A><BR>
55                <A HREF="#2_6">2.6: I am using an older compiler (ie gcc 2.7) and get errors about ANSI C++ not allowing implicit casting of "void *".</A><BR>
56                <A HREF="#2_7">2.7: What is socklen_t?</A><BR>
57                </blockquote>
58               
59            <h3>Section 3: Using</h3>
60                <blockquote>
61                <A HREF="#3_1">3.1: Where do I get a uin from?</A><BR>
62                <A HREF="#3_2">3.2: Does multi-party chat work?</A><BR>
63                <A HREF="#3_3">3.3: What is, and how do I use, the licq fifo?</A><BR>
64                <A HREF="#3_4">3.4: What happened to the "beep" OnEvent option, or, how do I make the pc-speaker beep when receiving a message?</A><BR>
65                <A HREF="#3_5">3.5: Licq appears 5 times in my process list, what's going on?</A><BR>
66                <A HREF="#3_6">3.6: I get "[ERR] Unable to allocate TCP port for local server (Unknown host)" when I start Licq.</A><BR>
67                <A HREF="#3_7">3.7: What happened to the spoof uin option?</A><BR>
68                <A HREF="#3_8">3.8: I am using ip_masq_icq module and it doesn't forward connections to Licq.</A><BR>
69                <A HREF="#3_9">3.9: How do I configure ipmasq for ICQ?</A><BR>
70               
71                <A HREF="#3_10">3.10: I can't connect to ICQ, all I get are timeouts!</A><BR>
72                <A HREF="#3_11">3.11: Does Licq support server side contact lists?</A><BR>
73                </blockquote>
74
75            <h3>Section 4: Plugins</h3>
76                <BLOCKQUOTE>
77                <A HREF="#4_1">4.1: I get something about being unable to load a plugin because "file not found" or "no such file or directory".</A><BR>
78                <A HREF="#4_2">4.2: I get something about "undefined symbol: ..." when I try and load the Qt-GUI plugin.</A><BR>
79                <A HREF="#4_3">4.3: Licq starts up but then exits with "licq: Fatal IO error: client killed".</A><BR>
80               
81                <A HREF="#4_4">4.4: What does "undefined symbol: LP_Main" mean?</A><BR>
82                <A HREF="#4_5">4.5: Qt-gui crashes on startup, it says something about "XRegisterIMInstantiateCallback"</A><BR>
83                <A HREF="#4_6">4.6: When Licq is docked it is still visible in the taskbar, what can i do?"</A><BR>
84                </BLOCKQUOTE>
85               
86            <h3>Section 5: Qt-GUI Plugin</h3>
87                <BLOCKQUOTE>
88                <A HREF="#5_1">5.1: The GUI says it is unable to load &lt;file&gt;.xpm or &lt;file&gt;.gif, but the file is there!</A><BR>
89               
90                <A HREF="#5_2">5.2: How do I change the colors of the Qt-Gui?</A><BR>
91                <A HREF="#5_3">5.3: Why are there no spaces between words in the History tab?</A><BR>
92                <A HREF="#5_4">5.4: How do I dock the Licq icon?</A><BR>
93                <A HREF="#5_5">5.5: How do I see other encodings (Russian, Japanese, etc.)?</A><BR>
94                </BLOCKQUOTE>
95               
96            <h3>Section 6: Protocol Plugins</h3>
97                <BLOCKQUOTE>
98                <A HREF="#6_1">6.1: What protocols are available?</A><BR>
99                <A HREF="#6_2">6.2: How do I start using a protocol plugin?</A><BR>
100                </BLOCKQUOTE>
101
102            <h3>Section 7: Donations</h3>
103                <BLOCKQUOTE>
104                <A HREF="#7_1">7.1: What are the operating expenses?</A><BR>
105                <A HREF="#7_2">7.2: What is the emergency fund?</A><BR>
106                <A HREF="#7_3">7.3: How do I know my donation is going to the project?</A><BR>
107               
108                <A HREF="#7_4">7.4: I donated money, will you add the feature I want?</A><BR>
109                </BLOCKQUOTE>
110              <div class="footer">
111                <div class="footer_right"></div>
112              </div>
113            </div>
114            <!-- News Item End-->
115               
116            <!-- News Item Begin-->
117            <div class="news">
118             
119            <H3><STRONG>Section 1: Basics</STRONG></H3>
120                <P>
121                <A NAME="1_1"><STRONG>1.1: Who wrote Licq?</STRONG>
122                <P>
123                Licq was first begun as a text mode client to ICQ in February 1998 by
124                Graham Roff and a programmer who wishes for some strange
125                reason to remain anonymous.  He's from Nova Scotia, perhaps that explains
126                things.  The Qt port was written by Graham Roff and starting in June
127                1998.<BR><BR>
128                Since then the entire code was rewritten by Graham Roff, with the
129                assistance of numerous internet volunteers.  The protocol plugin
130                rewrite of Licq was done by the current maintainer, Jon Keating.  All
131                current development is done by Jon Keating, Thomas Reitelbach, and
132                many volunteers.
133                <P>
134                <BR>
135               
136                <A NAME="1_2"><STRONG>1.2: What does Licq stand for anyway?</STRONG>
137                <P>
138                Contrary to popular belief, it does not stand for Linux ICQ.  This
139                would be (a) a bit conceited, and (b) way too obvious a name for a linux
140                program.
141                <P>
142                <BR>
143               
144                <A NAME="1_3"><STRONG>1.3: Is Licq based on micq code like many of the other clones? </STRONG>
145                <P>
146                Licq was begun a long time before micq was released and is based
147                completely on original source code.  It is also done in C++ as opposed to C
148                like micq and most of the other clones.
149                <P>
150                <BR>
151
152                <H3><STRONG>Section 2: Compiling and Installing</STRONG></H3>
153                <P>
154
155                <A NAME="2_1"><STRONG>2.1: What is needed to compile Licq?</STRONG>
156                <P>
157                See the web page in the info section under Requirements for all the details.
158                <P>
159                <BR>
160               
161                <A NAME="2_2"><STRONG>2.2: How do I get Licq working with a SOCKS5 server?</STRONG>
162                <P>
163                I do not use socks, and didn't write the code to make Licq work with
164                socks.  After configuring with --enable-socks5 you have to set some environment
165                variables as well, follow the guidelines that come with the socks5 client.
166                Other than that, I can't help you.  Try the README.SOCKS included with the
167                Licq distribution.
168                <P>
169                <BR>
170               
171                <A NAME="2_3"><STRONG>2.3: How do I do a manual install (ie I have a binary distribution)?</STRONG>
172                <P>
173                <EM>&amp;lt;= 0.61</EM><BR>
174                Easy, first copy the binary to somewhere nice (like /usr/local/bin).
175                Then copy licq-base.tar.gz to /usr/local/share.  There are some other
176                interesting documents to look at if you want as well.  Then run licq and it
177                should finish the install for you.  See, it's easy.<BR>
178                <EM>&amp;gt;= 0.70</EM><BR>
179                Copy the binary somewhere nice like above.  Then copy everything from the
180                share/ directory to /usr/local/share/licq.  To manually install a plugin simply
181                copy it to /usr/local/lib/licq/plugins.
182               
183                <P>
184                <BR>
185               
186                <A NAME="2_4"><STRONG>2.4: I am trying to compile and the compilation freezes at the "moc" line.</STRONG>
187                <P>
188                Licq requires GNU make to compiler properly.  Alternatively,
189                you can compile all the moc files by hand doing:<BR>
190                $&gt; moc &lt;infile&gt; -o &lt;outfile&gt;<BR>
191                The list of files to moc is in the Makefile.  If you do this, you will
192                still have to replace the $^ in the following section:<BR>
193               
194                ++ licq: $(OBJECTS) $(METAOBJ)<BR>
195                ++         $(CXX) $(CXXFLAGS) -o $@ $^ $(LDFLAGS) $(LDLIBS)<BR>
196                to be:<BR>
197                ++ licq: $(OBJECTS) $(METAOBJ)<BR>
198                ++         $(CXX) $(CXXFLAGS) -o $@ $(OBJECTS) $(METAOBJ) $(LDFLAGS) $(LDLIBS)<BR>
199                <P>
200                <BR>
201               
202                <A NAME="2_5"><STRONG>2.5: I am compiling and I get an internal error.</STRONG>
203                <P>
204                This is a problem with some versions of g++.  Simply remove <EM>-O2</EM>
205               
206                from the relevant Makefile and it should work fine.
207                <P>
208                <BR>
209               
210                <A NAME="2_6"><STRONG>2.6: I get errors about ANSI C++ not allowing implicit casting of "void *".</STRONG>
211                <P>
212                Some older implementations of libstdc++ erroneously define NULL as being
213                ((void *)0), which causes some c++ compilers to complain.  If this is the case,
214                you can either upgrade to a newer compiler or simply run the "remove-null.sh" (included
215                with the licq-data package in <EM>contrib</EM>)
216                inside the <EM>src/</EM> directory, which will replace all NULL's with zeros.
217                <P>
218                <BR>
219               
220                <A NAME="2_7"><STRONG>2.7: What is socklen_t?</STRONG>
221               
222                <P>
223                If you get compile errors refering to socklen_t simply edit config.h and
224                add "#define socklen_t int" to it somewhere.
225                <P>
226                <BR>
227               
228               
229                <H3><STRONG>Section 3: Using</STRONG></H3>
230                <P>
231
232               
233                <A NAME="3_1"><STRONG>3.1: How do I get a uin?</STRONG>
234                <P>
235                Licq can register a new user with Mirabilis.  Just select "Register User" from
236                the user menu.  See http://www.mirabilis.com for more info.
237                <P>
238                <BR>
239               
240                <A NAME="3_2"><STRONG>3.2: Does multi-party chat work?</STRONG>
241                <P>
242                Yes.
243                <P>
244                <BR>
245               
246                <A NAME="3_3"><STRONG>3.3: What is, and how do I use, the licq fifo?</STRONG>
247                <P>
248               
249                Please see the <A HREF="README.FIFO">README.FIFO</A>
250                <P>
251                <BR>
252               
253                <A NAME="3_4"><STRONG>3.4: What happened to the "beep" OnEvent option, or, how do I make the pc-speaker beep when receiving a message?</STRONG>
254                <P>
255                The beep command did not work properly and so was incorporated into a
256                self-contained executable (build beep.c in the contrib directory using the
257                instructions contained therein) which can be called instead of "play" (or
258                whatever) in order to generate a beep.<BR>
259                So to rephrase, instead of a beep option, you can build a "beep" executable,
260                and enter "beep" as the OnEvent Command (the parameters are irrelevant for
261                this command).
262                <P>
263                <BR>
264               
265                <A NAME="3_5"><STRONG>3.5: Licq appears 5 times in my process list, what's going on?</STRONG>
266               
267                <P>
268                There is really only 1 copy of Licq running, using the resources of one of
269                the listed processes.  The reason you see multiple copies is that Linux
270                shows threads as separate processes.  As Licq may be running 5 threads or more
271                at a time, multiple process entries will appear.
272                <P>
273                <BR>
274               
275                <A NAME="3_6"><STRONG>3.6: I get "[ERR] Unable to allocate TCP port for local server (Unknown host)" when I start Licq.</STRONG>
276                <P>
277                This will happen if you have not set up your hostname properly.  This is a
278                necessary step for running many network applications.  Make sure your hostname
279                (which can be found by typing "hostname") resolves to a valid ip.  Typically
280                this involves adding it to /etc/hosts and setting the ip to your static ip or
281                to 127.0.0.1 if you don't have one.
282                <P>
283                <BR>
284               
285                <A NAME="3_7"><STRONG>3.7: What happened to the spoof uin option?</STRONG>
286                <P>
287                This is no longer supported by the ICQ protocol. Sorry.
288                <P>
289                <BR>
290               
291               
292                <A NAME="3_8"><STRONG>3.8: I am using ip_masq_icq module and it doesn't forward connections to Licq.</STRONG>
293                <P>
294                The ip_masq_icq module uses the ip contained in the logon packet to determine whether
295                or not to forward connections to your machine.  This IP is determined typically
296                by looking at the hostname of the local machine.  If your hostname is not set correctly
297                or cannot be resolved, then Licq will default to using 127.0.0.1, which will be ignored
298                by the module.<BR>
299                The solution is to ensure that your hostname (to find it, type "hostname" at the prompt)
300                resolves to your correct sub-net IP.  To find out, ping your hostname ("ping &lt;hostname&gt;")
301                and see what the ip ends up being.<BR>
302                This ip will probably be something in the 192.168.xx.xx or 10.xx.xx.xx range.  If it
303                resolves to 127.0.0.1 or 0, then there is a problem.  To fix this, simply edit
304                <I>/etc/hosts</I> and enter the correct ip and hostname there, for example:
305                <P>
306                127.0.0.1    localhost<BR>
307               
308                192.168.0.2  &lt;hostname&gt;<BR>
309                ...<BR>
310                <P>
311                <BR>
312               
313                <A NAME="3_9"><STRONG>3.9: How do I configure ipmasq for ICQ?</STRONG>
314                <P>
315                Configuring ipmasq and ipchains for ICQ is fairly simple.  The relevant
316                man pages contain a good source of information as well.  Here is a sample
317                configuration using ipmasq:<BR>
318                ---(cut here)---<BR>
319                <BR>
320                # Enable port forwarding for ICQ Client<BR>
321               
322                #<BR>
323                port=2000<BR>
324                while [ $port -lt 2020 ]<BR>
325                do<BR>
326                /usr/sbin/ipmasqadm portfw -a -P tcp -L $xnet $port -R 192.168.1.2 $port<BR>
327                port=$((port+1))<BR>
328                done<BR>
329                /usr/sbin/ipmasqadm portfw -a -P udp -L $xnet 4000 -R 192.168.1.2 4000<BR>
330               
331                <BR>
332                ---(cut here)---<BR>
333                <BR>
334                And here is an example using iptables which is used with the Linux Kernel 2.4.x:<BR>
335                ---(cut here)---<BR>
336                <BR>
337                iptables -t nat -A PREROUTING -p tcp --destination-port 2000:2020 -i ppp0 -j DNAT --to 192.168.1.2<BR>
338                iptables -t nat -A PREROUTING -p udp --destination-port 4000 -i ppp0 -j DNAT --to 192.168.1.2<BR>
339               
340                <BR>
341                ---(cut here)---<BR>
342               
343                <BR>
344                This script will forward tcp ports 2000-2020 and udp port 4000 to your
345                machine inside the firewall. Note $xnet is the ip address issued to you by
346                your ISP and 192.168.1.2 should be changed to the ip address of the
347                machine that you are running Licq on.  Also note that this is just one
348                sample configuration and there are other ways to do this, using ipchains
349                for example.<BR>
350                <P>
351                <BR>
352               
353               
354                <A NAME="3_10"><STRONG>3.10: I can't connect to ICQ, all I get are timeouts!</STRONG>
355                <P>
356                This is a problem with the ICQ servers and people who use icq2000.  For
357                some reason a selection of the icq servers do not allow you to log on using
358                another client after using icq2000.<BR>
359                The solution?  Edit ~/.licq/licq.conf and set the servers to be a valid
360                icq.mirabilis.com ip except 205.188.153.*, eg 205.188.179.33.  Try
361                "nslookup icq.mirabilis.com" for more.<BR>
362                This, hopefully, will make it work.  In any case, it's not a Licq problem, but
363                a mirabilis stupidity.<BR>
364                <P>
365             
366               
367                <BR>
368               
369                <A NAME="3_11"><STRONG>3.11: Does Licq support server side contact lists?</STRONG>
370                <P>
371               
372                Yes, it is enabled by default. Licq supports having a user in multiple groups
373                but the server only allows one group per user. This is a little difficult to
374                manage, so there is a seperate menu item to change the server group of a user.
375                Just right click a user in the Qt-GUI and take a look for yourself.
376                <P>
377                <BR>
378               
379               
380                <H3><STRONG>Section 4: Plugins</STRONG></H3>
381                <P>
382
383                <A NAME="4_1"><STRONG>4.1: I get something about being unable to load a plugin because "file not found" or "no such file or directory".</STRONG>
384                <P>
385                If this happens with QT-GUI then you most likely configured --with-kde support.
386                In this case, please type "licq -p kde-gui" to start licq and read the README.KDE file.<BR>
387                In all other cases the plugin may be unable to find a necessary library.
388                Use "ldd" on the offending plugin to see which library it can't find.  Then add
389                the directory containing that missing library to your /etc/ld.so.conf file or
390                LD_LIBRARY_PATH environment variable (see 4.2).
391                <P>
392                <BR>
393               
394                <A NAME="4_2"><STRONG>4.2: I get something about "undefined symbol: ..." when I try and load the Qt-GUI plugin.</STRONG>
395                <P>
396                This problem occurs if you have a copy of qt 1.4 somewhere on your system
397                and Licq is linked to it.  Verify this using <EM>ldd /usr/local/lib/licq/licq_qt-gui.so</EM>
398                and see which qt library it's linked to.  If it is qt 1.4 then this library will have
399                to be moved to somewhere after the location of the qt 2.0 library, as listed
400                in /etc/ld.so.conf.  Read the README-QT-1.4-AND-2.0 for more information.<BR>
401                One other solution is simply to add the directory with Qt 2.0 in it to your
402                LD_LIBRARY_PATH environment variable like so:<BR>
403                <EM>export LD_LIBRARY_PATH=/usr/local/qt/lib</EM><BR>
404                which can be added to /etc/profile as per the Qt installation instructions.
405                <P>
406                <BR>
407               
408                <A NAME="4_3"><STRONG>4.3: Licq starts up but then exits with "licq: Fatal IO error: client killed".</STRONG>
409               
410                <P>
411                Because Licq is multi-threaded, it requires thread-safe X11 libraries.  These
412                can be aquired by recompiling your X server with the thread option or by grabbing
413                the binaries (see the Info section of the Licq web page under Requirements).
414                <P>
415                <BR>
416               
417                <A NAME="4_4"><STRONG>4.4: What does "undefined symbol: LP_Main" mean?</STRONG>
418                <P>
419                This is a bug with the dynamic loader used in SMP machines.  Try changing DLOPEN_POLICY
420                in config.h to RTLD_NOW and rebuild.  Or upgrade your kernel/ld.
421                <P>
422                <BR>
423                <A NAME="4_5"><STRONG>4.5: Qt-gui crashes on startup, it says something about "XRegisterIMInstantiateCallback"</STRONG>
424                <P>
425                There is a bug in QT 3.x whith X Input Methods (XIM).<BR>
426                Try to start licq like this: "licq -- -noxim".
427               
428                <P>
429                <BR>
430                <A NAME="4_6"><STRONG>4.6: When Licq is docked it is still visible in the taskbar, what can i do?</STRONG>
431                <P>
432                When you are using KDE you can prevent Licq from beeing visible in the taskbar.<BR>
433                Simply prepend "kstart --skiptaskbar" to your commandline:<BR>
434                <TT>kstart --skiptaskbar licq</TT>
435                <P>
436                <BR>
437               
438               
439                <H3><STRONG>Section 5: Qt-GUI Plugin</STRONG></H3>
440                <P>
441
442                <A NAME="5_1"><STRONG>5.1: The QUI says it is unable to load &lt;file&gt;.xpm or &lt;file&gt;.gif, but the file is there!</STRONG>
443                <P>
444                Qt has problems loading certain formats of xpm.  The solution is simply
445                to save the pixmap in question as a gif and edit the skin file appropriately.    If the
446                file in question is a gif, then make sure that you compiled qt with gif support
447                enabled (<EM>configure -gif</EM>).
448                <P>
449                <BR>
450               
451                <A NAME="5_2"><STRONG>5.2: How do I change the colors of the Qt-Gui?</STRONG>
452                <P>
453               
454                Colors are now integrated into the skin file.  To change colors you must
455                edit the skin file (found in <EM>/usr/local/share/licq/qt-gui/skin.&lt;name&gt;</EM>) and
456                add the following:<BR>
457                <BR>
458                # --- colors ---<BR>
459                colors.online = #ff0000 <BR>
460                colors.away = dark green<BR>
461                colors.offline = firebrick<BR>
462                colors.newuser = yellow<BR>
463                colors.background = default<BR>
464               
465                colors.gridlines = black<BR>
466                <BR>
467                Of course you get to select your own colors!
468                <P>
469                <BR>
470               
471                <A NAME="5_3"><STRONG>5.3: Why are there no spaces between words in the History tab?</STRONG>
472                <P>
473                This seems to be a bug in the Qt widget being used.  The solution is simply to use a TrueType font.
474                Select one from the Options Dialog in the Font section.
475                <P>
476                <BR>
477               
478                <A NAME="5_4"><STRONG>5.4: How do I dock the Licq icon?</STRONG>
479                <P>
480               
481                Docking the licq qt-gui status icon is fairly simple to do.  Here is a list
482                of window managers and what to do. If your window manager supports the
483                freedesktop.org standard, just enable the "Small Icon" in the Options. If you
484                are using KDE, use the KDE-GUI (./configure --with-kde for the Qt-GUI).
485               
486                If you aren't using a freedesktop.org compliant window manager, do the following:<BR>
487                <BR>
488                1. Start Licq and enable the dock icon in the Options screen.<BR>
489                2. Select "Save Settings" from the system menu.<BR>
490                3. Restart Licq (very important).<BR>
491                <BR>
492                <STRONG>WindowMaker</STRONG><BR>
493                4. Drag the status icon to the dock and voila.<BR>
494                Note that the other icon that appears is from windowmaker and can be set
495                to something nice, or disable entirely using the windowmaker menu.<BR>
496                <BR>
497               
498                <STRONG>AfterStep</STRONG><BR>
499                4. Add the following to your ~/GNUstep/Library/AfterStep/wharf file:<BR>
500                "*Wharf licq      - Swallow "LicqWharf" echo &amp;"<BR>
501                5. Next time start Licq, the icon should appear in the wharf.<BR>
502                4*.Another possibility is to add:<BR>
503                *FvwmButtons(Swallow (UseOld,NoKill,NoClose) "LicqWharf" Nop, Action (Mouse 1) 'Exec
504                /usr/bin/licq')<BR>
505                to your FvwmButtons config file.<BR>
506                <BR>
507               
508                <STRONG>KDE</STRONG><BR>
509                4. Configure the qt-gui plugin with --with-kde and then licq will dock in Kicker.<BR>
510                5. Start Licq and there it goes!<BR>
511                <BR>
512                <STRONG>Gnome</STRONG><BR>
513                4. Pick a smaller dock icon then the default (either 64x48 or one of the themed icons).<BR>
514                5. Select "Swallow App" from the gnome panel menu.<BR>
515                6. Set "Title =  LicqWharf", "Width =  64", "Height = 48".<BR>
516                <BR>
517                <P>
518               
519                <A NAME="5_5"><STRONG>5.5: How do I see other encodings (Russian, Japanese, etc.)?</STRONG><BR>
520                <P>
521                In the options, you can select a default encoding.  Also, there are per-user encodings. In the event window, there is an encoding button in the top right corner.  If the proper encoding isn't listed there, select the "Show all encodings" in the options dialog. You may have to experiment to find the correct encoding (there are 3 Japanese ones), but it does work properly. So please try all the appropriate encodings before saying that it doesn't work.
522                </P>
523                <BR>
524               
525                <H3><STRONG>Section 6: Protocol Plugins</STRONG></H3>
526                <P>
527               
528                <A NAME="6_1"><STRONG>6.1: What protocols are available?</STRONG><BR>
529                <P>
530                Currently ICQ, AIM and MSN are available. Only one account per protocol can be used with the 1.3.0 release.  This limitation will be removed in a future release.  ICQ and AIM are viewed as one protocol from Licq, so this means only one AIM or ICQ account can be used.  Fortunately, this isn't too bad of a problem since ICQ and AIM work together.  This means you can add AIM users to your ICQ list and vice versa.  As for MSN, it is still being developed and supports basic functionality, but will be a full featured client soon!<BR><BR>
531                Other protocols such as Yahoo will come later.. unless someone else starts to work on it, then sooner.
532                </P>
533                <BR>
534               
535                <A NAME="6_2"><STRONG>6.2: How do I start using a protocol plugin?</STRONG><BR>
536                <P>
537                First you need to install the protocol plugin.  If you installed Licq from source, it can be found in the 'plugins' directory.  After it is installed, you need to load the plugin.  From the Qt-GUI this is done from the Plugin Manager dialog.  After it is loaded, open up the Owner Manager and add your account for the new protocol.
538                </P>
539                <BR>
540               
541                <H3><STRONG>Section 7: Donations</STRONG></H3>
542                <P>
543
544                <A NAME="7_1"><STRONG>7.1: What are the operating expenses?</STRONG><BR>
545                <P>
546                The mail server and DNS server are currently run by Dennis Tenn and he pays all costs privately.  A percentage of the donations will go to pay for the cost of running this server.  Also, the domain names must be paid for every few years.
547                </P>
548                <BR>
549               
550                <A NAME="7_2"><STRONG>7.2: What is the emergency fund?</A></STRONG><BR>
551                <P>
552                It is a percentage of donations that are kept in case a main developer has a personal emergency that requires monetary assistance.  The usage for this money will be for necessary items such as food, rent, medicine, and other similiar items.  It will not be used for unnecessary items such as alcohol, hardware, or anything that is a personal interest.
553               
554                </P>
555                <BR>
556               
557                <A NAME="7_3"><STRONG>7.3: How do I know my donation is going to the project?</A></STRONG><BR>
558                <P>
559                Since you are using Licq, you trust us not to put a backdoor in the program.  With this reasoning, you should trust us that your valued contribution will be used solely to directly help Licq.
560                </P>
561                <BR>
562               
563                <A NAME="7_4"><STRONG>7.4: I donated money, will you add the feature I want?</A></STRONG><BR>
564                <P>
565                Just because you donated money does not entitle you to automatically have a feature you want to be added.  It will be considered as all other feature requests are considered.  Your donations are appreciated, but they are viewed as contribuations you make to help continue the Licq project.
566                </P>
567                <BR>
568              <div class="footer">
569                <div class="footer_right"></div>
570              </div>
571            </div>
572            <!-- News Item End-->
573
574          </div>
575        </div>
576
577        <div id="mainfooter"><p id="mainfooter_left"></p><!-- <img src="images/main_bg_bottomleft.gif" border="0" alt="Main" /> --></div>
578
579            </div>
580
581<? include "footer.php" ?>
Note: See TracBrowser for help on using the browser.