Currently we have articles.ent and books.ent, and
for example, articles.ent can be used by putting the
following lines in the doctype declaration:
<!ENTITY % articles.ent PUBLIC
"-//FreeBSD//ENTITIES DocBook FreeBSD Articles Entity Set//EN">
%articles.ent;
This pulls all of the necessary entities via share/sgml/articles.ent.
The translation teams can customize these entities by redefining
the articles.ent file in <langcode>/share/sgml. See
ja_JP.eucJP/share/sgml for example.
- Add trademark attributions.
- Don't join trademarks with other words, e.g. using hyphens.
- Don't use trademarks as nouns (e.g. don't use "Windows NT's").
Start writing the "FreeBSD PAM Modules" section, which will provide
short descriptions of each of the PAM modules we ship in the base
system, along with recommendations about their use.
Note to translators: more to come in the very near future, so you may
wish to hold back on this one for a while.
Sponsored by: DARPA, NAI Labs
between OpenPAM, Linux-PAM and Solaris PAM in some more detail. Also add
IDs to most sections and their titles, and an appendix listing a sample
conversation function.
Translators: please leave for later, there's still a lot to do.
Sponsored by: DARPA, NAI Labs
bibliography containing multiple bibliodiv's, and move the text
description of the bibliography to an abstract element within the
bibliography tag
o Add a link to OpenPAM's Source Forge Web page.
Sponsored by: DARPA, NAI Labs
- Correct a factual error in the "Transactions" section (which I
wrote mostly off the top of my head)
- Add a note about discrepancies in the original PAM paper to the (as
yet unwritten) "PAM Application Programming" section.
- Fill in the sample PAM application, and make room for an (as yet
unwritten) sample PAM module.
Sponsored by: DARPA, NAI Labs
