- 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.
of the website that could use more help than old release schedules
that are no longer relevant -- however this one is simple enough that
I'll just commit it so we can incorporate these improvements in our
next release schedule.
PR: www/50247
Submitted by: Sergey A. Osokin <osa@FreeBSD.org.ru>
release documentation.
With one exception (the 4.6-RELEASE announce.sgml), these are all
generated files. Usually I would be opposed to editing the generated
output, except that we're already getting bug reports resulting from
changing the way we refer to the Handbook.
Only doing this for 4.6-RELEASE and 5.0-DP1 now because these are the
latest active "releases".
Suggested by: nik
We're not ready to release tonight. We need :
* a repo copy of 16 ports files (cvs@ pinged again).
* resolution to sysinstall/X11 issue (O'Brien is working on this).
* more testing with the final package set.
* more ata(4) testing.
is solely a schedule for 4.6.
* Link to the FAQ/#DEFINE-MFC at our first use of that acronym.
* Make a few 4.5 -> 4.6 changes that slipped through.
* Add an item for us to post the proposed package split for the
release media 2 weeks before the final release, to give stable users
the chance to scrutinize our selection of packages for the first CD.
