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 missing ")" to %(formataddr) function.
- Add missing literal tags to "To:" and "Subject:".
- Add missing filename tag to "inbox".
PR: docs/57209
Submitted by: Josef El-Rayes <j.el-rayes@daemon.li>
- Use trademark entities
- Add trademark attributions.
- Always use correct case for trademarks.
- Don't join trademarks with other words, e.g. using hyphens.
trademark.ent:
- Add entities for more trademarks / companies.
- Sort the Sun trademark attribution entity.
enable it in en_US.ISO8859-1/ and ja_JP.eucJP/.
- Add PUBLIC "-//FreeBSD//ENTITIES DocBook Language Specific Entities//EN"
and l10n.ent for entity localization.
- Use share/misc/docbook.css for indentiation of <programlisting>
and <screen>.
- Add some missing $FreeBSD$.
book's author, Jerry Peek, now maintains an online version of this book,
so refer people to that instead. [See the message 'Suggestion: add a
link to your document "An MH Primer"' posted to freebsd-doc on 6th
August 2002]
While I'm here, update a broken link to the MH FAQ.
+ Add a comma to separate parts of existing sentences more clearly.
+ Change "Also you might want" to "You might also want".
+ Remove a duplicate <command>edit</command>.
+ Reword and split sentences, minor other grammar fixes.
internet -> Internet
can not -> cannot
CD-ROM -> CDROM
cdrom -> CDROM
UNIX -> Unix
To be standardized with the rest of the doc tree.
Approved by: murray
in the case of */FAQ/Makefile, because the FAQs are all in the wrong
place. Things still install properly, but some of the directory paths
are hardcoded. This will be going away ASAP.
Yes, this is supposed to be a new top level in the repository.
For the moment any changes to this area must be cleared by myself
or Jordan. Once the kinks are worked out, the policy will probably
be relaxed.
