\documentclass{article}
\usepackage{ulem}
\pagestyle{headings}
\begin{document}
\part{Special files}
\textbf{Colortext: NIThis information is valid for Horde 5 and later only. See Doc/Dev/SpecialFilesH3\footnote{http://example.com/index.php?page=Doc/Dev/SpecialFilesH3} for Horde 3 or Doc/Dev/SpecialFilesH4\footnote{http://example.com/index.php?page=Doc/Dev/SpecialFilesH4} for Horde 4.Colortext: NI}

\begin{itemize}
\item{\texttt{horde/lib/core.php}: This file}
\begin{itemize}
\item{sets some required PHP configuration settings}
\item{sets autoloading paths for Horde libraries}
\item{registers error handlers}
\end{itemize}
\end{itemize}
There are several files with a special meaning that can be found in every Horde application:

\begin{itemize}
\item{\texttt{index.php}: This script is loaded if a user enters an application. Usually this script doesn't have any functionality but simple loads the default view of the application, sometimes depending on the user's preferences.}
\item{\texttt{lib/Api.php}: This files defines and implements all methods that an application is exposing through the Registry\footnote{http://example.com/index.php?page=Doc/Dev/Registry} to the other Horde applications and the Horde RPC servers.}
\item{\texttt{lib/Application.php}: This file defines information need to initialize the application and to interact with the Horde framework. It also defines the version number of the application.}
\item{\texttt{lib/Exception.php}: This file defines the application-specific exception class.}
\item{\texttt{lib/Test.php}: This file defines any application specific tests to run when using the Horde test script.}
\item{\texttt{lib/Ajax/Application.php}: This file defines the AJAX actions provided by this module.}
\item{\texttt{themes/default/screen.css}: This is a CSS file that defines all application specific style sheet rules.}
\end{itemize}
\end{document}
