to both directories, and make it relative, rather than absolute.
This fixes the case where you might install the docs under one directory
/foo/bar/..., and then want to migrate them elsewhere (to /usr/share/).
With the old scheme, the symlink would start /foo/bar/..., and would
therefore be broken.
A good example of this happening is "make release" :-)
${FORMATS} on the command line then it would assume that you wanted to
build a document in the current directory, based on the setting of ${DOC}.
If ${DOC} wasn't set, it defaulted to the name of the current directory.
Any Makefile that includes this, and expects to have documentation built
in the current directory must now explicitly define DOC. All the current
ones do anyway. This should be a non-problem when docproj.docbook.mk is
split out in to smaller, more modular files.
Move the comments for DOC from the non-mandatory to the mandatory
section.
2. Clarify the meaning of DESTDIR, it's changed a little bit since it was
first documented.
3. Initial, tentative support for building pkg_* packages from the
formatted documentation. Needs work, but I've had the patch out for
review for a couple of days, and no comments either way -- so if
people hate it, this should at least spur them on to say so.
# cd /path/to/doc/to/turn/into/a/package
# touch COMMENT DESCR
# make 'FORMATS=this that and the other' package
to build 'n' packages, one per format. "make install" is run as part
of the package dependency, so this will overwrite documentation you
have already got installed.
4. Remove DOC_INSTALL_PREFIX. Should have been DOCDIR from the start.
encoding. This is a band aid fix, just to get it built, and will be fixed
properly in the next day or so, when I can properly analyze the problem.
Now to read the e-mail this has generated. . .
It will give the understandable result now.
Discussed with : nik.
o Fix some ANCHOR error, modify some format.
Obtained from : English version 1.6, PR: docs/13349
(Actually English version of FAQ still has some wrong link, I'll send-PR
when free. Any taker?)
o FAQ 2.29 : fiald -> failed
o FAQ 3.x : Make the title more easier to read.(Of course, it is Chinese
title)
o FAQ 10.13 : Delete a extra "W".
o FAQ 12.x : Style police. Use 2-bytes punctuation rather than one. Cleanup
some paragraph.
2. Sync with English version 1.5 (Tue,Aug 24 1999).
Fix up the list of questions and answers as a <qandaset> instead of
an <itemizedlist>. This entails converting the <itemizedlist> element
to a <qandaset>, and wrapping each question paragraph in a <question>
and </question> pair, and each answer in a <answer>...</answer> pair.
Then, search and replace for all the "Q. " and "A. " and remove them,
because the stylesheet adds these for you.
Finally, some of the questions are entered as
<para><anchor id="foo">...
Delete the anchor element, and put the id attribute on the para instead,
so you have
<para id="foo">...
I'm not entirely sure why, but if you have that in the first form then
the stylesheets don't include the links properly in the table of
questions. If you have it in the second form then everything works fine.
Default to labelling questions with "Q:" and answers with "A:" when
processing <qandaset>s. In the HTML output, render questions in a larger,
bolder font than the answers. Requested by several people on -doc.
Default to numbering sections. Requested by one person on -doc, who
seemed somewhat confused that I hadn't read his mind and done this three
months previously.
cvs: ----------------------------------------------------------------------
With his brim pulled way down low
Ain't no sound but the sound of his feet
Machine guns ready to go
Are you ready hey are you ready for this?
Are you hanging on the edge of your seat?
Out of the doorway the bullets rip
To the sound of the beat yeah
Another one bites the dust
Another one bites the dust
And another one gone and another one gone
Another one bites the dust
Hey I'm gonna get you too
Another one bites the dust
...
remains on the ground, and walk lightly over them two or three times.
Removing the other LinuxDoc and two letter country code directories
won't be so graphic, but they'll be as fun.
The first question in the preface, "What is the purpose of this FAQ"
doesn't need to be there (although the contents of the answer do). Remove
the question, and associated markup, but retain the answer.