From e9ab230626471337b99966702108b686e09b616f Mon Sep 17 00:00:00 2001 From: Jeff Teunissen Date: Thu, 15 Dec 2011 00:13:56 -0500 Subject: [PATCH] Docs: minor cleanups --- doc/config.dox | 13 ++++++------- doc/faq.dox | 14 +++++++------- 2 files changed, 13 insertions(+), 14 deletions(-) diff --git a/doc/config.dox b/doc/config.dox index c26d37745..7cf2662aa 100644 --- a/doc/config.dox +++ b/doc/config.dox @@ -1,7 +1,7 @@ //unfortunately, have to wrap the docs in a C comment for doxygen // vim:tw=74:formatoptions-=l /** -\page run_config Runtime Configuration. +\page run_config Runtime Configuration \li \subpage cmdline \li \subpage cvars @@ -13,7 +13,6 @@ \li \subpage key_binding \li \subpage cshift_cvars \li \subpage server_timestamps - */ /** @@ -44,13 +43,12 @@ part of the console command. nq-glx +setrom m_pitch \"-0.022\" \endverbatim \note The above works in bash. Other shells may vary. - */ /** -\page cvars Configuration variables +\page cvars Config Variables (Cvars) -The core of \QF's configurabitly is the cvar. +The core of \QF's configuration is the cvar. \section cvar_value Cvar values. Depending on the engine's use of the cvar, the value will be treated as a @@ -64,7 +62,7 @@ From the user's perspective, there are three types of cvar: automatically saved. \li archive cvar: like a plain cvar, the value can be displayed or set, but the cvar will be automatically saved to \c config.cfg by the engine on -shutdown or gamedir change (quakeworld). +shutdown or gamedir change (QuakeWorld). \li read-only cvar: the value can be displayed but not changed in any way (value or flags). If the cvar also happens to be an archive cvar (the archive flag was set before the read-only flag), then the cvar will be @@ -139,7 +137,7 @@ is set, or WINDOWS if not). ~/.config/quakeforge/quakeforge.conf on Linux and other UNIX like systems, and \c ~/quakeforgerc on Windows. -The global and user configuration files are normal quake scripts, but only +The global and user configuration files are normal Quake scripts, but only \c set, \c seta, and \c setrom commands are executed. It might seem strange to have the global and user configuration files @@ -177,6 +175,7 @@ user config file or the global config file. If \c setrom is used on the command line, even \c setrom in the config files can be overridden. */ + /** \page cmdcvarlist Command and Cvar Lists Lists of commands and cvars by program. diff --git a/doc/faq.dox b/doc/faq.dox index 73c0d09e9..ed6d869e9 100644 --- a/doc/faq.dox +++ b/doc/faq.dox @@ -11,10 +11,10 @@ \li \ref faq_cvar_rom \section gfx_wad What does "W_LoadWadFile: unable to load gfx.wad" mean? -The most common cause of this error is QuakeForge is unable to find -pak0.pak. QuakeForge looks for pak0.pak in both the $fs_userpath/id1 and +The most common cause of this error is \QF is unable to find +pak0.pak. \QF looks for pak0.pak in both the $fs_userpath/id1 and $fs_sharepath/id1 directories. In Windows, both fs_userpath and fs_sharepath -default to "." (ie, the current directory: the same as id's quake clients). In +default to "." (ie, the current directory: the same as id's Quake clients). In Linux (and other UNIX like operating systems), fs_userpath defaults to ~/.quakeforge and fs_sharepath defaults to $prefix/share/games/quakeforge (distribution packages might alter the exact path). @@ -24,16 +24,16 @@ See \ref filesystem for more details. \section pak0_pak Where can I get pak0.pak? See \ref game_data -\section game_data Why doesn't QuakeForge come with the game data? -While QuakeForge itself (and the Quake source code in general) is Free +\section game_data Why doesn't \QF come with the game data? +While \QF itself (and the Quake source code in general) is Free Software, the game itself is not free. You need to either purchase it from id Software or you can use OpenQuartz, a -project developing GPL compatible game data for Quake. +project developing GPL-compatible game data for Quake. \section git_compile_error Checking out git and running ./bootstrap creates a configure that syntax errors when I run it! What's wrong? Unlike downloading and compiling a release, when you checkout from git, you -must have all the dependencies of QuakeForge already installed as when +must have all the dependencies of \QF already installed as when configure is being created autotools sources m4 files... If the files do not exist, you get the errors you have seen. Try installing packages which contain the libraries that caused the syntax error, including the -dev versions, then