XML Schema - DocBook XML in detail

Being able to write a document and then create it in a number of different output formats has been a dream of many development teams over the years. This can be achieved through DocBook XML, which not only maintains semantic markup, but also maintains control over data formatting and output. Control semantics can specify the chapters and paragraphs that make up the document. The included items may be specified in further detail within the paragraph. For example, being able to write a document and then create it in many different output formats has been a dream of many development teams for many years. This can be achieved through DocBook
XML, which not only maintains semantic markup, but also maintains control over data formatting and output. Control semantics can specify the chapters and paragraphs that make up the document. The included items may be specified in further detail within the paragraph. For example, you can put the command and
function names in separate tags, as shown in Listing 8.
Listing 8. Wrapping commands and functions in separate tags ​                                                                  

<para>The <command>compile</command> takes the source code of the 

material and builds a new class based on the filename. For example, if the filename is

<filename>HelloWorld</filename> then the name of the class generated will be

<classname>HelloWorld</classname>.

You can choose different output styles and formats when displaying different elements, or you can choose the same style. More importantly, because semantic information is returned (for example, the document may contain a

reference to a class name), it can be used to generate a list (the list) when writing the index Contains all class names detailed in the documentation). In addition to semantic markup, sections and different parts of a document can also be marked with special IDs, and these IDs can be used to establish links to different parts of the document. Some types can be
auto-completed (chapters, sections, and other types that generate a table of contents), others require links to other sections to be established explicitly. These links can be automatically converted into the appropriate format when converted to the target format. For example, the link will be converted to the appropriate HTML page or link to an anchor within the page. If you are generating a PDF, you can include the page number of the target chapter.
This conversion is completed by the
XSLT style sheet. Existing standard DocBook XSLT stylesheets support conversion to standard HTML, XHTML, PDF (via the FO standard), Texinfo, Java™ Help and Man pages. Data can also be transformed into a variety of different sizes and styles, books, A4 pages and slides using standard style sheets. The flexibility of various output formats and markup means that when creating documentation, the same documentation source code can be used to provide printed manuals, embedded help, man pages, online and context-aware information. Using the more traditional
model, these elements can be written separately. DocBook
XML has been widely recognized in the technical article community, and all documents of many companies adopt the DocBook XML standard (or a subset of it).                                                                                              

The above is the detailed content of XML Schema - DocBook XML in detail. For more information, please follow other related articles on the PHP Chinese website!