--- a/htdocs/documentation.php Thu Jan 15 15:04:02 2004 -0500
+++ b/htdocs/documentation.php Thu Jan 15 15:30:13 2004 -0500
@@ -28,6 +28,7 @@
<li><a href="faq.php">FAQ</a> - Frequently Asked Questions</li>
<li><a href="shortcuts.php">Keyboard Shortcuts</a></li>
<li><a href="statusicons.php">Status Icons</a></li>
+ <li><a href="i18n/">Internationalization Statistics</a> - Updated nightly</li> <li><a href="gdb.php">Getting a backtrace</a> - Using GDB to get a backtrace</li>
<li><a href="protocol.php">Protocols</a> -
Descriptions of the protocols gaim uses (incomplete)</li>
--- a/htdocs/downloads.php Thu Jan 15 15:04:02 2004 -0500
+++ b/htdocs/downloads.php Thu Jan 15 15:30:13 2004 -0500
@@ -6,7 +6,8 @@
start_section("Downloads");
- The current version is <b><?php print $current_version; ?></b>.+ The current *nix version is <b><?php print $current_version; ?></b>.<br> + The current Windows version is <b><?php print $current_win32_version; ?></b>. @@ -85,7 +86,7 @@
CVS is a way of storing and tracking changes in the code between releases.
The Gaim source is kept in CVS. Because this is the central location for
all Gaim development, it always has the latest code and bug fixes. However,
- this also means it has the latest bugs.+ this means it also has the latest bugs. @@ -178,7 +179,7 @@
start_section("CVS Mailing List");
- We also now have a mailing list set up that will notify you when new+ We also have a mailing list set up that will notify you when new commits are made. Join gaim-commits@lists.sourceforge.net by telling us
<a href="http://lists.sourceforge.net/lists/listinfo/gaim-commits">http://lists.sourceforge.net/lists/listinfo/gaim-commits</a>.
--- a/htdocs/faq.txt Thu Jan 15 15:04:02 2004 -0500
+++ b/htdocs/faq.txt Thu Jan 15 15:30:13 2004 -0500
@@ -814,34 +814,30 @@
Q: Trepia is showing people in Japan, England, etc. on my buddy list. I
thought this was supposed to show people in my area?
-A: We believe this to be the protocol, not Gaim. As Trepia continues to-update and refine their protocol, it will become more accurate. If we find-out otherwise, we will attempt to incorporate the changes necessary to act-like the official client.+A: We believe this to be the fault of protocol, not Gaim. As Trepia +continues to update and refine their protocol, it will become more +accurate. If we find out otherwise, we will attempt to incorporate +the changes necessary to act like the official client. !SECTION Scripts and Plugins
Q: How do I use perl scripts with Gaim?
-A: Save the perl script to ~/.gaim/ or $prefix/lib/gaim/, restart Gaim,-and load the perl script by checking the check box next to its name on the-Plugins page in preferences.+A: Save the perl script to ~/.gaim/plugins/ or $prefix/lib/gaim/, +restart Gaim, and load the perl script by checking the check box +next to its name on the Plugins page in preferences. Q: How do I compile a plugin for Gaim?
-A: To compile a plugin for Gaim, you must have Gaim's source code. There-are two ways to get this: Tarballs, and CVS. To work with a tarball, follow-the instructions below. To use CVS, follow the instructions on the <a-href="cvs.php">CVS</a> page. Please note that often, CVS is much less stable -than the tarballs! Do not use CVS unless you are writting a patch. -<p> To work with a tarball, download the latest-source code from <a href="http://gaim.sf.net/">http://gaim.sf.net/</a> and-untar it with the command: <pre>tar zxvf <i>filename</i></pre> where-<i>filename</i> is the file you downloaded. </p>+A: To compile a plugin for Gaim, you must have Gaim's source code. +To download Gaim's source code, get the most recent tarball from +<a href="http://gaim.sourceforge.net/downloads.php">http://gaim.sourceforge.net/downloads.php</a> +and untar it with the command: <pre>tar zxvf <i>filename</i></pre> where +<i>filename</i> is the file you downloaded. - After you have a Gaim source code tree, either through tarballs or CVS:+ After you have a Gaim source code tree: @@ -880,34 +876,50 @@
A: The plugin and perl script API has changed in 0.60, which means plugins
and perl scripts must be modified in order to work. The plugin or perl
-script must be located in $prefix/lib/gaim or in ~/.gaim, and must+script must be located in $prefix/lib/gaim/ or in ~/.gaim/plugins/, and must implement the new API, as documented in the howto file in the plugins
directory. Plugins and perl scripts are now controled from preferences.
Q: Where can I find documentation on writing plugins and Perl scripts?
A: If you look in the <code>plugins/</code> directory in the Gaim source,
-you should see a HOWTO file for C plugins and a PERL-HOWTO for Perl+you should see a HOWTO file with some details for C plugins. You should +<a href="http://gaim.sourceforge.net/api/index.html">online documentation</a>. +Be especially sure to look at the Related Pages, which lists all of Gaim's +signals, as well as a nice perl script HOWTO. - In 0.68 or later, get the source code and run <code>make docs</code>. You will- need doxygen and graphviz dot installed for this to work. This will produce an- api reference and both the perl and plugin documentation.+ This documentation can be generated directly from the Gaim source by + running <code>make docs</code>. You will need doxygen and graphviz + dot installed for this to work. +A: But of course. Just find something that's bugging you and fix it. +There is a slew of a bug reports in Gaim's bug report tracker, you could +pick one and try to tackle it and submit a patch. You could also help +with general bug triage by going through the bug reports and leaving +comments such as "this has been fixed" or "this is a duplicate of bug +#12345." As always, make sure you follow the same coding style used in +Gaim, and make sure you don't break the core/UI split. +Q: Gaim never leaves a core file. +A: On most installs core files are limited in size to 0 bytes, and are +therefore not created. To rectify this situation, add +<code>ulimit -c unlimited</code> to your startup scripts (~/.bash_profile +is a good place) or run it manually in a terminal before starting gaim +from that terminal. You can also run Gaim directly in gdb with Q: Where should I report bugs?
A: <a href="bug.php">Here</a>.
-Q: Gaim never leaves a core file.-A: On most installs, for some odd reason, core files are limited in size-to 0 bytes, and so are not created. To rectify this situation, add-<code>ulimit -c unlimited</code> to your startup scripts or run it manually-in a terminal before starting gaim from that terminal. Q: Where should I submit patches?
A: <a href="patches.php">Here</a>.
@@ -918,22 +930,9 @@
didn't have to reverse engineer those. Oscar, ICQ, and Yahoo are not
published, and were reverse engineered by other people.
-Q: Will Gaim be ported to Windows 95/98/Me/2000/XP?-A: Gaim has released a Windows version.-Q: Does AOL's attempts at blocking Trillian affect Gaim?-Q: Is Gaim affected by the vulnerability found in Windows AIM or-Yahoo Instant Messenger clients? A: Sure! Look at the <a href="/contactinfo.php">Contact Information</a> page!
--- a/inc/navigation.inc.php Thu Jan 15 15:04:02 2004 -0500
+++ b/inc/navigation.inc.php Thu Jan 15 15:30:13 2004 -0500
@@ -30,16 +30,16 @@
+ "Windows Port" => array( + "URL" => "/win32/index.php", - "Windows Port" => array(- "URL" => "/win32/index.php",