- 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.
variable to point to http://www.FreeBSD.org/ - This is very useful for
when you e.g. are building part of the website, like we do for
http://security.FreeBSD.org/, and do not want broken links.
This knob only works for SGML files, which is enough for what I need.
We do not run XML files through sed so the same hack as used for SGML
cannot be used.
used to distribute FreeBSD Security Advisories and the associated
patches.
This change will change links of the advisory to point to the new web
server.
Discussed with: secteam
mainly a band-aid to make the project news box not be way too large.
The current problem is that the XSLT code counts 5 days, not 5 news
items so when we, like we do now, have a few days with multiple
entries the news box gets way to big. I could not find a quick way to
change this, hence the band-aid.
between our www and doc SGML files a bit smaller.
I know one is HTML and the other is DocBook, but since I try to
remember to use &os; for new text in doc/ it's a bit confusing that we
don't have &os; in www/.
newest testing toolbox whitepaper to the marketing documents page.
The goal is to segregate out non technical articles from the general
Books/HowTos page so that we do not confuse our audience for these
very different types of documents.
Discussed with: Dru Lavigne, gnn
