finally appeared on the FTP site.
Update the list of FreeBSD releases for which security advisories are
released.
Make mention of the its4 port for security auditing.
Point to http://www.shmoo.com/securecode/ as a useful secure coding
reference site.
sheet definitions for that language only. Each file reads in the defaults
from the master share/sgml/freebsd.dsl file, and adds overrides, or new
definitions, as necessary.
Move the per-language hacks from share/sgml/freebsd.dsl in to
<lang>/share/sgml/freebsd.dsl as necessary.
Add links to the -questions and -doc mailing lists to the bottom of the
generated HTML output for some languages. The -questions link will
become a link to Greg's "Getting the most from questions" document when
I bring that in, but I haven't done that yet, and I didn't want these
patches hanging around my local tree.
This was the real reason for making freebsd.dsl language local, as it
makes it much easier to translate generated text, such as the text of
the links, without polluting share/sgml/freebsd.dsl.
Update doc.docbook.mk to use the new, per-language freebsd.dsl file when
building the docs. While I'm here, update .pdb generation so that it
creates a symlink to ${CURDIR:T}.pdb as well (e.g., the Handbook generates
"book.pdb" and "handbook.pdb"). This makes it easier to install more than
one document on a Palm, because two docs called "book.pdb" or "article.pdb"
can not co-exist.
attributes. We don't use these yet, but they've been hanging around my
tree for ages, and it's time other people got to play with them.
Add (HTML) entity defs for lsquo and rsquo, ` and ' respectively.
page of articles. This necessitates duplicating the entire list in the
customisation layer, which will need to be kept up to date as the master
stylesheets change.
Tidy cannot handle EUC-JP codepoint range correctly with -raw option.
I will try to fix this problem, but temporary disable to use tidy in
Japanese Handbook and FAQ.
is superior, and the various translation teams are fine with it.
Use iSilo instead of pilot-makedoc to produce Palm compatible files. It
works from the HTML and retains the formatting (including the internal
links) making it much nicer to work with than the output from pilot-makedoc.
1. Add .sgml -> .revinc rule in web.mk. This tells how to make SGML
include file which contains revision information.
2. Add ja/revcheck script. This script makes revision information
from English SGML file and localized one.
3. Add *.revinc files into GENDOCS in localized Makefile. This will
generate *.revinc files from each *.sgml files.
4. Add %rev.diff entity into localized includes.sgml.
5. Add statement to include *.revinc for each *.sgml files.
(this will be followed separately.)
Reviewed and not objected by: Doc Team
works, but isn't great (at least in SmartDOC). Still, if you want to carry
the FreeBSD FAQ on your Palm (or the Handbook for that matter) it's a start.
PR: docs/13439
Submitted by: Slaven Rezic <eserte@cs.tu-berlin.de>
