sgml entities for CPU architectures?
Dmitry Morozovsky
marck at rinet.ru
Sat Sep 22 17:06:10 UTC 2007
On Sat, 22 Sep 2007, Ben Kaduk wrote:
BK> > >> I'm updating my patch to the FAQ (docs/115000) for danger@'s
BK> > >> (somewhat) new daily snapshot
BK> > >> builds, which are specific to x86 and amd64. Should I just use literals for
BK> > >> these architectures, or are the entity-ified somewhere that I haven't found yet?
BK> > >
BK> > > As far as I know, we do not have entities for architectures.
BK> >
BK> > The release documents grew these entities fairly recently...see
BK> > src/release/doc/share/sgml/release.ent (on HEAD only at the moment).
BK>
BK> But is release.ent pulled into the build of books/faq/book.sgml ?
I can see in share/sgml/freebsd.ent:
<!-- Entities for various architectures. These are to be used
only for denoting a variant of FreeBSD for a particular
architecture (e.g. &os;/&arch.i386;). Other entities should
be used when referring generically to an architecture,
particularly because entities such as &i386; properly
denote trademarks and registered trademarks. -->
<!ENTITY arch.alpha "alpha">
<!ENTITY arch.amd64 "amd64">
<!ENTITY arch.arm "arm">
<!ENTITY arch.i386 "i386">
<!ENTITY arch.ia64 "ia64">
<!ENTITY arch.pc98 "pc98">
<!ENTITY arch.powerpc "powerpc">
<!ENTITY arch.sparc64 "sparc64">
<!ENTITY arch.sun4v "sun4v">
This is from rev 1.93 of freebsd.ent:
date: 2007/08/11 19:17:41; author: bmah; state: Exp; lines: +15 -0
Add &arch.*; entities for the various architectures. These
should only be used when referring to a version of FreeBSD on
a specific architecture, e.g. &os;/&arch.i386;. Use other,
already existing entities (such as &i386;) when talking generically
about an architecture, in order to attribute trademarks correctly.
Sincerely,
D.Marck [DM5020, MCK-RIPE, DM3-RIPN]
[ FreeBSD committer: marck at FreeBSD.org ]
------------------------------------------------------------------------
*** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- marck at rinet.ru ***
------------------------------------------------------------------------
More information about the freebsd-doc
mailing list