Abstraction Layer (i.e. volume auto-mounting, troubleshooting, etc.). Link
this new FAQ into the navibar, and replace our old auto-mounting question
with a link to this new FAQ.
While in our general FAQ, clean up the question on gnome-keyring.
Reviewed by: mezz and ahze
- Move includes.nav*.sgml to share/sgml/navibar.ent and
<lang>/share/sgml/nabibar.l10n.ent.
- Move includes.sgml and includes.xsl to
share/sgml/common.ent, share/sgml/header.ent, <lang>/share/sgml/l10n.ent,
and <lang>?share/sgml/header.l10n.ent.
- Move most of XSLT libraries to share/sgml/*.xsl and
<lang>/share/sgml/*.xsl.
- Move news.xml and other *.xml files for the similar purpose
to share/sgml/*.xml and <lang>/share/sgml/*.xml.
- Switch to use a custom DTD for HTML document. Now we use
"-//FreeBSD//DTD HTML 4.01 Transitional-Based Extension", which is
HTML 4.01 + some entities previously pulled via
"<!ENTITY % includes SYSTEM "includes.sgml"> %includes;" line.
The location of entity file will be resolved by using catalog file.
- Add DOCTYPE declearation to XML documents. This makes the followings
possible:
* Use of &foo; entities for SGML in an XML file instead of defining
{$foo} as the same content.
* &symbolic; entities for Latin characters.
- Duplicated information between SGML and XML, or English and
translated doc, has been removed as much as possible.
There's a new upgrade FAQ, and a new script to handle the upgrading. Do
not upgrade GNOME without it!
Also incorporated are a number of grammar and readability fixes.
Now there are three separate lists: GNOME 1 components, GNOME 2 components,
and thingies that aren't in the other things with the stuff, like the
hacks.
This now mirrors the division present in bsd.gnome.mk in the development
tree.
with tracking development releases of GNOME, plus give them information on
reporting bugs, known issues, and what more they can do to help.
The bulk of this work was by adamw, with some additional content and
formatting changes.
* Move the GNOME FAQ to the GNOME 1.4.1 FAQ
* Add corresponding links to the main page
* Add a disclaimer to the porting page saying that the porting methods
are about to change
