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
- Add link to the new advisory page into the support sidebar.
- Do not include release info in advisory list as it's not that
interesting in this context.
- Try to make it more clear where to report security issues to.
- Include public key directly on web site instead of referring to FTP
site.
- Remove some stale information.
- Misc minor cleanup.
Reviewed by: cperciva, remko, bz (various versions)
link to it from the navibar. The build machine of the web site doesn't
have ``XML/Parser.pm'' so to format the XML files we need either the
module or a conversion to XSLT :-(
Reported by: build triggered by kuriyama-san's webupdate script
The placement of the link here, instead of say "Documentation",
is done because the multimedia list of FreeBSD resources falls
under the wider umbrella of "creations of the worldwide FreeBSD
community", but are not really project-developed works.
the different teams do and what their responsibilities are. Our developers
are generally very confused when it comes to finding the right person to
talk to, for example when requesting repo-copies or new perforce accounts
etc. This will hopefully improve the situation somewhat.
This is meant to replace certain sections of the contributors article, as
this contains more up-to-date information and more teams etc. I'll take
a look at removing the sections in question and all references to them soon.
Also, the translation teams generally don't translate the contributors article
since it doesn't seem to be worth the effort. Hopefully this will change now,
since this can be quite important information even for non-English speaking
people.
I've based my work on comments from many developers and patches have been
floating around on the doc list for a while, so it's about time I commit it.
Reviewed by: doc@
- 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.
