this was that 'SGMLFLAGS' had to be changed to 'XMLFLAGS' in
share/mk/doc.docbook.mk so that everything continued to build OK.
Approved by: gabor (mentor)
much better ways of doing this in modern web browsers. Furthermore, it
never worked as well as it should have done, as too much of the website is
built around fixed layouts.
It was felt it was best to remove the size switcher from all languages at
once, so that the infrastructure (styleswitcher.js etc.) could be removed
at the same time.
Discussed at: Cambridge DevSummit, August 2012
Discussed on: www@
Approved by: gabor (mentor)
earlier one. It does not any more has per-tag and per-source pages
but one page for tags and one for sources with anchors. With the current
number of entries it will probably be fine for a long time but if once
we need to divide it into smaller chunks, it will be easier with XSLT.
- Now the documents are also rebuilt if stylesheets or the source XML
database changes and the build time is drastically decreased.
Reviewed by: www@
reasonable to maintain the reference, use the archived docs.
5-roadmap
checkpoint
dialup-firewall
diskless-x
euro
formatting-media
hats (content moved to htdocs/internal)
multi-os
storage-devices
vinum
zip-drive
All of these articles can be found here:
http://docs.freebsd.org/doc/9.0-RELEASE/usr/share/doc/freebsd/en_US.ISO8859-1/articles/
No objection from: doc@, www@
www.freebsd.org/security/{advisories,patches}/...
from the en_US.ISO8859-1 directory as we do for logos, etc.
The magic is a bit special to avoid having to add each advisory
or errata notice, and their patches and signatures individually.
Factor out the slightly different to bsd.links.mk SYMLINKS
support as well as the "bulk data install" that cannot be
handled by just DATA as (i) the input dir differs, (ii) input
uses a 1 or more level of sub-directories.
This is the second of three steps. The last one will be to link
to these files locally rather than to security.freebsd.org.
Approved by: gabor
- Documentation is updated from DocBook 4.1/SGML to DocBook 4.2/XML
- Webpages are updated from HTML 4.01 Transitional to XHTML 1.0 Transitional
- Static webpages are now processed by XSLT behind the scenes
- Webpages are now built with less cycles; tidy has been removed and the
date processing is now done by XSLT
- Generated webpages are now actually valid (they did not use to be)
- All XSLT stylesheets now pull in a main XSLT, which reduces
duplicated markup
- Site map and index are converted to an XML format with an
XSLT transformation that generates the output
- For docs, there is now only one entity set for both articles and books
- Some trademark/legalnotice entities have been merged to a cohesive
single entity file
- Untranslated entity sets are now always pulled in from the English tree
instead of redundant copies
- The base and enbase entities are already automatically generated so
remove inline definitions from individual files
- Fetch the LEGAL file via http instead of depending on CVS
- Convert id names to lowercase to avoid mixing different styles and
for better readability
- All PSGML comments are removed since they are mostly useless
- Convert character entities to normal characters
- Do not copy CSS files but override only necessary part
- Fix build with newest tidy
- Partly update the fdp-primer to reflect changes
Approved by: doceng (implicit)
two different places. In addition the linked instructions are out of
dated.
Don't give bad advice of downloading a single port at a time. This
rarely works and is unsupported.
Approved by: brd
using "ypcat passwd" and towards "getent passwd". With work taking place
on the FreeBSD cluster, the former will eventually start failing.
While here, increase the lowest UID we care about from 100 to 500.
In reality, daemons may get any user ID below 1000, but the FreeBSD
cluster has some longstanding users with IDs in the 500s. At the
very least, this change is no less wrong than the existing code.
Approved by: bcr (mentor)
- Use rel.head.major and rel{,2}.current.major entities instead of
hard-coding version numbers.
- Comment the paragraph stating snapshots will be regularly released.
- Comment the paragraph stating 10-CURRENT, 9-STABLE, and 8-STABLE
snapshots are available.
- Note snapshots may be outdated.
