Bug#470750: Add warning about outdated info to texinfo texts.

git-svn-id: svn+ssh://svn.gnucash.org/repo/gnucash/trunk@16485 57a11ea4-9604-0410-9ed3-97b8803252fd

src/doc/design/component-manager.texinfo

@@ -2,6 +2,11 @@
 @chapter Component Manager
 @cindex Component Manager
 
+@strong{This whole document is completely outdated. Don't read this. All
+function names and every described structure has changed
+completely. Only read this if you want to know how gnucash looked like
+in 1999. This is completely outdated!}
+
 The Component Manager (hereafter referred to as the CM) is a framework
 for managing GUI objects in GnuCash. The CM provides several services.
 

src/doc/design/engine.texinfo

@@ -2,6 +2,11 @@
 @chapter Engine
 @cindex The Engine
 
+@strong{This whole document is completely outdated. Don't read this. All
+function names and every described structure has changed
+completely. Only read this if you want to know how gnucash looked like
+in 1999. This is completely outdated!}
+
 The Engine provides an interface to a financial engine with three basic
 financial entities: Accounts, Transactions (known as Journal Entries in
 accounting practice), and Splits (known as Ledger Entries). These three

src/doc/design/intro.texinfo

@@ -1,6 +1,11 @@
 @node Introduction, Top Level, GNU Free Documentation License, Top
 @unnumbered Introduction
 
+@strong{This whole document is completely outdated. Don't read this. All
+function names and every described structure has changed
+completely. Only read this if you want to know how gnucash looked like
+in 1999. This is completely outdated!}
+
 This document defines the design and architecture of the GnuCash
 program, an application for tracking finances. GnuCash is composed
 of several subsystems or modules. This document describes each module,

src/doc/design/register.texinfo

@@ -2,6 +2,11 @@
 @chapter Register
 @cindex Register
 
+@strong{This whole document is completely outdated. Don't read this. All
+function names and every described structure has changed
+completely. Only read this if you want to know how gnucash looked like
+in 1999. This is completely outdated!}
+
 The register is an infrastructure for building a modular matrix of cells
 in which each cell may be specialized to perform a particular function,
 e.g., to read dates, numerical amounts, or text. The register has been

src/doc/design/reports.texinfo

@@ -2,6 +2,11 @@
 @chapter Reports
 @cindex Reports
 
+@strong{This whole document is completely outdated. Don't read this. All
+function names and every described structure has changed
+completely. Only read this if you want to know how gnucash looked like
+in 1999. This is completely outdated!}
+
 The reporting infrastructure is designed facilitate the creation
 of sophisticated reports including tables, graphs, and hyperlinks.
 The infrastructure includes functionality to support the following:

src/doc/design/top-level.texinfo

@@ -1,6 +1,11 @@
 @node Top Level, Engine, Introduction, Top
 @chapter Architectural Overview
 
+@strong{This whole document is completely outdated. Don't read this. All
+function names and every described structure has changed
+completely. Only read this if you want to know how gnucash looked like
+in 1999. This is completely outdated!}
+
 GnuCash is written primarily in two languages: C and Scheme. The
 engine/server is written in C primarily for speed, portability,
 stability and historical purposes. Much of the day-to-day workhorse code

src/doc/design/user-preferences.texinfo

@@ -2,6 +2,11 @@
 @chapter User Preferences
 @cindex User Preferences
 
+@strong{This whole document is completely outdated. Don't read this. All
+function names and every described structure has changed
+completely. Only read this if you want to know how gnucash looked like
+in 1999. This is completely outdated!}
+
 The options system is used to obtain user preferences, both globally,
 and when displaying a report. A wide variety of option types are
 supported, so it should be possible to create an option for just about