and near it. Most of the time this consisted of replacing the <emphasis>
with <replaceable> or <userinput>. Sometimes <screen> is the wrong element
to use, and will need replacing with something like <programlisting> or
<literallayout>.
command(number)) from the variety of different existing markup
(which included <command>, <emphasis>, and <ulink>s to man2html
CGI scripts) to a common format, which is
<citerefentry>
<refentrytitle>command</refentrytitle>
<manvolnum>number</manvolnum>
</citerefentry>
although in the interests of keeping the changes as simple as possible
for the translators, the above was flattened on to one line.
to link to it any more, and the version on my website is currently more
up to date. An AltaVista search to see if any one else had linked to it
didn't turn up anything, so I think this is pretty safe. I'll 'cvs remove'
the directory and its files shortly.
them with the correct markup.
The only quotes left now are either around items for which I'm not 100%
sure which element to use, or in literal blocks as part of commands the
user types in.
so I can check my progress, partly so that others can offer comments on
the result of the conversion.
See <URL:http://www.freebsd.org/~nik/handbook/book01.htm> for the first
results. Keep in mind that the conversion has not been fine tuned in any
way. That said, comments are welcome.
The file:/usr/src/sys/i386/boot/biosboot/README.386BSD is probably false,
but I don't have a checked out tree at hand, and I'd rather would let that
point to some http or ftp source (at least alternatively). Will check later
today.
Submitted by: "SSC Webmaster" <wwwadmin@ssc.com>
markup something that looks like a filename as <filename>...</filename>,
rather than <emphasis role="tt">...</emphasis> or whatever.
These changes can not be automated, the Japanese team will need to go
through the diffs to see which bits of markup have changed.
I'm halfway through (line 16704). It's been quite instructive, and I'm
learning lots about printing with FreeBSD :-)
Join me tomorrow, when I'll be doing the same thing to the other half of
the Handbook -- same Bat time, same Bat channel.
in English, to be consistent with the doc/ja/ hierarchy.
Rather than moving the existing FAQ and Handbook over to this directory,
they will be converted to the DocBook DTD, and the results of the conversion
will be committed to this new hierarchy. The existing doc/faq and
doc/handbook can then be removed.
The README file will be used to explain the current state of the DocBook
conversion process for the Handbook, so that people without easy access
to the CVS logs can keep track of what's going on, and lend a hand where
appropriate.
I plan to start converting the Handbook around 1830 BST.
clean up the build process a wee bit.
The basic change: instead of cheacking out bits and pieces of the
doc tree into the web build tree, check out the doc tree somewhere
else and put in a few symlinks from the web tree to the doc tree.
On catfish (soon to be hub) for example:
/usr/local/www/build/doc/...
/usr/local/www/build/www/...
where
/usr/local/www/build/www/data/handbook -> ../../doc/handbook
You have to manually put in the symlinks at the moment, but it
works better than the evil CVS hackery.
Also, install with -C to help avoid gratuitous cache-busting due to
gratuitous timestamp twiddling.
