--- a/hugo/content/_index.md Fri Jul 09 16:04:09 2021 -0500
+++ b/hugo/content/_index.md Fri Jul 09 23:35:35 2021 -0500
@@ -14,7 +14,7 @@
Pidgin is compatible with the following chat networks out of the box:
Jabber/XMPP, Bonjour, Gadu-Gadu, IRC, Novell GroupWise Messenger, Lotus
Sametime, SILC, SIMPLE, and Zephyr. It can support many more with
+[plugins]({{< ref "plugins" >}}). Pidgin supports many features of these chat networks, such as file transfers,
away messages, buddy icons, custom smileys, and typing notifications. Numerous
--- a/hugo/content/development/building/2.x.y/_index.md Fri Jul 09 16:04:09 2021 -0500
+++ b/hugo/content/development/building/2.x.y/_index.md Fri Jul 09 23:35:35 2021 -0500
@@ -7,7 +7,9 @@
-If you're building for Windows you'll want to have a look at [windows](windows) instead.
+If you're building for Windows you'll want to have a look at +[the building on Windows page]({{< ref "development/building/2.x.y/windows" >}}) Pidgin's default build has a lot of dependencies. This document will hopefully
help you find and install them all.
@@ -54,7 +56,7 @@
`-dev` (Debian-based systems) package for each library installed. If `configure`
is succeeding, but `make` fails, this is harder to diagnose and you will
probably want to drop by the IRC channel or XMPP conference listed on
-[Community](/community) to get help.
+the [Contact]({{< ref "contact" >}}) page to get help. ## How do I install the dependencies on Debian or Ubuntu?
@@ -100,4 +102,4 @@
## Can I compile just Finch, not Pidgin?
-Sure. Pass `--disable-gtkui` to `./configure`.
\ No newline at end of file
+Sure. Pass `--disable-gtkui` to `./configure`. --- a/hugo/content/development/building/2.x.y/windows.md Fri Jul 09 16:04:09 2021 -0500
+++ b/hugo/content/development/building/2.x.y/windows.md Fri Jul 09 23:35:35 2021 -0500
@@ -63,7 +63,7 @@
The following instructions were written under the assumption that the
-[Pidgin source](#get-the-pidgin-source-code) will be extracted or checked out
+[Pidgin source]({{< ref "#get-the-pidgin-source-code" >}}) will be extracted or checked out into `$PIDGIN_DEV_ROOT/pidgin-<version>` and that you install all of Pidgin's
build dependencies under `$PIDGIN_DEV_ROOT/win32-dev` (the point being that
the pidgin source root and `win32-dev` directories should be on the same level). Similar to the example below:
@@ -110,8 +110,8 @@
## Get the Pidgin source code
The development source is available via Mercurial in the `release-2.x.y`
-branch. See [version control](/development/version-control/) for more
+branch. See [version control]({{< ref "development/version-control" >}}) for If you want to build a release tarball, the instructions in the rest of this
document should work for you, however they are written for the most recent
@@ -372,7 +372,8 @@
installing packages `mingw32`, `mingw32-binutils`, and `mingw32-runtime`. On
other distributions, the packages may be named differently.
-Set up a build environment as described [above](set-up-your-build-environment).
+Set up a build environment as described +[above]({{< ref "#set-up-your-build-environment" >}}). You should already have a bash shell and have just installed the mingw
@@ -423,4 +424,6 @@
MAKENSIS := /usr/local/bin/makensis
-Finally, you should be able to follow the [build](#build) instructions above.
+Finally, you should be able to follow the +[build]({{< ref "#build" >}}) instructions --- a/hugo/content/development/gsoc/_index.md Fri Jul 09 16:04:09 2021 -0500
+++ b/hugo/content/development/gsoc/_index.md Fri Jul 09 23:35:35 2021 -0500
@@ -26,13 +26,14 @@
-You can find our current list of ideas on the [Ideas](ideas) page. If
-you have any ideas, feel free to email the mailing list or open a pull request.
+You can find our current list of ideas on the [Ideas]({{< ref "ideas" >}}) +page. If you have any ideas, feel free to email the mailing list or open a ## Instructions for Applications
We have some detailed directions on how to make yourself stand out from the
-crowd on the [instructions](instructions) page.
+crowd on the [instructions]({{< ref "instructions" >}}) page. --- a/hugo/content/development/voice-and-video/_index.md Fri Jul 09 16:04:09 2021 -0500
+++ b/hugo/content/development/voice-and-video/_index.md Fri Jul 09 23:35:35 2021 -0500
@@ -30,12 +30,13 @@
flavor of Jingle. XMPP uses rawudp and XMPP, GTalk, and Gmail use the libnice
Farstream transmitter plugin.
-Voice and video support for XMPP/GTalk was worked on for a [Summer of Code
-project](/wiki/GSoC2008/VoiceAndVideo)
+Voice and video support for XMPP/GTalk was worked on for a +[Summer of Code project]({{< ref "development/gsoc/#previous-years" >}}) -Sametime seems to support at least voice chat according to
+Sametime seems to support at least voice chat according to [this IBM document](http://publib.boulder.ibm.com/infocenter/sametime/v8r0/index.jsp?topic=/com.ibm.help.sametime.standard.doc/st_adm_avserv_aboutvoicechat_r.html)
@@ -62,8 +63,8 @@
> Build with voice and video.... yes
For help with building, see
-[Installing Pidgin](/wiki/Installing%20Pidgin#Compiling). Please carefully
-read through that section and any extra information for the distribution you're
+[Building Pidgin]({{< ref "development/building" >}}). Please carefully read +through that section and any extra information for the distribution you're --- a/hugo/content/help/protocols/otherprotocols.md Fri Jul 09 16:04:09 2021 -0500
+++ b/hugo/content/help/protocols/otherprotocols.md Fri Jul 09 23:35:35 2021 -0500
@@ -11,17 +11,19 @@
website is gone. AOL terminated AIM in December 2017.
Yahoo! Messenger and ICQ changed protocols and Pidgin doesn't have the developer
-resources to support these protocols ourselves. See the [Plugins](/plugins/)
-page for community-maintained plugins for these and other services.
+resources to support these protocols ourselves. See the +[Plugins]({{< ref "plugins" >}}) page for community-maintained plugins for +these and other services. ### What happened to Facebook Chat support?
Facebook terminated their XMPP support in April 2014. An alternative Facebook
Messenger plugin was developed as a
-[Google Summer of Code](/gsoc/#previous-years) project. That plugin is
-currently in the Pidgin 3 source tree and has been backported to Pidgin 2. The
-backport can be found either
+[Google Summer of Code]({{< ref "development/gsoc/#previous-years" >}}) project. +That plugin is currently in the Pidgin 3 source tree and has been backported to +Pidgin 2. The backport can be found either [here](https://github.com/dequis/purple-facebook/wiki/) or on the
-[Plugins](/plugins/) page, but it is _not_ maintained by Pidgin's developers.
+[Plugins]({{< ref "plugins" >}}) page, but it is _not_ maintained by Pidgin's ### Why doesn't Pidgin support CyanChat, Microsoft LCS/Skype for Business, Skype, NateOn, NetSoul, etc.?
It is an incredible amount of work to implement and maintain support for a
@@ -32,7 +34,7 @@
That said, there are a number of people in the Pidgin community that have spent
the time to develop plugins for additional services including Skype, Microsoft
LCS/Skype for Business, and others. A list of known community-maintained
-plugins is available on the [Plugins](/plugins/) page.
+plugins is available on the [Plugins]({{< ref "plugins" >}}) page. If you are willing and able to implement and maintain a plugin for a protocol
that you use, we welcome and encourage you to do so! The beauty of Pidgin and
--- a/hugo/content/install/_index.md Fri Jul 09 16:04:09 2021 -0500
+++ b/hugo/content/install/_index.md Fri Jul 09 23:35:35 2021 -0500
@@ -44,7 +44,7 @@
If your operating system doesn't provide a pre-built package, or if their
pre-built package is out of date and you want to upgrade, then you can try
-[building from source](/development/building/).
+[building from source]({{< ref "development/building" >}}). @@ -103,7 +103,7 @@
If your operating system doesn't provide a pre-built package, or if their
pre-built package is out of date and you want to upgrade, then you can try
-[building from source](/development/building/).
+[building from source]({{< ref "development/building" >}}).