1.1 --- a/en/ch06-collab.xml	Mon Mar 09 23:37:29 2009 -0700
     1.2 +++ b/en/ch06-collab.xml	Thu Mar 12 17:12:18 2009 +0800
     1.3 @@ -1,6 +1,6 @@
     1.4  <!-- vim: set filetype=docbkxml shiftwidth=2 autoindent expandtab tw=77 : -->
     1.5  
     1.6 -<chapter id="cha:collab">
     1.7 +<chapter id="cha.collab">
     1.8    <?dbhtml filename="collaborating-with-other-people.html"?>
     1.9    <title>Collaborating with other people</title>
    1.10  
    1.11 @@ -47,12 +47,12 @@
    1.12        first is using the <command role="hg-cmd">hg serve</command>
    1.13        command, which is best suited to short-term
    1.14        <quote>lightweight</quote> serving.  See section <xref
    1.15 -	linkend="sec:collab:serve"/> below for details of how to use
    1.16 +	linkend="sec.collab.serve"/> below for details of how to use
    1.17        this command.  If you have a long-lived repository that you'd
    1.18        like to make permanently available, Mercurial has built-in
    1.19        support for the CGI (Common Gateway Interface) standard, which
    1.20        all common web servers support.  See section <xref
    1.21 -	linkend="sec:collab:cgi"/> for details of CGI
    1.22 +	linkend="sec.collab.cgi"/> for details of CGI
    1.23        configuration.</para>
    1.24  
    1.25    </sect1>
    1.26 @@ -120,7 +120,7 @@
    1.27  	  role="hg-cmd">hg serve</command> does not require any fancy
    1.28  	server infrastructure.  You can get started with <command
    1.29  	  role="hg-cmd">hg serve</command> in moments, by reading
    1.30 -	section <xref linkend="sec:collab:serve"/> below.  Then simply
    1.31 +	section <xref linkend="sec.collab.serve"/> below.  Then simply
    1.32  	tell
    1.33  	the person next to you that you're running a server, send the
    1.34  	URL to them in an instant message, and you immediately have a
    1.35 @@ -165,9 +165,9 @@
    1.36        <para>In this kind of scenario, people usually use the
    1.37  	<command>ssh</command> protocol to securely push changes to
    1.38  	the central repository, as documented in section <xref
    1.39 -	  linkend="sec:collab:ssh"/>.  It's also
    1.40 +	  linkend="sec.collab.ssh"/>.  It's also
    1.41  	usual to publish a read-only copy of the repository over HTTP
    1.42 -	using CGI, as in section <xref linkend="sec:collab:cgi"/>.
    1.43 +	using CGI, as in section <xref linkend="sec.collab.cgi"/>.
    1.44  	Publishing over HTTP
    1.45  	satisfies the needs of people who don't have push access, and
    1.46  	those who want to use web browsers to browse the repository's
    1.47 @@ -270,9 +270,9 @@
    1.48  	People working on an individual branch are typically quite
    1.49  	isolated from developments on other branches.</para>
    1.50  
    1.51 -      <informalfigure id="fig:collab:feature-branches">
    1.52 +      <informalfigure id="fig.collab.feature-branches">
    1.53  	<mediaobject><imageobject><imagedata
    1.54 -				    fileref="feature-branches"/></imageobject><textobject><phrase>XXX 
    1.55 +				    fileref="images/feature-branches.png"/></imageobject><textobject><phrase>XXX 
    1.56  	      add text</phrase></textobject><caption><para>Feature
    1.57  	      branches</para></caption></mediaobject>
    1.58        </informalfigure>
    1.59 @@ -408,7 +408,7 @@
    1.60  	in which your team may be moving at once.  Even though this
    1.61  	subject is intimately related to how your team collaborates,
    1.62  	it's dense enough to merit treatment of its own, in chapter
    1.63 -	<xref linkend="chap:branch"/>.</para>
    1.64 +	<xref linkend="chap.branch"/>.</para>
    1.65  
    1.66      </sect2>
    1.67    </sect1>
    1.68 @@ -419,7 +419,7 @@
    1.69        serving data to your collaborators.</para>
    1.70  
    1.71    </sect1>
    1.72 -  <sect1 id="sec:collab:serve">
    1.73 +  <sect1 id="sec.collab.serve">
    1.74      <title>Informal sharing with <command role="hg-cmd">hg
    1.75  	serve</command></title>
    1.76  
    1.77 @@ -498,7 +498,7 @@
    1.78  
    1.79      </sect2>
    1.80    </sect1>
    1.81 -  <sect1 id="sec:collab:ssh">
    1.82 +  <sect1 id="sec.collab.ssh">
    1.83      <title>Using the Secure Shell (ssh) protocol</title>
    1.84  
    1.85      <para>You can pull and push changes securely over a network
    1.86 @@ -859,7 +859,7 @@
    1.87  
    1.88      </sect2>
    1.89    </sect1>
    1.90 -  <sect1 id="sec:collab:cgi">
    1.91 +  <sect1 id="sec.collab.cgi">
    1.92      <title>Serving over HTTP using CGI</title>
    1.93  
    1.94      <para>Depending on how ambitious you are, configuring Mercurial's
    1.95 @@ -951,7 +951,7 @@
    1.96  	must not be writable by others.</para>
    1.97        <programlisting>chmod 755 ~/public_html</programlisting>
    1.98  
    1.99 -      <sect3 id="sec:collab:wtf">
   1.100 +      <sect3 id="sec.collab.wtf">
   1.101  	<title>What could <emphasis>possibly</emphasis> go
   1.102  	  wrong?</title>
   1.103  
   1.104 @@ -1118,7 +1118,7 @@
   1.105  	display an empty list of repositories.  If you get a blank
   1.106  	window or error message, try walking through the list of
   1.107  	potential problems in section <xref
   1.108 -	  linkend="sec:collab:wtf"/>.</para>
   1.109 +	  linkend="sec.collab.wtf"/>.</para>
   1.110  
   1.111        <para>The <filename role="special">hgwebdir.cgi</filename>
   1.112  	script relies on an external configuration file.  By default,
   1.113 @@ -1317,7 +1317,7 @@
   1.114  	    <literal>default</literal> and <literal>gitweb</literal>
   1.115  	    (the latter is much more visually attractive).  You can
   1.116  	    also specify a custom template of your own; see chapter
   1.117 -	    <xref linkend="chap:template"/> for details.
   1.118 +	    <xref linkend="chap.template"/> for details.
   1.119  	    Here, you can see how to enable the
   1.120  	    <literal>gitweb</literal> style.</para>
   1.121  	  <programlisting>[web] style = gitweb</programlisting>