Suggested paragraph change in Chapter 4 just before figure 4.3.
neilb at idiom.com
neilb at idiom.com
Thu Jul 14 13:45:07 CDT 2011
Ok, that's four terms I am unfamiliar with. Good thing XML
has no terror for me. Learning is good. :-)
When I can I will take a look @ said docs. Being a buildmeister
I suspect I will put together a build environment out of reflex.
Neil
> On 07/06/2011 07:22 PM, Brown, NeilX D wrote:
>> Hi Michael,
>>
>> Re: r3881 cool. Thanks.
>>
>> Re: Index. Can I help? How?
>
> The book sources are all just Docbook XML. I edit them in Emacs, but any
> text editor will do. If you are able to get setup with a build
> environment
> for the book, I think you'll find the mechanics of adding index entries
> fairly easy. I mean, you just drop tags like the following into the code:
>
> <indexterm>
> <primary>svn</primary>
> <secondary>subcommands</secondary>
> <tertiary>update</tertiary>
> </indexterm>
>
> And the build process does the rest.
>
> Information about getting book sources is here:
>
> http://code.google.com/p/svnbook/source/checkout
>
> Information about building the book sources is here:
>
> http://code.google.com/p/svnbook/source/browse/trunk/src/en/README
>
> Conventions we use when hacking on the book sources are here:
>
> http://code.google.com/p/svnbook/source/browse/trunk/src/en/HACKING
>
> Just make your tweaks against the latest trunk sources, run 'svn diff' to
> generate a patch, and mail the patch to this mailing list.
>
> Currently the indexterm tags in the codebase are dropped in before the
> paragraphs which contain their target. A better approach might be to put
> the tags inside the paragraphs, as close to the exact target text as
> possible. But that can complicate 80-column source formatting, so ...
> I've
> not decided to make that leap just yet.
>
> --
> C. Michael Pilato <cmpilato at red-bean.com> | http://cmpilato.blogspot.com/
>
More information about the svnbook-dev
mailing list