Re: [docbook-apps] How do I get the generated content to use a specific name

[David Cramer <david@thingbag.net>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Derek,
You'll find some good information about this in Bob Stayton's book.
Regarding how to control the names of chunked files, see:

http://www.sagehill.net/docbookxsl/Chunking.html

When you cross reference to a page using xref with a linkend
attribute, then the link text and target file name are computed
automatically. If you use link and linkend, then just the file name is
computed automatically and you can supply your own link text:

http://www.sagehill.net/docbookxsl/CrossRefs.html

If you want to link between files, you can use olink, but that
requires that you set up an "olink database".

David

On 05/24/2012 02:59 PM, Derek Van Kooten wrote:
> I see some of the samples listed use very specific names for their 
> content. For example
> 
> http://docs.rackspace.com/files/api/v1/cf-devguide/content/Additional_Resources-d1e388.html
>
> 
> 
> Notice how the name of the page is Additional_Resources and the
> content is about Additional Resources.
> 
> When I run the program I get generated names like /ch01s02.html
> 
> Thats all fine and good. But if I have a specific page of content I
> want to link to, I need it to have a name that doesnt change. For
> example, lets say I have a chapter that documents how are invoice
> system works. Well, I would like the name of that generated page to
> be /invoice.html or something like that, so I could then link to it
> from our application.
> 
> Is there some tag or something I can put on that chapter to get the
> name of the page that is generated to be something specific?

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJPvpt9AAoJEMHeSXG7afUhbt0H/RxT5KRdy+NTLPVBUXxDI30v
c2oFzUMUwO1VmLJmYaFEyRdsYWCt/eQR5qI7VEDAAH4pDzZO/G/l9rpFMjtM721E
sxN4SPTJ0QnrpNWA7/VC2ALfIPDRWSLln5BeAnqTI+qbkkgSXkF5LFaMzI3kJdYt
g7me2vp1eREJ/vGv0a5RWpWDZT18UmI9rQ3ZQj4A7SjGychZE/e+8KeMYwhUy7pN
lkyQUNrqqV5qPCyvZ5EHL3vuzxJA+mwuqR2C+2/L4ElZHYCb33Sd8pE01R1NoLub
nlJqPnFyYdAhphDt4pNanc4w3s4rYSYDzgyXbZIKvREJq8AAy1PdrQ+TQ1Gu9I4=
=btwR
-----END PGP SIGNATURE-----