An attribute such as xlink:href=”” refers to an arbitrary URL. This is similar to the DocBook 4 ulink element, which was removed in DocBook 5. ULink — A link that addresses its target by means of a URL (Uniform Resource Because DocBook is harmonizing towards XML, this restriction cannot easily be. Keywords: external links, simple XLinks, xlink:href, ulink . if you want to insert a book title with an additional link, in DocBook 4 it has to be written like this.
|Published (Last):||18 February 2009|
|PDF File Size:||4.63 Mb|
|ePub File Size:||4.74 Mb|
|Price:||Free* [*Free Regsitration Required]|
RelaxNG permits an element in different contexts to have different content models. You can assign a role attribute to an annotation to identify it as a certain kind of annotation.
The ulink tag: Linking to a Web page
Because the association is by attributes, an annotation element can be located close to or far from the element it is annotating. In DocBook 4, a bookinfo comes after a book’s title element, but a chapterinfo element comes before a chapter’s title element. This notation is semantically equivalent to an xref. Either direction is sufficient to establish the association.
Setting up the tools. The ulunk may have different content models in different contexts, to manage titled ulinl non-titled elements, for example.
DocBook 5 also adds new concepts. If ylink is a xlink: It has these features:. The problem is that URLs have no spaces, and so will not be line broken on a space. The title can be in either location, but not both. All hierarchical elements and many block elements can have a metadata container. You will need to develop a stylesheet customization if you want to include annotation information in your output. Likewise, DocBook fragments can more easily be embedded in other compound document types.
Re: [docbook] ulink
An alt element is placed as a child of the element it is describing. The way it works is you set uliink stylesheet parameter ulink. That is because the semantics of a particular annotation are defined by the application, not the DocBook schema. An element within that scope is actually in the namespace only if the element’s prefix matches the namespace attribute’s prefix. DocBook 5 has a new system for associating annotations with elements.
The link element contains some text or even other elements: URL link with literal text.
An olink-style link from any element can be formed using two attributes. The link can go to an internal or external destination. In other words, you do not have to use a link element anymore. Regardless of the parameter settings, if the URL exactly matches the ulink text string or the ulink element is empty, which produces the same resultthen the stylesheet does not repeat the same URL in brackets or a footnote.
Creating a link from your DocBook document to a website is easy. When a namespace attribute has no prefix, the namespace becomes the default namespace.
For FO output, you can choose whether the url attribute value for the ulink is printed.
In DocBook 5, most elements that generate some output can be made into a link. For example, the DocBook 5 info element in book can contain a titlebut the info element in para cannot.
That standard says that any XML element can become the source or target of a link if it has the universal XLink attributes on it. The following are some examples:. Setting the namespace as the dlcbook namespace is usually more convenient when creating an entire document in a single namespace, as is typically done with DocBook.
A single info element name is used as the metadata container for all elements. In the following example, the prefix is d:. On the other hand, the XLink attribute xlink: They are each described in more detail in the following sections. It is quite easy to customize in order to extend or subset the DocBook schema. An annotation element’s content can be any mix of DocBook block elements. Element as internal link. Internal link with generated text.
First consult DocBook V5. Its content model is like section but without any nested sections.
The main difference is that the document’s root element must have the DocBook namespace attribute and a schema version attribute. In DocBook 5, elements from DocBook 4 such as bookinfochapterinfodoccbooketc. The following example allows breaks after slash, ampersand, and question mark in a URL, and does not display a hyphen at the break:.
It permits as content only text and inlinemediaobject which is only included to support characters not in the current font. The DocBook stylesheets currently only handle xlink: For example, the DTD version does not permit an element to have different content when the element appears in different contexts.
The olink element itself is retained in DocBook 5. In DocBook 5, the alt element serves ulnik similar function except that it is an element and it can be applied to many elements, not just images.
Instead of ulinkuse a link element with a URL in its xlink: This allows elements from other namespaces to be mixed into DocBook documents without creating element name conflicts.
The universal linking mechanism enables you to create logical links between any two DocBook elements.