From: Steve Ball Date: Tue, 10 Jun 2008 11:39:44 +0000 (+0000) Subject: Updated specification. X-Git-Tag: release/1.79.1~6^2~1315 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=f26f766043ef59a2f7281a4510215f2f2880c371;p=docbook-dsssl Updated specification. to-DocBook: add cols attribute to tgroup from-DocBook: fix for blockquote title --- diff --git a/xsl/roundtrip/blocks2dbk.xsl b/xsl/roundtrip/blocks2dbk.xsl index debeb7538..f6a68c76e 100644 --- a/xsl/roundtrip/blocks2dbk.xsl +++ b/xsl/roundtrip/blocks2dbk.xsl @@ -1198,7 +1198,47 @@ - + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/xsl/roundtrip/dbk2wp.xsl b/xsl/roundtrip/dbk2wp.xsl index 3ae434862..241048af4 100644 --- a/xsl/roundtrip/dbk2wp.xsl +++ b/xsl/roundtrip/dbk2wp.xsl @@ -887,7 +887,8 @@ - + diff --git a/xsl/roundtrip/specifications.xml b/xsl/roundtrip/specifications.xml index 4af252494..85db866e1 100644 --- a/xsl/roundtrip/specifications.xml +++ b/xsl/roundtrip/specifications.xml @@ -1,6 +1,6 @@ - -
- + +
+ Round-Tripping Specifications Bob @@ -18,63 +18,69 @@ - 1.7 - 2008-02-22 - SRB - Added edition. + 1.8 + 2008-05-22 + SRB + Updated for current implementation. - 1.6 - 2007-10-19 - SRB - Added keyword. + 1.7 + 2008-02-22 + SRB + Added edition. - 1.5 - 2007-01-05 - SRB - Reduce emphasis on WordML, add support for OpenOffice. + 1.6 + 2007-10-19 + SRB + Added keyword. - 1.4 - 2005-11-11 - SRB - Added bibliography. + 1.5 + 2007-01-05 + SRB + Reduce emphasis on WordML, add support for OpenOffice. - 1.3 - 2005-10-31 - SRB - Added mediaobjectco, imageobjectco, programlistingco, areaspec, area, calloutlist. + 1.4 + 2005-11-11 + SRB + Added bibliography. - 1.2 - 2005-10-13 - SRB - Version prior to using revhistory. + 1.3 + 2005-10-31 + SRB + Added mediaobjectco, imageobjectco, programlistingco, areaspec, area, calloutlist. + + + 1.2 + 2005-10-13 + SRB + Version prior to using revhistory. - + - This document specifies how DocBook elements can be mapped to paragraph and character styles in a word processor. The specifications will be used to write conversions between DocBook XML and word processor XML formats, such as Microsoft's WordProcessingML (WordML), OpenOffice's OpenDocument and Apple's Pages. + This document specifies how DocBook elements are mapped to paragraph and character styles in a word processor. The specifications are used to write conversions between DocBook XML and word processor XML formats, such as Microsoft's WordProcessingML (WordML), OpenOffice's OpenDocument and Apple's Pages.
Introduction - Microsoft Word 2003 introduced WordProcessingML (WordML), an XML vocabulary for Word documents. Since then, other popular word processors have become available that use XML as their data representation, namely Apple's Pages and OpenOffice. By converting Word (or OpenOffice or Pages) to XML, it becomes possible to convert a word processing document to DocBook and vice versa using XSL transformations. Such conversions would then enable the following. + Microsoft Word 2003 introduced WordProcessingML (WordML), an XML vocabulary for Word documents. Since then, other popular word processors have become available that use XML as their data representation, namely Apple's Pages and OpenOffice. By converting Word (or OpenOffice or Pages) to XML, it becomes possible to convert a word processing document to DocBook and vice versa using XSL transformations. Such conversions then enable the following. - DocBook content creators could write in their familiar wordprocessing application, rather than learning a new XML editing application. + DocBook content creators write in their familiar wordprocessing application, rather than learning a new XML editing application. - DocBook XML documents could be styled for output using the typesetting features of the word processor. + DocBook XML documents can be styled for output using the typesetting features of the word processor. Word processors have a simple, flat data model; documents consist of paragraphs (and tables) and paragraphs contain text and character spans. All word processors allow styles to be associated with paragraphs and spans. - This specification describes how DocBook elements could map to a set of paragraph and character styles. It defines a specific set of style names for which a Word style template can be created. The style names would also be used in XSLT template match patterns for conversion. Although originally targetted to MS Word, the system has subsequently been extended to use other word processors, notably Apple's Pages. + This specification describes how DocBook elements map to a set of paragraph and character styles. It defines a specific set of style names for which a Word style template can be created. The style names are also used in XSLT template match patterns for conversion. Although originally targetted to MS Word, the system has subsequently been extended to use other word processors, notably Apple's Pages and Open Office.
Project goals - The goal of this project is to enable a word processor, such as Microsoft Word, to be used with DocBook files. The specific goals include: + The goal of this project is to enable a word processor, such as, but not limited to, Microsoft Word, to be used with DocBook files. The specific goals include: Enable authoring of basic DocBook documents in the word processor. @@ -83,10 +89,10 @@ Enable importing of basic DocBook XML documents into the word processor. - To meet these goals, the project will produce a toolkit that can be immediately put to use. The kit will include: + To meet these goals, the project provides a toolkit that can be immediately put to use. The kit includes: - Templates for Microsoft Word, Apple Pages and OpenOffice with formatting styles attached to the style names. + Templates for Microsoft Word, Apple Pages and Open Office with formatting styles attached to the style names. XSLT stylesheets that convert a word processing document that is authored with the corresponding template into a DocBook XML file. @@ -97,9 +103,10 @@
Why basic DocBook? - It isn't clear that this project will ever be able to support all DocBook elements and structure. The project will initially focus on a basic set of commonly used DocBook elements to demonstrate the feasibility and usefulness of using a word processor with DocBook. - One problem facing this conversion project is the sheer number of DocBook elements, over 400 in DocBook 4.3. To support DocBook structural models, several of the elements will require more than one paragraph or character style. This could lead to a very long and unwieldy list of styles in the word processor interface. That would make authoring less efficient and discourage users. - So this project assumes that authors who need the full set of DocBook elements will use an XML authoring tool that better supports them. This project will enable authors to write basic DocBook documents using a word processor. Because Microsoft Word is so widespread, this project will help a lot of new DocBook users get started with familiar tools. They can then graduate to more advanced tools as their needs develop. + This project will never be able to support all DocBook elements and structure. Take, for example, the address element. This element can be used both as a block element for metadata. It can also be used as a phrase level element in a block parent, such as the affiliation element. To make matters worse, it can itself contain phrase level markup, such as personname. No word processor allows character styles to be nested. + The project will initially focus on a basic set of commonly used DocBook elements in order to create a useful editing environment that utilises a word processor with DocBook. + One problem facing this conversion project is the sheer number of DocBook elements, over 400 in DocBook 5.0. To support DocBook structural models, several of the elements require more than one paragraph or character style. This would lead to very long and unwieldy list of styles in the word processor interface. That would make authoring less efficient and discourage users. + Accordingly, this project assumes that authors who need the full set of DocBook elements and structures will use an XML authoring tool that better supports them. This project is focused on authors who wish to write basic DocBook documents using a word processor. Because Microsoft Word is so widespread, it is hoped that this project will help a lot of new DocBook users get started with familiar tools. They can then graduate to more advanced tools as their needs develop.
@@ -109,9 +116,6 @@ Support of versions of Word that do not feature reading/writing WordML (XML). That is, all versions prior to Word 11 (Office 2003). - - Supporting user-defined style names. However, this system should not prevent, or make difficult, adding such support via a customisation layer. - Support of arbitrarily defined styles. This system may expect certain styles to be defined in a particular fashion (in particular, those defining the title of components and divisions). @@ -120,614 +124,1297 @@
Mapping elements to styles Although WordML, OpenDocument and DocBook are all XML, there several challenges when trying to convert between them. - The basic problem in mapping paragraph/character styles to DocBook elements is that word processor documents support far less structure than DocBook. DocBook permits nesting of elements within other elements, providing multiple levels of context for each element. - Word's only structural feature is the outlining mode. In Word outlining, certain paragraph styles are assigned outline levels. When a user applies those styles, they effectively create logical structure in the Word document. Unfortunately, Word itself attempts to automatically determine which paragraphs are headings, and so this method is unreliable. - Instead of relying on Word's built-in outlining mode, this system uses only the names of paragraph styles to determine document structure. Certain heuristics are applied to build the DocBook element structure from the (relatively flat) word processing structure. Titles and other features are used to mark the beginning of a structure, and all paragraphs following that are included in that structure until the beginning of the next structure is found. Problems may arise when a structure should end, but there is no word processor feature that marks the endpoint. - Nesting of block elements is another commonly used feature of DocBook. It is not possible to use Word's outline mode for blocks if it is being used for components and sections. So in this specification, nesting of block elements is indicated by adding a number suffix to a style. So a paragraph with style orderedlist2 is considered to be contained within a preceding paragraph with style listitem. In the word processor, paragraph indent levels will be used to visually indicate nesting of blocks. - Nesting of inline DocBook elements is particularly difficult to support because word processors do not nest character styles. That means a nested inline would require a separate character style to indicate the parent-child relationship. Given the large number of combinations possible, a prohibitively large number of character styles would have to be created. In this project, nesting of character styles will not be supported in the first release. Nested inlines being imported from DocBook will be converted to a sequence of single-name character styles. - In many cases, DocBook structure can be derived from the flat sequence of paragraphs based on sibling relationships. For example, when a paragraph styled as para is followed by a paragraph styled as itemizedlist, the conversion to DocBook will output a para element and then start an itemizedlist element, with the second paragraph as its first listitem. All itemizedlist paragraphs that follow without interruption are put in the same itemizedlist element. - Some combinations of elements cannot be supported (at least not with the techniques as described in this document). An example is informalexample and its permitted content; there is no title to mark the beginning of the element and no marker for the end of the element, also there are too many parent-child combinations to reasonably define style names. - Here are the design principles used in this project for selecting paragraph/character style names: + The basic problem in mapping paragraph/character styles to DocBook elements is that word processor documents support far less structure than DocBook. DocBook permits nesting of elements within other elements, providing multiple levels of context for each element. + Word's only structural feature is the outlining mode. In Word outlining, certain paragraph styles are assigned outline levels. When a user applies those styles, they effectively create logical structure in the Word document. Unfortunately, Word itself attempts to automatically determine which paragraphs are headings, rendering this method is unreliable. + Instead of relying on Word's built-in outlining mode, this system uses only the names of paragraph styles to determine document structure. Certain heuristics are applied to build the DocBook element structure from the (relatively flat) word processing structure. Titles and other features are used to mark the beginning of a structure and all paragraphs following that are included in that structure until the beginning of the next structure is found. That is, the beginning of one structure marks the end of the previous structure. + Problems may arise when a structure should end, but there is no word processor feature that marks the endpoint. To mark the end of a feature an empty paragraph is used. + Nesting of block elements is another commonly used feature of DocBook. It is not possible to use Word's outline mode for blocks if it is being used for components and sections. So in this specification, nesting of block elements is indicated by adding a number suffix to a style. So a paragraph with style orderedlist2 is considered to be contained within a preceding paragraph with style orderedlist1 or itemizedlist1. Where appropriate in the word processor, paragraph indent levels are used to visually indicate nesting of blocks. + Nesting of inline DocBook elements is particularly difficult to support because word processors do not nest character styles. That means a nested inline would require a separate character style to indicate the parent-child relationship. Given the large number of combinations possible, a prohibitively large number of character styles would have to be created. In this project, nesting of character styles is not supported. Nested inlines being imported from DocBook will be converted to a sequence of single-name character styles, where possible, or rejected. + In many cases, DocBook structure can be derived from the flat sequence of paragraphs based on sibling relationships. For example, when a paragraph styled as para is followed by a paragraph styled as itemizedlist1, the conversion to DocBook will output a para element and then start an itemizedlist element, with the second paragraph as its first listitem. All itemizedlist1 paragraphs that follow without interruption are inserted into the same itemizedlist element. + Some combinations of elements cannot be supported (at least not with the techniques as described in this document). An example is informalexample and its permitted content; there is no title to mark the beginning of the element and no marker for the end of the element, also there are too many parent-child combinations to reasonably define style names. + The design principles used in this project for selecting paragraph/character style names are as follows: - Where Word (or OpenOffice or Pages), by default, has a style or feature that corresponds directly to a DocBook element then that style or feature will be used (and documented in this document). For example, the Normal paragraph style maps to a DocBook para element, and a Word table (w:tbl) maps to a DocBook tableIn some cases Word may posess a feature, but it doesn't function in an acceptable manner. For example, lists. In these cases the feature is to be avoided, and a workaround provided.. + Where Word (or OpenOffice or Pages), by default, has a style or feature that corresponds directly to a DocBook element then that style or feature will be used (and documented in this document). For example, the Normal paragraph style maps to a DocBook para element, and a Word table (w:tbl) maps to a DocBook tableIn some cases Word may posess a feature, but it doesn't function in an acceptable manner. For example, lists. In these cases the feature is to be avoided, and a workaround provided.. - Paragraph and character style names will match DocBook element names as much as possible. This will enable authors to learn DocBook element names, and help debug problems with conversion. + Paragraph and character style names will match DocBook element names as much as possible. This will enable authors to learn DocBook element names and help debug problems with conversion. - A style may indicate a parent-child relationship, but the paragraph for such an element may only occur after a paragraph that denotes the beginning of the parent structure. In this case the element name is used as the style name. For example, a personblurb paragraph may only occur after an author, editor or othercontrib paragraph. If a paragraph occurs without the appropriate preceding paragraph, then an error is signalled. + A style may indicate a parent-child relationship, but the paragraph for such an element may only occur after a paragraph that denotes the beginning of the parent structure. In this case the element name is used as the style name. For example, a personblurb paragraph may only occur after an author, editor or othercontrib paragraph. If a paragraph occurs without the appropriate preceding paragraph, then an error is signalled. - Some styles may also indicate a parent-child relationship, but either the parent structure is ambiguous or the paragraph starts the parent structure. For example, chapter-title indicates that the paragraph is a title whose DocBook parent is a chapter. + Some styles may also indicate a parent-child relationship, but either the parent structure is ambiguous or the paragraph starts the parent structure. For example, chapter-title indicates that the paragraph is a title element whose DocBook parent is a chapter element. - Some style names are simplified to make them easier to use in the word processor. For example, a paragraph in an orderedlist requires three elements in DocBook: orderedlist, listitem, and para. The paragraph style name in Word is shortened from orderedlist-listitem-para to just orderedlist. In the case of lists (see below), the list level is appended so this example becomes orderedlist1 + Some style names are simplified to make them easier to use in the word processor. For example, a paragraph in an orderedlist requires three elements in DocBook: orderedlist, listitem, and para. The paragraph style name in Word is shortened from orderedlist-listitem-para to just orderedlist1 (for a first level list). In the case of lists (see below), the list level is appended, which is why this example becomes orderedlist1. Style names with a number suffix indicate a nesting level, as described above. - Style names with continue indicate that the paragraph is part of the preceding element. For example, a para paragraph is used for a single paragraph para element. This would cause any preceding list to be closed. If a list item in the preceding list is to contain more than one paragraph, then the subsequent paragraphs in the word processor document would get a para-continue style. + Style names with continue indicate that the paragraph is part of the preceding element. For example, a para paragraph is used for a single paragraph para element. This causes any preceding list to be closed. If a list item in the preceding list is to contain more than one paragraph, then the subsequent paragraphs in the word processor documentmust use the para-continue style. - Character styles map to elements that are children of the element for the paragraph, hence there is no need to encode parent-child relationships. For example, a surname character style in an author paragraph becomes a surname child element of the author element. + Character styles map to elements that are children of the element for the paragraph, hence there is no need to encode parent-child relationships. For example, a surname character style in an author paragraph becomes a surname child element of the author element. - Empty paragraph and character styles are ignored. + Empty paragraph and character styles are ignored. This can be useful to end structures. - The first paragraph style in the word processor document is used to define the root element of the DocBook document. For example, if the document starts with book-title, then the DocBook document will have book as its root element. All the rest of the document content will be contained in that root element. + The first paragraph style in the word processor document is used to define the root element of the DocBook document. For example, if the document starts with book-title, then the DocBook document will have book element as its root element. All the rest of the document content will be contained in that root element. - Sequential structures are coalesced into a single parent element. For example, a sequence of itemizedlist paragraphs becomes a single itemizedlist element with several listitem children. + Sequential structures are coalesced into a single parent element. For example, a sequence of itemizedlist1 paragraphs becomes a single itemizedlist element with several listitem element children. DocBook to Paragraph/Character Styles - - - + + + - DocBook element - Style(s) - Comments + + DocBook element + + + Style(s) + + + Comments + - Components and sections + + Components and sections + - book/bookinfo/title - book-title - + + book/info/title + + + book-title + + + + - book/bookinfo/subtitle - book-subtitle - + + book/info/subtitle + + + book-subtitle + + + + - book/bookinfo/titleabbrev - book-titleabbrev - + + book/info/titleabbrev + + + book-titleabbrev + + + + - chapter/chapterinfo/title - chapter-title - Assigned Word outline level 1. + + chapter/info/title + + + chapter-title + + + Assigned Word outline level 1. + - chapter/chapterinfo/subtitle - chapter-subtitle - + + chapter/info/subtitle + + + chapter-subtitle + + + + - chapter/chapterinfo/titleabbrev - chapter-titleabbrev - + + chapter/info/titleabbrev + + + chapter-titleabbrev + + + + + + + + appendix/info/title + + + appendix-title + + + Assigned Word outline level 1. + - appendix/appendixinfo/title - appendix-title - Assigned Word outline level 1. + + preface/info/title + + + preface-title + + + Assigned Word outline level 1. + + + + + article/info/title + + + article-title + + + Assigned Word outline level 1. + + + + + article/info/subtitle + + + article-subtitle + + + + + + + + article/info/titleabbrev + + + article-titleabbrev + + + + - preface/prefaceinfo/title - preface-title - Assigned Word outline level 1. + + bibliography/info/title + + + bibliography-title + + + Assigned Word outline level 1. + - article/articleinfo/title - article-title - Assigned Word outline level 1. + + bibliography/bibliodiv/info/title + + + bibliodiv-title + + + + - article/articleinfo/subtitle - article-subtitle - + + biblioentry/title + + + biblioentry-title + + + Metadata elements after the biblioentry-title paragraph become part of the biblioentry. + - article/articleinfo/titleabbrev - article-titleabbrev - + + glossary/info/title + + + glossary-title + + + Assigned Word outline level 1. + - bibliography/bibliographyinfo/title - bibliography-title - Assigned Word outline level 1. + + index/info/title + + + index-title + + + Assigned Word outline level 1. + - bibliography/bibliodiv - bibliodiv-title - + + part/info/title + + + part-title + + + + - biblioentry - biblioentry-title - Metadata elements after the biblioentry-title paragraph become part of the biblioentry. + + section + + + + + + Unnumbered section elements are translated into their equivalent numbered paragraph style. Sections 6 levels and deeper are reported as an error. + - glossary/glossaryinfo/title - glossary-title - Assigned Word outline level 1. + + sect1/info/title + + + sect1-title + + + Assigned Word outline level 2. + - index/indexinfo/title - index-title - Assigned Word outline level 1. + + sect1/info/subtitle + + + sect1-subtitle + + + + - sect1/sect1info/title - sect1-title - Assigned Word outline level 2. + + sect2/info/title + + + sect2-title + + + Assigned Word outline level 3. + - sect1/sect1info/subtitle - sect1-subtitle - + + sect2/info/subtitle + + + sect2-subtitle + + + + - sect1/sect1info/titleabbrev - sect1-titleabbrev - + + sect3/info/title + + + sect3-title + + + Assigned Word outline level 4. + - sect2/sect2info/title - sect2-title - Assigned Word outline level 3. + + sect3/info/subtitle + + + sect3-subtitle + + + + - sect2/sect2info/subtitle - sect2-subtitle - + + sect4/info/title + + + sect4-title + + + Assigned Word outline level 5. + - sect2/sect2info/titleabbrev - sect2-titleabbrev - + + sect4/info/subtitle + + + sect4-subtitle + + + + - sect3/sect3info/title - sect3-title - Assigned Word outline level 4. + + sect5/info/title + + + sect5-title + + + Assigned Word outline level 6. + - sect3/sect3info/subtitle - sect3-subtitle - + + sect5/info/subtitle + + + sect5-subtitle + + + + - sect3/sect3info/titleabbrev - sect3-titleabbrev - + + simplesect/info/title + + + simplesect-title + + + + - sect4/sect4info/title - sect4-title - Assigned Word outline level 5. + + simplesect/info/subtitle + + + simplesect-subtitle + + + + - sect4/sect4info/subtitle - sect4-subtitle - + + bridgehead + + + bridgehead + + + + - sect4/sect4info/titleabbrev - sect4-titleabbrev - + + + Metadata elements + + - sect5/sect5info/title - sect5-title - Assigned Word outline level 6. + + abstract/title + + + abstract-title + + . - sect5/sect5info/subtitle - sect5-subtitle - + + abstract/para + + + abstract + + + + - sect5/sect5info/titleabbrev - sect5-titleabbrev - + + affiliation + + + affiliation + + + + - section - sectN-title - Unnumbered sections are mapped to their numbered equivalent. A parameter (named?) may be set to map numbered sections (sect1, etc) back to unnumbered sections. + + address + + + address + + + + - - Metadata elements + + author + + + author + + + - edition - edition - + + date + + + date + + + + - - Block-level elements + + edition + + + edition + + + - para - para, Normal - Any Word paragraph with style Normal will also be converted to a para element. + + legalnotice + + + legalnotice + + + + - abstract - abstract,abstract-title - abstract/para. + + pubdate + + + pubdate + + + + - note/para - note - Consecutive paragraphs with style "note" after the first note are to be treated as part of the same note element. That is, consecutive notes are coalesced. + + publisher/pubishername + + + publisher + + + + - note/title - note-title - + + publisher/address + + + publisher-address + + + + - caution/para - caution - Consecutive cautions are coalesced. + + revhistory/revision + + + revision + + + + - warning/para - warning - Consecutive warnings are coalesced. + + + Block-level elements + + - important/para - important - Consecutive importants are coalesced. + + para + + + para, Normal + + + Any Word paragraph with style Normal will also be converted to a para element. + - tip/para - tip - Consecutive tips are coalesced. + + formalpara/title + + + formalpara-title + + + + - itemizedlist/listitem/para + + formalpara/para + - itemizedlist1 -itemizedlist1 -itemizedlist2 -itemizedlist3 -itemizedlist4 + formalpara + + + - A number suffix indicates a nesting level within other lists. - orderedlist/listitem/para + + simpara + - orderedlist1 -orderedlist1 -orderedlist2 -orderedlist3 -orderedlist4 + simpara + + + - - variablelist/varlistentry/term + + note/title + - variablelist1-term -variablelist2-term -variablelist3-term -variablelist4-term -variablelist5-term + note-title + + + - A variablelist in Word should be a sequence of alternating paragraphs styled as variablelist-term and variablelist. - variablelist/varlistentry/listitem/para + + note/para + - variablelist1 -variablelist1 -variablelist2 -variablelist3 -variablelist4 + note + + + Consecutive paragraphs with style note after the first note are to be treated as part of the same note element. That is, consecutive notes are coalesced. The note may or may not have a title. - - listitem/para[position() != 1] - para-continue - This paragraph is included in the immediately preceding listitem. + + caution/title + + + caution-title + + + + - example with title and programlisting children - example-title followed by programlisting - + + caution/para + + + caution + + + Consecutive cautions are coalesced. + - example with title and literallayout children - example-title followed by literallayout - + + warning/title + + + warning-title + + + + - example with title and mediaobject children - example-title followed by image styled with example style - + + warning/para + + + warning + + + Consecutive warnings are coalesced. + - figure with title and programlisting children - figure-title followed by programlisting - + + important/title + + + important-title + + + + - figure with title and literallayout children - figure-title followed by literallayout - + + important/para + + + important + + + Consecutive importants are coalesced. + - figure with title and mediaobject children - figure-title followed by image styled with figure style - + + tip/title + + + tip-title + + + + - informalfigure - image tagged as figure style - with no figure-title above or below + + tip/para + + + tip + + + Consecutive tips are coalesced. + - informalfigure/mediaobject/imageobject/imagedata/@fileref - informalfigure-imagedata - The content of the paragraph is taken as the URI for the image. For use in cases where the image is not embedded in the Word document. + + itemizedlist/listitem/para + + + + itemizedlist1 +itemizedlist2 +itemizedlist3 +itemizedlist4 + + + + A number suffix indicates a nesting level within other lists. + - - mediaobject|imageobject - imageobject-imagedata, caption - The content of the imageobject-imagedata paragraph is taken as the URI for the image. May be followed by a caption style paragraph. - - mediaobjectco/imageobjectco/*[self::imagedata/@fileref|areaspec|calloutlist] - mediaobjectco-title, imageobjectco-imagedata, areaspec, area, callout - The content of the imageobjectco-imagedata paragraph is taken as the URI for the image. May be preceded by areaspec and area paragraphs, and followed by callout paragraphs (these are ignored if not associated with an imageobjectco or programlistingco). areaspec and area are normally empty paragraphs, but may have attributes encoded in the usual fashion. callout paragraphs are collected together into a calloutlist, and may have nested lists. + + orderedlist/listitem/para + + + + orderedlist1 +orderedlist2 +orderedlist3 +orderedlist4 + + + + + - programlistingco/*[self::programlisting|areaspec|calloutlist] - programlistingco, areaspec, area, callout - programlistingco may be preceded by areaspec and area paragraphs, and followed by callout paragraphs (these are ignored if not associated with an imageobjectco or programlistingco). areaspec and area are normally empty paragraphs, but may have attributes encoded in the usual fashion. callout paragraphs are collected together into a calloutlist, and may have nested lists. + + listitem/para[position() != 1] + + + para-continue + + + This paragraph is included in the immediately preceding listitem. + - table - Word table - + + example/title + + + example-title + + + All content following the title is included in the example element. The end of the example content is marked by a caption paragraph or an empty paragraph if there is no caption. + - table/title - table-title - + + figure/title + + + figure-title + + + All content following the title is included in the figure element. Metadata must immediately follow the title. The end of the figure content is marked by a caption paragraph or an empty paragraph if there is no caption. + - informaltable - Word table - with no table-title above or below + + informalfigure/mediaobject/imageobject/imagedata/@fileref + + + informalfigure-imagedata, caption + + + The content of the imageobject-imagedata paragraph is taken as the URI for the image. Metadata may immediately follow the paragraph. + - literallayout - literallayout - Inside a literallayout paragraph in Word, lines should be separated by line break (Shift-Enter) rather than paragraph break (Enter). + + mediaobject/imageobject/imagedata/@fileref + + + imageobject-imagedata, caption + + + The content of the imageobject-imagedata paragraph is taken as the URI for the image. May be followed by a caption style paragraph. Metadata may immediately follow the paragraph, before the caption, if any. + - programlisting - programlisting - Inside a programlisting paragraph in Word, lines should be separated by line break (Shift-Enter) rather than paragraph break (Enter). Tabs are not supported. + + table + + + Word table, caption + + + + - blockquote/para - blockquote - + + table/title + + + table-title, caption + + + Metadata may immediately follow the paragraph. + - blockquote/title - blockquote-title - Should immediately precede a blockquote paragraph in Word. + + informaltable + + + Word table + + + A table with no title imediately preceding it. + - blockquote/attribution - blockquote-attribution - Should immediately follow a blockquote paragraph in Word. + + caption + + + caption + + + + - highlights/para - highlights - Consecutive highlights paragraphs are coalesced into a single highlights parent. + + literallayout + + + literallayout + + + Inside a literallayout paragraph in Word, lines should be separated by line break (Shift-Enter) rather than paragraph break (Enter). + - highlights/itemizedlist/listitem/para - highlights-itemizedlist - Nested lists are not currently supported. + + programlisting + + + programlisting + + + Inside a programlisting paragraph in Word, lines should be separated by line break (Shift-Enter) rather than paragraph break (Enter). Tabs are not supported. + - highlights/orderedlist/listitem/para - highlights-orderedlist - Nested lists are not currently supported. + + blockquote/title + + + blockquote-title + + + Must immediately precede a blockquote paragraph in Word. + - highlights/caution - highlights-caution - + + blockquote/para + + + blockquote + + + + - highlights/important - highlights-important - + + blockquote/attribution + + + blockquote-attribution + + + Must immediately follow a blockquote paragraph in Word. + - highlights/note - highlights-note - + + bibliomisc + + + bibliomisc + + + + - highlights/tip - highlights-tip - + + + Non-DocBook elements + + - highlights/warning - highlights-warning - + + xi:include + + + xinclude + + + The content of the paragraph becomes the value of the href attribute. + - Inline elements + + Inline elements + + + + + + emphasis + + + emphasis + + + + + + + + emphasis/@role="bold" + + + emphasis-bold + + + + + + + + emphasis/@role="underline" + + + emphasis-underline + + + + + + + + footnote + + + Word footnote + + + + + + + + link + + + link + + + In Word, hyperlink properties identify the DocBook linkend. - emphasis - emphasis - + + releaseinfo + + + releaseinfo + + + + - emphasis with @role="bold" - emphasis-bold - + + surname + + + surname + + + Character style. Must occur in an appropriate parent paragraph, such as author or editor. + - footnote - Word footnote - + + firstname + + + firstname + + + Character style. Must occur in an appropriate parent paragraph, such as author or editor. + - link - link - In Word, hyperlink properties identify the DocBook linkend. + + orgname + + + orgname + + + + - xref - xref - In Word, hyperlink properties identify the DocBook linkend. Some placeholder text can be used in Word, but it will be discarded when exported to DocBook where xref is an empty element. + + keyword + + + keywordset/keyword + + + Paragraph style. Consecutive keyword elements are merged into a single keywordset parent element. Words (phrases) within a paragraph separated by commas become individual keyword elements. + - olink - olink - In Word, hyperlink properties identify the DocBook targetdoc and targetptr. + + citetitle + + + citetitle + + + + - ulink - ulink - In Word, hyperlink properties identify the url. + + city + + + city + + + + - glossterm - glossterm - In Word, hyperlink properties identify the DocBook linkend. + + contrib + + + contrib + + + + - firstterm - firstterm - In Word, hyperlink properties identify the DocBook linkend. + + country + + + country + + + + - computeroutput - computeroutput - + + email + + + email + + + + - literal - literal - + + fax + + + fax + + + + - replaceable - replaceable - + + honorific + + + honorific + + + + - userinput - userinput - + + jobtitle + + + jobtitle + + + + - command - command - + + lineage + + + lineage + + + + - filename - filename - + + orgdiv + + + orgdiv + + + + - option - option - + + otheraddr + + + otheraddr + + + + - parameter - parameter - + + othername + + + othername + + + + - systemitem - systemitem - + + phone + + + phone + + + + - releaseinfo - releaseinfo - + + pob + + + pob + + + + - author - author - + + postcode + + + postcode + + + + - bibliomisc - bibliomisc - + + shortaffil + + + shortaffil + + + + - surname - surname - Character style. Must occur in an appropriate parent paragraph, such as author. + + state + + + state + + + + + + +
+ + Proposed Additions - not yet implemented + + + + + - firstname - firstname - Character style. Must occur in an appropriate parent paragraph, such as author. + + DocBook element + + + Style(s) + + + Comments + + + - orgname - orgname - + + variablelist/varlistentry/term + + + + variablelist1-term +variablelist2-term +variablelist3-term +variablelist4-term + + + + A variablelist in Word should be a sequence of alternating paragraphs styled as variablelistN-term and variablelistN. + - keyword - keywordset/kyword - Paragraph style. Consecutive keyword elements are merged into a single keywordset parent element. Words (phrases) within a paragraph separated by commas become individual keyword elements. + + variablelist/varlistentry/listitem/para + + + + variablelist1 +variablelist2 +variablelist3 +variablelist4 + + + + Consecutive paragraphs are coalesced. +
Attributes - Attributes are a feature of DocBook XML that have no direct counterpart in Word. Several approaches are possible: - - - Use Word comments (annotations); the currently implemented approach. Some dummy text (just a space, using a character style that includes the hidden property) anchors the comment. Within the comment text, character types are used to indicate attribute names and values (these must be paired). This approach keeps the attributes separate to the main body and allows multiple attributes to be encoded. - A disadvantage to this approach (which also applies to the other approaches below) is that a paragraph may be related to more than one element, but the attributes are associated with only one element (by default the parent). For example, a section may have an attribute as well as the title child element, but only a single paragraph (with paragraph style section-title) represents both elements. Any attribute defined in a comment would be associated with the section element. - Pages does not have annotations, so the character styles attribute-name and attribute-value are used. - - - Use Word Bookmarks for attributes. For example, a Word Bookmark named att_role_foobar could be inserted into a paragraph. When converted to DocBook XML, this would become a role="foobar" attribute on the element derived from the paragraph containing the Bookmark. - - - Use hidden text. Define character styles that have their text hidden, and place these at the beginning of a paragraph. - - + Attributes are a feature of DocBook XML that have no direct counterpart in Word. + XML attributes are encoded in Word comments (annotations). Some dummy text (just a space, using a character style that includes the hidden property) anchors the comment. Within the comment text, character types are used to indicate attribute names and values (these must be paired). This approach keeps the attributes separate to the main body and allows multiple attributes to be encoded. + A disadvantage to this approach is that a paragraph may be related to more than one element, but the attributes are associated with only one element (by default the parent). For example, a section may have an attribute as well as the title child element, but only a single paragraph (with paragraph style sect1-title) represents both elements. Any attribute defined in a comment would be associated with the sect1 element. + Pages does not have annotations, so the character styles attribute-name and attribute-value are used.
diff --git a/xsl/roundtrip/supported.xml b/xsl/roundtrip/supported.xml deleted file mode 100644 index 4249c1037..000000000 --- a/xsl/roundtrip/supported.xml +++ /dev/null @@ -1,7137 +0,0 @@ -
- - Supported Elements - - - Ball - Steve - - Explain -
- www.explain.com.au -
- - - - $Id$ - - - - 1.1 - SRB - 2005-12-14 - Added contrib. - - - 1.0 - SRB - 2005-12-06 - Moved material from specs document. - - - - - The DocBook roundtripping system supports only a subset of DocBook elements. The status of support for the various elements is shown below. - Further, DocBook elements may only be combined in certain ways. Restrictions to how elements may be used together is also noted below. - - Legend: dbk:yes fully supported; dbk:no not supported; dbk:partial limited support. - - - Support Elements - - - - - - - - - - - - Element name - - - Style name - - - Support status - - - Type - - - Comments - - - - - - - - abbrev - - - abbrev - - - dbk:no - - - Character - - - - - - - - abstract - - - abstract - abstract-title - - - dbk:yes - - - Paragraph - - - Will be included in component metadata. May be preceded by a title. - - - - - accel - - - accel - - - dbk:no - - - Character - - - - - - - - ackno - - - ackno - - - dbk:no - - - Paragraph - - - - - - - - acronym - - - acronym - - - dbk:no - - - Character - - - - - - - - action - - - action - - - dbk:no - - - Character - - - - - - - - address - - - address - - - dbk:yes - - - Paragraph - - - Address elements will be created where necessary in metadata, but mayalso be explicit. - - - - - affiliation - - - affiliation - - - dbk:yes - - - Paragraph - - - May be included in metadata. - - - - - alt - - - alt - - - dbk:no - - - Character - - - - - - - - anchor - - - anchor - - - dbk:no - - - Character - - - - - - - - answer - - - answer - - - dbk:yes - - - Paragraph - - - Must be preceded by a question. - - - - - appendix - - - appendix-title - - - dbk:yes - - - Paragraph - - - - - - - - appendixinfo - - - - - - dbk:yes - - - None - - - Created when required for metadata. - - - - - application - - - application - - - dbk:yes - - - Character - - - - - - - - area - - - area - - - dbk:yes - - - Paragraph - - - Must be preceded by an areaspec element. No content is permitted. - - - - - areaspec - - - areaspec - - - dbk:yes - - - Paragraph - - - Only effective when used with a callout element. No content is permitted. - - - - - arg - - - arg - - - dbk:no - - - Character - - - - - - - - article - - - article-title - article-subtitle - article-titleabbrev - - - dbk:yes - - - Paragraph - - - articleinfo is created if required for metadata. title, subtitle and titleabbrev created as required. - - - - - articleinfo - - - - - - dbk:yes - - - None - - - See article. - - - - - artpagenums - - - artpagenums - - - dbk:no - - - Paragraph - - - - - - - - attribution - - - blockquote-attribution - - - dbk:partial - - - Paragraph - - - Only supported for use with blockquote. Must be preceded by blockquote or blockquote-title. - - - - - audiodata - - - audiodata - - - dbk:no - - - Paragraph - - - - - - - - audioobject - - - audioobject - - - dbk:no - - - Paragraph - - - - - - - - author - - - author - - - dbk:yes - - - Paragraph - - - Child elements are defined using character styles. Any other text content is ignored. - - - - - authorblurb - - - authorblurb - - - dbk:no - - - Paragraph - - - - - - - - authorgroup - - - authorgroup - - - dbk:no - - - Paragraph - - - - - - - - authorinitials - - - authorinitials - - - dbk:yes - - - Character - - - - - - - - beginpage - - - beginpage - - - dbk:no - - - Paragraph - - - - - - - - bibliocoverage - - - bibliocoverage - - - dbk:no - - - Paragraph - - - - - - - - bibliodiv - - - bibliodiv-title - - - dbk:yes - - - Paragraph - - - Must be preceded by bibliography-title. title element created as required. - - - - - biblioentry - - - biblioentry-title - - - dbk:yes - - - Paragraph - - - Must be preceded by bibliography-title. title element created as required. - - - - - biblioentry - - - biblioentry-title - - - dbk:yes - - - Paragraph - - - Must be preceded by bibliography-title. title element created as required. - - - - - bibliography - - - bibliography-title - - - dbk:yes - - - Paragraph - - - title element created as required. - - - - - bibliographyinfo - - - - - - dbk:no - - - None - - - - - - - - biblioid - - - biblioid - - - dbk:no - - - Paragraph - - - - - - - - bibliolist - - - bibliolist - - - dbk:no - - - Paragraph - - - - - - - - bibliomisc - - - bibliomisc - - - dbk:yes - - - Paragraph - - - - - - - - bibliomixed - - - bibliomixed - - - dbk:no - - - Paragraph - - - - - - - - bibliomset - - - bibliomset - - - dbk:no - - - Paragraph - - - - - - - - biblioref - - - biblioref - - - dbk:no - - - Character - - - - - - - - bibliorelation - - - bibliorelation - - - dbk:yes - - - Paragraph - - - - - - - - biblioset - - - biblioset - - - dbk:no - - - Paragraph - - - - - - - - bibliosource - - - bibliosource - - - dbk:no - - - Paragraph - - - - - - - - blockinfo - - - - - - dbk:partial - - - None - - - Created when necessary for metadata. - - - - - blockquote - - - blockquote - blockquote-title - - - dbk:yes - - - Paragraph - - - Consecutive blockquote elements are coalesced into a single blockquote element. - - - - - book - - - book-title - book-subtitle - book-titleabbrev - - - dbk:yes - - - Paragraph - - - bookinfo is created if required for metadata. title, subtitle and titleabbrev created as required. - - - - - bookinfo - - - - - - dbk:yes - - - None - - - Created when required, see book. - - - - - bridgehead - - - bridgehead - - - dbk:yes - - - Paragraph - - - - - - - - callout - - - callout - - - dbk:yes - - - Paragraph - - - calloutlist element created automatically. Consecutive callout elements are coalesced into a single calloutlist element. - - - - - calloutlist - - - - - - dbk:yes - - - None - - - calloutlist element created automatically, see callout element. - - - - - caption - - - caption - - - dbk:yes - - - Paragraph - - - Must be preceded by mediaobject, table or figure. - - - - - caution - - - caution - caution-title - - - dbk:yes - - - Paragraph - - - Consecutive cautions are colesced into a single caution element. - - - - - chapter - - - chapter-title - chapter-subtitle - chapter-titleabbrev - - - dbk:yes - - - Paragraph - - - chapterinfo is created if required for metadata. title, subtitle and titleabbrev created as required. - - - - - chapterinfo - - - - - - dbk:yes - - - None - - - Created when required, see chapter. - - - - - citation - - - citation - - - dbk:no - - - Character - - - - - - - - citebiblioid - - - citebiblioid - - - dbk:no - - - Character - - - - - - - - citerefentry - - - citerefentry - - - dbk:no - - - Character - - - - - - - - citetitle - - - citetitle - - - dbk:yes - - - Character - - - - - - - - city - - - city - - - dbk:yes - - - Character - - - - - - - - classname - - - classname - - - dbk:no - - - Character - - - - - - - - classsynopsis - - - classsynopsis - - - dbk:no - - - Paragraph - - - - - - - - classsynopsisinfo - - - classsynopsisinfo - - - dbk:no - - - None - - - - - - - - cmdsynopsis - - - cmdsynopsis - - - dbk:no - - - Paragraph - - - - - - - - co - - - co - - - dbk:no - - - Character - - - - - - - - code - - - code - - - dbk:no - - - Character - - - - - - - - col - - - col - - - dbk:no - - - None - - - - - - - - colgroup - - - colgroup - - - dbk:no - - - None - - - - - - - - collab - - - collab - - - dbk:no - - - Character - - - - - - - - collabname - - - collabname - - - dbk:no - - - Character - - - - - - - - colophon - - - colophon - - - dbk:no - - - Paragraph - - - - - - - - colspec - - - colspec - - - dbk:yes - - - None - - - Created when required. - - - - - command - - - command - - - dbk:no - - - Character - - - - - - - - computeroutput - - - computeroutput - - - dbk:no - - - Character - - - - - - - - confdates - - - confdates - - - dbk:no - - - Character - - - - - - - - confgroup - - - confgroup - - - dbk:no - - - None - - - - - - - - confnum - - - confnum - - - dbk:no - - - Character - - - - - - - - confsponsor - - - confsponsor - - - dbk:no - - - Character - - - - - - - - conftitle - - - conftitle - - - dbk:no - - - Character - - - - - - - - constant - - - constant - - - dbk:no - - - Character - - - - - - - - constraint - - - constraint - - - dbk:no - - - Character - - - - - - - - constraintdef - - - constraintdef - - - dbk:no - - - Character - - - - - - - - constructorsynopsis - - - constructorsynopsis - - - dbk:no - - - Paragraph - - - - - - - - contractnum - - - contractnum - - - dbk:no - - - Character - - - - - - - - contractsponsor - - - contractsponsor - - - dbk:no - - - Character - - - - - - - - contrib - - - - - - dbk:yes - - - None - - - Default element to use for metadata. - - - - - copyright - - - copyright - - - dbk:no - - - Paragraph - - - - - - - - coref - - - coref - - - dbk:no - - - Character - - - - - - - - corpauthor - - - corpauthor - - - dbk:no - - - Paragraph - - - - - - - - corpcredit - - - corpcredit - - - dbk:no - - - Character - - - - - - - - corpname - - - corpname - - - dbk:no - - - Character - - - - - - - - country - - - country - - - dbk:yes - - - Character - - - - - - - - database - - - database - - - dbk:no - - - Character - - - - - - - - date - - - date - - - dbk:yes - - - Character - - - - - - - - dedication - - - dedication - - - dbk:no - - - Paragraph - - - - - - - - destructorsynopsis - - - destructorsynopsis - - - dbk:no - - - Paragraph - - - - - - - - edition - - - edition - - - dbk:yes - - - Paragraph - - - - - - - - editor - - - editor - - - dbk:no - - - Paragraph - - - - - - - - email - - - email - - - dbk:yes - - - None - - - Created when a hyperlink refers to an email address. - - - - - emphasis - - - emphasis - emphasis-bold - emphasis-underline - - - dbk:yes - - - Character - - - Also created when text is marked-up as bold, italic or underlined. The role attribute encodes the weight or style used. - - - - - entry - - - entry - - - dbk:yes - - - None - - - Created for table cells. - - - - - entrytbl - - - entrytbl - - - dbk:no - - - None - - - - - - - - envvar - - - envvar - - - dbk:no - - - Character - - - - - - - - epigraph - - - epigraph - - - dbk:no - - - Paragraph - - - - - - - - equation - - - equation - - - dbk:no - - - Paragraph - - - - - - - - errorcode - - - errorcode - - - dbk:no - - - Character - - - - - - - - errorname - - - errorname - - - dbk:no - - - Character - - - - - - - - errortext - - - errortext - - - dbk:no - - - Character - - - - - - - - errortype - - - errortype - - - dbk:no - - - Character - - - - - - - - example - - - example-title - - - dbk:yes - - - Paragraph - - - title element created as required. The immediately following block element is included in the example. - - - - - exceptionname - - - exceptionname - - - dbk:no - - - Character - - - - - - - - fax - - - fax - - - dbk:yes - - - Character - - - - - - - - fieldsynopsis - - - fieldsynopsis - - - dbk:no - - - Character - - - - - - - - figure - - - figure-title - - - dbk:yes - - - Paragraph - - - Created for images in the document. - - - - - filename - - - filename - - - dbk:yes - - - Character - - - - - - - - firstname - - - firstname - - - dbk:yes - - - Character - - - - - - - - firstterm - - - firstterm - - - dbk:no - - - Character - - - - - - - - footnote - - - - - - dbk:yes - - - None - - - Created for footnotes. - - - - - footnoteref - - - footnoteref - - - dbk:no - - - Character - - - - - - - - foreignphrase - - - foreignphrase - - - dbk:no - - - Character - - - - - - - - formalpara - - - formalpara - formalpara-title - - - dbk:yes - - - Paragraph - - - Consecutive formal paragraphs are coalesced into a single formalpara element. - - - - - funcdef - - - funcdef - - - dbk:no - - - Character - - - - - - - - funcparams - - - funcparams - - - dbk:no - - - Character - - - - - - - - funcprototype - - - funcprototype - - - dbk:no - - - Character - - - - - - - - funcsynposis - - - funcsynopsis - - - dbk:no - - - Paragraph - - - - - - - - funcsynopsisinfo - - - funcsynopsisinfo - - - dbk:no - - - None - - - - - - - - function - - - function - - - dbk:no - - - Character - - - - - - - - glossary - - - glossary-title - - - dbk:yes - - - Paragraph - - - - - - - - glossaryinfo - - - - - - dbk:no - - - Character - - - - - - - - glossdef - - - glossdef - - - dbk:no - - - Paragraph - - - - - - - - glossdiv - - - glossdiv-title - - - dbk:no - - - Paragraph - - - - - - - - glossentry - - - glossentry - - - dbk:no - - - Paragraph - - - - - - - - glosslist - - - glosslist - - - dbk:no - - - Paragraph - - - - - - - - glosssee - - - glosssee - - - dbk:no - - - Character - - - - - - - - glossseealso - - - glossseealso - - - dbk:no - - - Character - - - - - - - - glossterm - - - glossterm - - - dbk:no - - - Paragraph - - - - - - - - graphic - - - graphic - - - dbk:no - - - Paragraph - - - - - - - - graphicco - - - graphicco - - - dbk:no - - - Paragraph - - - - - - - - group - - - group - - - dbk:no - - - Paragraph - - - - - - - - guibutton - - - guibutton - - - dbk:no - - - Paragraph - - - - - - - - guiicon - - - guiicon - - - dbk:no - - - Paragraph - - - - - - - - guilabel - - - guilabel - - - dbk:no - - - Paragraph - - - - - - - - guimenu - - - guimenu - - - dbk:no - - - Paragraph - - - - - - - - guimenuitem - - - guimenuitem - - - dbk:no - - - Paragraph - - - - - - - - guisubmenu - - - guisubmenu - - - dbk:no - - - Paragraph - - - - - - - - hardware - - - hardware - - - dbk:no - - - Character - - - - - - - - highlights - - - highlights - highlights-caution - highlights-important - highlights-itemizedlist - highlights-note - highlights-orderedlist - highlights-tip - highlights-warning - - - dbk:yes - - - Paragraph - - - Consecutive elements are coalesced into a single highlights element. - - - - - holder - - - holder - - - dbk:no - - - Character - - - - - - - - honorific - - - honorific - - - dbk:yes - - - Character - - - - - - - - html:form - - - html:form - - - dbk:no - - - Paragraph - - - - - - - - imagedata - - - - - - dbk:yes - - - Character - - - See informalfigure, imageobject or mediaobject. - - - - - imageobject - - - imageobject-imagedata - - - dbk:yes - - - Paragraph - - - Also creates imagedata element. The content of the paragraph becomes the value of the imagedata element's fileref attribute. - - - - - imageobjectco - - - imageobjectco-imagedata - - - dbk:yes - - - Paragraph - - - Also creates imagedata element. The content of the paragraph becomes the value of the imagedata element's fileref attribute. - - - - - important - - - important - important-title - - - dbk:yes - - - Paragraph - - - Consecutive important paragraphs are coalesced into a single important element. - - - - - index - - - index-title - - - dbk:yes - - - Paragraph - - - - - - - - indexdiv - - - indexdiv-title - - - dbk:no - - - Paragraph - - - - - - - - indexentry - - - indexentry-title - - - dbk:no - - - Paragraph - - - - - - - - indexinfo - - - - - - dbk:no - - - None - - - - - - - - indexterm - - - - - - dbk:yes - - - Character - - - Created by index terms in the document. - - - - - informalequation - - - informalequation - - - dbk:no - - - Paragraph - - - - - - - - informalexample - - - informalexample - - - dbk:no - - - Paragraph - - - - - - - - informalfigure - - - informalfigure-imagedata - - - dbk:yes - - - Paragraph - - - imageobject and imagedata elements created as required. - - - - - informaltable - - - - - - dbk:yes - - - None - - - Created for a table in the document. - - - - - initializer - - - initializer - - - dbk:no - - - Character - - - - - - - - inlineequation - - - inlinequation - - - dbk:no - - - Character - - - - - - - - inlinegraphic - - - inlinegraphic - - - dbk:no - - - Character - - - - - - - - inlinemediaobject - - - inlinemediaobject - - - dbk:no - - - Character - - - - - - - - interface - - - interface - - - dbk:no - - - Character - - - - - - - - interfacename - - - interfacename - - - dbk:no - - - Character - - - - - - - - invpartnumber - - - invpartnumber - - - dbk:no - - - Character - - - - - - - - isbn - - - isbn - - - dbk:yes - - - Paragraph - - - - - - - - issn - - - issn - - - dbk:no - - - Paragraph - - - - - - - - issuenum - - - issuenum - - - dbk:no - - - Character - - - - - - - - itemizedlist - - - itemizedlist - itemizedlist1 - itemizedlist2 - itemizedlist3 - itemizedlist4 - - - dbk:yes - - - Paragraph - - - Itemizedlist (bullet) list with nesting. Trailing digit refers to nesting level. Consecutive elements are coalesced into a single list element. - para-continue style paragraphs become separate paragraphs within a list item. - - - - - itermset - - - itermset - - - dbk:no - - - None - - - - - - - - jobtitle - - - jobtitle - - - dbk:yes - - - Character - - - - - - - - keycap - - - keycap - - - dbk:no - - - Character - - - - - - - - keycode - - - keycode - - - dbk:no - - - Character - - - - - - - - keycombo - - - keycombo - - - dbk:no - - - Character - - - - - - - - keysym - - - keysym - - - dbk:no - - - Character - - - - - - - - keyword - - - keyword - - - dbk:no - - - Character - - - - - - - - keywordset - - - keywordset - - - dbk:no - - - Paragraph - - - - - - - - label - - - label - - - dbk:no - - - Character - - - - - - - - legalnotice - - - legalnotice - - - dbk:no - - - Paragraph - - - - - - - - lhs - - - lhs - - - dbk:no - - - Character - - - - - - - - lineage - - - lineage - - - dbk:yes - - - Character - - - - - - - - lineannotation - - - lineannotation - - - dbk:no - - - Character - - - - - - - - link - - - link - - - dbk:yes - - - Character - - - Created for hyperlinks. - - - - - listitem - - - - - - dbk:yes - - - None - - - Created automatically in lists. - - - - - literal - - - literal - - - dbk:yes - - - Character - - - - - - - - literallayout - - - literallayout - - - dbk:yes - - - Paragraph - - - Line breaks are preserved in content. Consecutive literal layout paragraphs are coalesced into a single literallayoutelement. - - - - - lot - - - lot - - - dbk:no - - - Paragraph - - - - - - - - lotentry - - - lotentry - - - dbk:no - - - Paragraph - - - - - - - - manvolnum - - - manvolnum - - - dbk:no - - - Character - - - - - - - - markup - - - markup - - - dbk:no - - - Character - - - - - - - - medialabel - - - medialabel - - - dbk:no - - - Character - - - - - - - - mediaobject - - - mediaobject-title - - - dbk:yes - - - Paragraph - - - Following image and/or text objects are included in the mediaobject element. - - - - - mediaobjectco - - - mediaobjectco - - - dbk:yes - - - Paragraph - - - Following image object callout is included in the mediaobjectco. - - - - - member - - - member - - - dbk:no - - - Paragraph - - - - - - - - menuchoice - - - menuchoice - - - dbk:no - - - Character - - - - - - - - methodname - - - methodname - - - dbk:no - - - Character - - - - - - - - methodparam - - - methodparam - - - dbk:no - - - Character - - - - - - - - methodsynopsis - - - methodsynopsis - - - dbk:no - - - Paragraph - - - - - - - - mml:math - - - mml:math - - - dbk:no - - - Paragraph - - - - - - - - modespec - - - modespec - - - dbk:no - - - Character - - - - - - - - modifier - - - modifier - - - dbk:no - - - Character - - - - - - - - mousebutton - - - mousebutton - - - dbk:no - - - Character - - - - - - - - msg - - - msg - - - dbk:no - - - Paragraph - - - - - - - - msgaud - - - msgaud - - - dbk:no - - - Character - - - - - - - - msgentry - - - msgentry - - - dbk:no - - - Paragraph - - - - - - - - msgexplan - - - msgexplan - - - dbk:no - - - Paragraph - - - - - - - - msginfo - - - msginfo - - - dbk:no - - - None - - - - - - - - msglevel - - - msglevel - - - dbk:no - - - Character - - - - - - - - msgmain - - - msgmain - - - dbk:no - - - Paragraph - - - - - - - - msgorig - - - msgorig - - - dbk:no - - - Character - - - - - - - - msgrel - - - msgrel - - - dbk:no - - - Character - - - - - - - - msgset - - - msgset - - - dbk:no - - - Paragraph - - - - - - - - msgsub - - - msgsub - - - dbk:no - - - Character - - - - - - - - msgtext - - - msgtext - - - dbk:no - - - Character - - - - - - - - nonterminal - - - nonterminal - - - dbk:no - - - Character - - - - - - - - note - - - note - - - dbk:yes - - - Paragraph - - - Consecutive note paragraphs are coalesced into a single note element. - - - - - objectinfo - - - objectinfo - - - dbk:yes - - - None - - - Created when required. - - - - - olink - - - olink - - - dbk:yes - - - Character - - - Created from hyperlinks. - - - - - ooclass - - - ooclass - - - dbk:no - - - Character - - - - - - - - ooexception - - - ooexception - - - dbk:no - - - Character - - - - - - - - oointerface - - - oointerface - - - dbk:no - - - Character - - - - - - - - option - - - option - - - dbk:no - - - Character - - - - - - - - optional - - - optional - - - dbk:no - - - Character - - - - - - - - orderedlist - - - orderedlist - orderedlist1 - orderedlist2 - orderedlist3 - orderedlist4 - - - dbk:yes - - - Paragraph - - - Orderedlist (number) list with nesting. Trailing digit refers to nesting level. Consecutive elements are coalesced into a single list element. - para-continue style paragraphs become separate paragraphs within a list item. - - - - - orgdiv - - - orgdiv - - - dbk:no - - - Character - - - - - - - - orgname - - - orgname - - - dbk:yes - - - Character - - - - - - - - otheraddr - - - otheraddr - - - dbk:yes - - - Character - - - May be automatically created when required. - - - - - othercredit - - - othercredit - - - dbk:no - - - Character - - - - - - - - othername - - - othername - - - dbk:no - - - Character - - - - - - - - package - - - package - - - dbk:no - - - Character - - - - - - - - pagenums - - - pagenums - - - dbk:no - - - Character - - - - - - - - para - - - para - - - dbk:yes - - - Paragraph - - - May be created automatically when required. Paragraphs without a style use this element. - - - - - paramdef - - - paramdef - - - dbk:no - - - Character - - - - - - - - parameter - - - parameter - - - dbk:no - - - Character - - - - - - - - part - - - part-title - - - dbk:yes - - - Paragraph - - - partinfo element is created when required. - - - - - partinfo - - - - - - dbk:yes - - - None - - - See part. - - - - - partintro - - - partintro - - - dbk:no - - - Paragraph - - - - - - - - personblurb - - - personblurb - - - dbk:no - - - Paragraph - - - - - - - - personname - - - personname - - - dbk:no - - - Character - - - - - - - - phone - - - phone - - - dbk:no - - - Character - - - - - - - - phrase - - - phrase - - - dbk:no - - - Character - - - - - - - - pob - - - pob - - - dbk:no - - - Character - - - - - - - - postcode - - - postcode - - - dbk:no - - - Character - - - - - - - - preface - - - preface-title - - - dbk:yes - - - Paragraph - - - - - - - - prefaceinfo - - - prefaceinfo - - - dbk:yes - - - None - - - See preface. - - - - - primary - - - - - - dbk:partial - - - None - - - See indexterm - - - - - primaryie - - - primaryie - - - dbk:no - - - Character - - - - - - - - printhistory - - - printhistory - - - dbk:no - - - Paragraph - - - - - - - - procedure - - - procedure - - - dbk:no - - - Paragraph - - - - - - - - production - - - production - - - dbk:no - - - Character - - - - - - - - productionrecap - - - productionrecap - - - dbk:no - - - Character - - - - - - - - productionset - - - productionset - - - dbk:no - - - Character - - - - - - - - productionname - - - productionname - - - dbk:no - - - Character - - - - - - - - productnumber - - - productnumber - - - dbk:no - - - Character - - - - - - - - programlisting - - - programlisting - - - dbk:yes - - - Paragraph - - - Line breaks within the content are preserved. Consecutive paragraphs are coalesced into a single programlisting element. - - - - - programlistingco - - - programlistingco - - - dbk:yes - - - Paragraph - - - Line breaks within the content are preserved. Consecutive paragraphs are coalesced into a single programlistingco element. - - - - - prompt - - - prompt - - - dbk:no - - - Character - - - - - - - - property - - - property - - - dbk:no - - - Character - - - - - - - - pubdate - - - pubdate - - - dbk:no - - - Paragraph - - - - - - - - publisher - - - publisher - - - dbk:no - - - Paragraph - - - - - - - - publishername - - - publishername - - - dbk:yes - - - Paragraph - - - - - - - - pubsnumber - - - pubsnumber - - - dbk:no - - - Character - - - - - - - - qandadiv - - - qandadiv-title - - - dbk:yes - - - Paragraph - - - Must be preceded by a qandaset-title. - - - - - qandaentry - - - qandaentry-title - - - dbk:yes - - - Paragraph - - - Must be preceded by a qandaset-title. This element is created for a question element. - - - - - qandaset - - - qandaset-title - - - dbk:yes - - - Paragraph - - - - - - - - question - - - question - - - dbk:yes - - - Paragraph - - - Must be preceded by qandaset-title. qandaentry element is created as required. - - - - - quote - - - quote - - - dbk:no - - - Character - - - - - - - - refclass - - - refclass - - - dbk:no - - - Character - - - - - - - - refdescriptor - - - refdescriptor - - - dbk:no - - - Paragraph - - - - - - - - refentry - - - refentry - - - dbk:no - - - Paragraph - - - - - - - - refentryinfo - - - - - - dbk:no - - - None - - - - - - - - refentrytitle - - - refentrytitle - - - dbk:no - - - Paragraph - - - - - - - - reference - - - reference-title - - - dbk:no - - - Paragraph - - - - - - - - referenceinfo - - - - - - dbk:no - - - None - - - - - - - - refmeta - - - refmeta - - - dbk:no - - - None - - - - - - - - refmiscinfo - - - refmiscinfo - - - dbk:no - - - Character - - - - - - - - refname - - - refname - - - dbk:no - - - Paragraph - - - - - - - - refnamediv - - - refnamediv - - - dbk:no - - - Paragraph - - - - - - - - refpurpose - - - refpurpose - - - dbk:no - - - Paragraph - - - - - - - - refsect1 - - - refsect1-title - - - dbk:no - - - Paragraph - - - - - - - - refsect1info - - - - - - dbk:no - - - None - - - - - - - - refsect2 - - - refsect2-title - - - dbk:no - - - Paragraph - - - - - - - - refsect2info - - - - - - dbk:no - - - None - - - - - - - - refsect3 - - - refsect3-title - - - dbk:no - - - Paragraph - - - - - - - - refsect3info - - - - - - dbk:no - - - None - - - - - - - - refsection - - - refsection-title - - - dbk:no - - - Paragraph - - - - - - - - refsectioninfo - - - - - - dbk:no - - - None - - - - - - - - refsynopsisdiv - - - refsynopsisdiv-title - - - dbk:no - - - Paragraph - - - - - - - - refsynopsisdivinfo - - - - - - dbk:no - - - None - - - - - - - - releaseinfo - - - releaseinfo - - - dbk:yes - - - Paragraph - - - - - - - - remark - - - remark - - - dbk:no - - - Character - - - - - - - - replaceable - - - replaceable - - - dbk:no - - - Character - - - - - - - - returnvalue - - - returnvalue - - - dbk:no - - - Character - - - - - - - - revdescription - - - revdescription - - - dbk:no - - - Paragraph - - - - - - - - revhistory - - - - - - dbk:yes - - - None - - - Created as required. - - - - - revision - - - revision - - - dbk:yes - - - Paragraph - - - Revision data is specified by character styles. Any other content is discarded. - - - - - revnumber - - - revnumber - - - dbk:yes - - - Character - - - - - - - - revremark - - - revremark - - - dbk:yes - - - Paragraph - - - Must be preceded by revision paragraph. - - - - - rhs - - - rhs - - - dbk:no - - - Character - - - - - - - - row - - - - - - dbk:yes - - - None - - - Created as required in tables. - - - - - sbr - - - sbr - - - dbk:no - - - Character - - - - - - - - screen - - - screen - - - dbk:no - - - Paragraph - - - - - - - - screenco - - - screenco - - - dbk:no - - - Paragraph - - - - - - - - screeninfo - - - screeninfo - - - dbk:no - - - Paragraph - - - - - - - - screenshot - - - screenshot - - - dbk:no - - - Paragraph - - - - - - - - secondary - - - secondary - - - dbk:partial - - - Character - - - See indexterm. - - - - - secondaryie - - - secondaryie - - - dbk:no - - - Character - - - - - - - - sect1 - - - sect1-title - sect1-subtitle - - - dbk:yes - - - Paragraph - - - - - - - - sect1info - - - - - - dbk:yes - - - Paragraph - - - Created as required for metadata. - - - - - sect2 - - - sect2-title - sect2-subtitle - - - dbk:yes - - - Paragraph - - - - - - - - sect2info - - - - - - dbk:yes - - - Paragraph - - - Created as required for metadata. - - - - - sect3 - - - sect3-title - sect3-subtitle - - - dbk:yes - - - Paragraph - - - - - - - - sect3info - - - - - - dbk:yes - - - Paragraph - - - Created as required for metadata. - - - - - sect4 - - - sect4-title - sect4-subtitle - - - dbk:yes - - - Paragraph - - - - - - - - sect4info - - - - - - dbk:yes - - - Paragraph - - - Created as required for metadata. - - - - - sect5 - - - sect5-title - sect5-subtitle - - - dbk:yes - - - Paragraph - - - - - - - - sect5info - - - - - - dbk:yes - - - Paragraph - - - Created as required for metadata. - - - - - section - - - section-title - section-subtitle - section-titleabbrev - - - dbk:yes - - - Paragraph - - - - - - - - sectioninfo - - - - - - dbk:yes - - - Paragraph - - - Created as required for metadata. - - - - - see - - - see - - - dbk:no - - - Character - - - - - - - - seealso - - - seealso - - - dbk:no - - - Character - - - - - - - - seealsoie - - - seealsoie - - - dbk:no - - - Character - - - - - - - - seeie - - - seeie - - - dbk:no - - - Character - - - - - - - - seg - - - seg - - - dbk:no - - - Paragraph - - - - - - - - seglistitem - - - seglistitem - - - dbk:no - - - Paragraph - - - - - - - - segmentedlist - - - - - - dbk:no - - - None - - - - - - - - segtitle - - - segtitle - - - dbk:no - - - Paragraph - - - - - - - - seriesvolnums - - - seriesvolnums - - - dbk:no - - - Paragraph - - - - - - - - set - - - set-title - - - dbk:no - - - Paragraph - - - - - - - - setindex - - - setindex-title - - - dbk:no - - - Paragraph - - - - - - - - setindexinfo - - - - - - dbk:no - - - None - - - - - - - - sgmltag - - - sgmltag - - - dbk:yes - - - Character - - - - - - - - shortaffil - - - shortaffil - - - dbk:no - - - Character - - - - - - - - shortcut - - - shortcut - - - dbk:no - - - Character - - - - - - - - sidebar - - - sidebar-title - - - dbk:no - - - Paragraph - - - - - - - - sidebarinfo - - - - - - dbk:no - - - None - - - - - - - - simpara - - - simpara - - - dbk:yes - - - Paragraph - - - - - - - - simplelist - - - simplelist - - - dbk:no - - - Paragraph - - - - - - - - simplemsgentry - - - simplemsgentry - - - dbk:no - - - Paragraph - - - - - - - - simplesect - - - simplesect-title - simplesect-subtitle - - - dbk:no - - - Paragraph - - - - - - - - spanspec - - - - - - dbk:no - - - None - - - - - - - - state - - - state - - - dbk:no - - - Character - - - - - - - - step - - - step - - - dbk:no - - - Character - - - - - - - - stepalternatives - - - stepalternatives - - - dbk:no - - - Character - - - - - - - - street - - - street - - - dbk:no - - - Character - - - - - - - - structfield - - - structfield - - - dbk:no - - - Character - - - - - - - - structname - - - structname - - - dbk:no - - - Character - - - - - - - - subject - - - subject - - - dbk:no - - - Character - - - - - - - - subjectset - - - subjectset - - - dbk:no - - - Character - - - - - - - - subjectterm - - - subjectterm - - - dbk:no - - - Character - - - - - - - - subscript - - - subscript - - - dbk:no - - - Character - - - - - - - - substeps - - - substeps - - - dbk:no - - - Character - - - - - - - - subtitle - - - - - - dbk:yes - - - Paragraph - - - See component element. - - - - - superscript - - - superscript - - - dbk:no - - - Character - - - - - - - - surname - - - surname - - - dbk:yes - - - Character - - - - - - - - svg:svg - - - svg:svg - - - dbk:no - - - Character - - - - - - - - symbol - - - symbol - - - dbk:no - - - Character - - - - - - - - synopfragment - - - synopfragment - - - dbk:no - - - Character - - - - - - - - synopfragmentref - - - synopfragmentref - - - dbk:no - - - Character - - - - - - - - synopsis - - - synopsis - - - dbk:no - - - Character - - - - - - - - systemitem - - - systemitem - - - dbk:no - - - Character - - - - - - - - table - - - - - - dbk:yes - - - None - - - Tables in the document are encoded using this element. - - - - - task - - - task - - - dbk:no - - - Paragraph - - - - - - - - taskprerequisites - - - taskprerequisites - - - dbk:no - - - Paragraph - - - - - - - - taskrelated - - - taskrelated - - - dbk:no - - - Paragraph - - - - - - - - tasksummary - - - tasksummary - - - dbk:no - - - Paragraph - - - - - - - - tbody - - - - - - dbk:yes - - - None - - - Created as required for tables. - - - - - td - - - - - - dbk:no - - - None - - - See entry. - - - - - term - - - variablelist-term - - - dbk:yes - - - Paragraph - - - See variablelist. - - - - - tertiary - - - - - - dbk:partial - - - Character - - - See indexterm. - - - - - tertiaryie - - - tertiaryie - - - dbk:no - - - Paragraph - - - - - - - - textdata - - - - - - dbk:yes - - - Paragraph - - - See textobject. - - - - - textobject - - - textobject-title - - - dbk:yes - - - Paragraph - - - Creates a mediaobject and textdata elements as required. Immediately following paragraph becomes part of the text data. - - - - - tfoot - - - tfoot - - - dbk:no - - - Paragraph - - - - - - - - tgroup - - - - - - dbk:yes - - - None - - - Created as required for tables. See table. - - - - - th - - - th - - - dbk:no - - - Paragraph - - - - - - - - tip - - - tip - tip-title - - - dbk:yes - - - Paragraph - - - Consecutive tip paragraphs are coalesced into a single tip element. - - - - - title - - - - - - dbk:yes - - - Paragraph - - - See component and division elements. - - - - - titleabbrev - - - - - - dbk:yes - - - Paragraph - - - See component and division elements. - - - - - toc - - - toc-title - - - dbk:no - - - Paragraph - - - - - - - - tocback - - - tocback - - - dbk:no - - - Paragraph - - - - - - - - tocchap - - - tocchap - - - dbk:no - - - Paragraph - - - - - - - - tocentry - - - tocentry - - - dbk:no - - - Paragraph - - - - - - - - tocfront - - - tocfront - - - dbk:no - - - Paragraph - - - - - - - - toclevel1 - - - toclevel1 - - - dbk:no - - - Paragraph - - - - - - - - toclevel2 - - - toclevel2 - - - dbk:no - - - Paragraph - - - - - - - - toclevel3 - - - toclevel3 - - - dbk:no - - - Paragraph - - - - - - - - toclevel4 - - - toclevel4 - - - dbk:no - - - Paragraph - - - - - - - - toclevel5 - - - toclevel5 - - - dbk:no - - - Paragraph - - - - - - - - tocpart - - - tocpart - - - dbk:no - - - Paragraph - - - - - - - - token - - - token - - - dbk:no - - - Character - - - - - - - - tr - - - - - - dbk:no - - - None - - - - - - - - trademark - - - trademark - - - dbk:no - - - Character - - - - - - - - type - - - type - - - dbk:no - - - Character - - - - - - - - ulink - - - ulink - - - dbk:yes - - - Character - - - Created from hyperlinks, or explicitly. - - - - - uri - - - uri - - - dbk:no - - - Character - - - - - - - - userinput - - - userinput - - - dbk:no - - - Character - - - - - - - - varargs - - - varargs - - - dbk:no - - - Paragraph - - - - - - - - variablelist - - - variablelist-term - variablelist-title - variablelist-titleabbrev - - - dbk:yes - - - Paragraph - - - Consecutive terms are coalesced into a single variablelist. varlistentry elements are created as required. - - - - - varlistentry - - - - - - dbk:yes - - - Paragraph - - - See variablelist. - - - - - varname - - - varname - - - dbk:no - - - Character - - - - - - - - videodata - - - videodata - - - dbk:no - - - Paragraph - - - - - - - - videoobject - - - videoobject - - - dbk:no - - - Paragraph - - - - - - - - void - - - void - - - dbk:no - - - Character - - - - - - - - volumenum - - - volumenum - - - dbk:no - - - Character - - - - - - - - warning - - - warning - warning-title - - - dbk:yes - - - Paragraph - - - Consecutive paragraphs are coalesced into a single warningelement. - - - - - wordasword - - - wordasword - - - dbk:no - - - Character - - - - - - - - xref - - - xref - - - dbk:no - - - Character - - - - - - - - year - - - year - - - dbk:no - - - Character - - - - - - - - -
-
diff --git a/xsl/roundtrip/wordml2normalise.xsl b/xsl/roundtrip/wordml2normalise.xsl index 9ef8daaba..b0581cefa 100644 --- a/xsl/roundtrip/wordml2normalise.xsl +++ b/xsl/roundtrip/wordml2normalise.xsl @@ -276,9 +276,21 @@ - - - + + + + + + + + + + + + + + +