--- title: "Microsoft Word DOCX – import config usage" source: https://dev.pageseeder.com/guide/publishing/ant_api/extensions/microsoft_word_docx_import_config_usage.html last_updated: 2026-08-07T17:09:54+10:00 tokens: ~12568 --- # Microsoft Word DOCX – import config usage For creating a [PSML](../../../../reference/glossary/psml.md) file from a DOCX document. For the default word-import-config.xml, see the [default config example](microsoft_word_docx_import_config_default.md). > **Tip:** Additional information regarding support for DOCX in PageSeeder is: - [Word DOCX - import schema reference](../../../../reference/advanced/schemas/word-import-config.md), and - [Import Microsoft Word DOCX Ant task](task_import-docx.md). > **Note:** The Word import process can only import to the **default** PSML structures. There are some structures available in PSML that require custom configuration, and further editing to the imported content is needed once in PSML. Content for the following requires further editing once imported: - **Citations** – for further information, see [How to import xrefs, captions and citations from DOCX](../../../../get_started/tutorials/how_to_import_xrefs%2C_captions_and_citations_from_docx.md). - **Glossary** – for further information, see [How to create a shared glossary](../../../../get_started/tutorials/how_to_create_a_shared_glossary.md). - **Index** - **Placeholders** - **Properties fragments** ## Overview Editable by developers or technically-minded end users, the `word-import-config.xml` modifies the conversion of Word DOCX files to PSML. Changing the file requires familiarity with XML syntax, and a solid understanding of Microsoft Word. Depending on the import workflow, modifying the `word-import-config.xml` might require elevated permission. The location of the default file is: ```text /WEB-INF/template/default/document/docx/word-import-config.xml ``` The `word-import-config.xml` does not process all properties of the `.docx` file format. There are many aspects of a Word document where Word provides better and more immediate feedback. This is especially true where Word controls document formatting and page layout. PageSeeder excels at collaborative editing, managing content access, tracking changes, and enabling content reuse. Therefore, the focus of the import process is: - **Document structure** – Word expresses structure explicitly, *Heading 1* style contains *Heading 2* styles, and implicitly, bullet items in a table cell might be seen as less important than bullet items in the Overview section. The concepts are easy to understand, but Word lacks any formal definition of structure. This is why the `word-import-config.xml` provides flexibility for mapping Word styles for headings, outline levels, sections, lists, and paragraphs. - **File organization** – The import split process creates a hierarchical collection of files from a single Word document. It creates links from the [references document](../../../../reference/glossary/references_document.md) to the [component documents](../../../../reference/glossary/component_document.md). - **Semantics** – Extending the question of structure is that of semantics. Do the names that users create in their documents mean something? Or, are they simply to help format and organize objects in the document? The lack of any uniform answer to these questions is why the `word-import-config.xml` supports mapping the style names of Word paragraphs, characters, lists, and table styles. It also supports mapping bookmarks, document types, and other IDs. - **Linking** – Users rarely add many links to Word documents because of structural or semantic issues. However, the strong linking in PageSeeder, and ability of the `word-import-config.xml` to transform Word cross-references into PageSeeder xrefs and links, is worth mentioning. ### **Pre-import considerations** Not all aspects of a Word document are processed upon import. This means parts of the document that might be important are outside what PageSeeder can process. To ensure that information isn’t lost, attention should be given to the contents of the [Word](microsoft_word_docx_import_config_usage.md) document before importing it. For example, where software documentation includes code samples, replace any monospace font setting with a Word paragraph style like `HTML Preformatted`, or Word character style `HTML Code`, before importing into PageSeeder. Information that PageSeeder discards includes: - **Fonts / typefaces** – operating system dependencies and font licenses make the preservation of fonts from one system to another impractical. - **Style settings** – the import only processes the name (or `ID`, really) of the style. Any other settings, such as indents, must be part of the mapping rule. - **Measurements** – PageSeeder doesn’t process many measurements such as tab stops, margins, indents, column widths, line spacing, and borders. Exceptions include table settings that use percentages, and image size. - **Characters** – characters such as tabs or style separators are discarded on import – these could be changed to a space character, for example, so the content doesn’t run together after import. - **Headers / footers** – move any meaningful content in the headers or footers into the body of the document before importing. - **Macros** – the import ignores any macro code. - **Content controls** – a forms-based user interface will require building a [document template](../../../../reference/glossary/document_template.md). - **Fields** – some DOCX field data such as bookmarks and cross-references will import automatically,  an other fields such as index entries and footnotes require configuration. To preserve other field content requires processing them in Word before importing. - **Security** – PageSeeder has a separate permission model for accessing content, so the process ignores Word security settings. ## Background Understanding the complementary relationship between Word and PageSeeder, along with the role of `word-import-config.xml`, requires a basic understanding of how Word files function. One place to start is Microsoft [Open XML](https://en.wikipedia.org/wiki/Office_Open_XML) and the [Open Packaging Conventions](https://en.wikipedia.org/wiki/Open_Packaging_Conventions). Another is a tool such as the Google Chrome browser extension for [OpenXML](https://chrome.google.com/webstore/detail/ooxml-tools/bjmmjfdegplhkefakjkccocjanekbapn). Alternatively, simply copy a `.docx` file, rename it with a `.zip` extension, and open the zip archive to view the underlying XML. ![Import DOCX file - Underlying xml](/content/guide/publishing/ant_api/extensions/../../../../images/publishing/underlying-xml-from-docx-example.png) Another issue that can make a big difference is understanding how [heading and paragraph numbers](microsoft_word_docx_import_config_usage.md) work in Word documents – Word numbering is famously hard to tame. Many people find this aspect of Word frustrating, but with a proper implementation, this feature works consistently and correctly. For further understanding of its complexities, consider reading [Word’s Numbering Explained.](https://wordmvp.com/FAQs/Numbering/WordsNumberingExplained.htm) Unfortunately, the good use of Word [styles](http://office.microsoft.com/en-au/word-help/style-basics-in-word-HA010230882.aspx) is essential to get the most out of any DOCX file, and the `word-import-config.xml` offers some, but not much scope for improving the document quality on import. If the DOCX is consistently styled, using List Styles, and no manual overriding of paragraph or character styles, then the import process can covert the document to valid PSML. ## Usage To change from the PageSeeder [default word-import-config.xml](microsoft_word_docx_import_config_default.md), follow the steps below: 1. **Sign in** to PageSeeder and select a project or group. 2. Select** Developer** mode under *Account menu* \> **Preferences**. 3. [Project managers](../../../../reference/glossary/role.md) and administrators can change the `word-import-config.xml` for themselves ONLY: 1. Click the **Upload document...** option (located under the **Plus** button on several *group* pages) and drop/browse a `.docx` file. 2. Click **Import options** icon, **Import document as PageSeeder PSML**. 3. Choose **+Show more options**, then **Edit config**. 4. OR, the **Preview** button, then **config** button. 4. To change the default config for **all** groups in a project (*available only to project managers and administrators*): 1. Click *Project administration menu* \> **Template \> Template configuration.** 2. In the **Media types** table, **Word import** column, **docx** row, select **override** under the **default** option. 3. To revert to the default config, click **delete** under the **edit** option in the **Word import** column. > **Note:** For autocomplete when editing the `word-import-config.xml`, press **ctrl-space**. ### Converting Word styles to PSML #### Formatting By design, there is no formatting information in PageSeeder content. This is not because formatting isn’t important, rather, it is to support the concept of separating content and format. The architectural objective for this is that the exclusion of formatting leads to: - Better reuse of content. - Better productivity for writers. - More flexibility of delivery formats. In PageSeeder, formatting is moved further along the document lifecycle, to the [export](microsoft_word_docx_export_config_usage.md) stage, and adding it programmatically instead of manually, improves quality and consistency. #### Getting the best import result Using Word to get the most out of PageSeeder requires first creating a Word document with content that is consistently styled, [automatically numbered](microsoft_word_docx_import_config_usage.md), and ideally, free from manual overrides. Word styles are mapped to PSML content and labels, using the following relationships: - **Characters** – equivalent to an [inline label](../../../../reference/glossary/inline_label.md). - **Paragraphs** – equivalent to a [block label](../../../../reference/glossary/block_label.md). - **Tables** – can be categorized in PageSeeder by the use of the [@role attribute](../../../../psml/elements/element-table.md). - **Lists** – can be categorized in PageSeeder by the use of the `@role` attribute on [\](../../../../psml/elements/element-list.md) or [\](../../../../psml/elements/element-nlist.md). - **Images** – can have a character style in PSML. - **Metadata** – map pre-defined properties. - **Fields** – including footnotes, endnotes, index entries. - **References** – including Xrefs and links. Often the best way to import Word documents into PageSeeder is to clean them up first. In this circumstance, the best way to clean up Word files is in Word itself. ## Analyse data before import – OX and Docs Toolkit ### Word import – Numbering In order to get the right results from the PageSeeder import, the `word-import-config.xml` and the Word document to be converted, ideally, should have the proper numbering configuration. Users who are familiar with Word multilevel lists know their importance to enabling accurate numbering. If the numbering in your List Style works well in Word, then it will work just as well in PageSeeder. #### Numbering is hierarchical Numbering is hierarchical and a List Style defines this hierarchy – without a List Style, Word can’t know what this hierarchy is. It is the **heirarchical logic** defined in your List Style that PageSeeder imports – which paragraph style should follow which and which paragraph the numbering should restart at. PageSeeder doesn't import the actual numbering you see in Word, as the numbers are generated by the logic defined in your List Style and Word doesn’t store this actual numbering - only the **hierarchical logic** that is generating it. The defining of the List Style provides a definition that can be **replicated** in PageSeeder. > **Tip:** When you click the Multilevel List icon ![Microsoft Word Multilevel List icon](/content/guide/publishing/ant_api/extensions/microsoft_word_docx_import_config_usage_files/image_64191.png) in the Word ribbon, you see the list gallery. 1. New List Styles that you create always appear under the **List Styles** section in the list gallery. 2. Word’s built-in multilevel lists appear under the **List Library** section of the list gallery. #### Benefits of using List Styles in Word New List Styles, beneficially, can be: - named - shared - modified, and - deleted. List Styles are essential for consistency across a document. They enable the editing/updating of multiple paragraphs with the same style across the document. #### When should you use a List Style? – Always when you are numbering paragraphs These are just examples: - If you have unusual number schemes, for example: First, Second or 00001, 00002 (new to Word 2010), irregular indents for numbering levels, number font formatting that is different from the content of the heading style it is linked to, or appendix numbering. - If you have many writers collaboratively writing – and need to handle cut and pasted content. - To help other contributors to use the document correctly with minimal learning. #### Stability in numbering – Use List Styles List Styles, as defined in Word, only provide the numbering and its formatting, with the assigned levels determining the incrementation. Word paragraph and character styles provide the formatting for content that is not the numbering, for example, the text of a heading that follows the number, or the text of a paragraph that follows the number. A Word List Style defines a numbering scheme, including the form of number to be used and the tabs and indents for the number. They add stability to multilevel numbering, but the **crucial** part is: - Linking each level in a List Style to a **unique Word paragraph style**, and conversely - Each paragraph or heading style can point to **only one** List Style. When you set up your document with unique Word paragraph styles **and** a List Style, you can make changes to numbering by modifying the list. Using List Styles makes implementing changes across documents highly flexible, and results in much greater numbering consistency. - **A List Style creates a set or group of heading and paragraph styles** – Word comes with built-in paragraph styles named Heading 1, Heading 2, Heading 3. A List Style ‘groups’ those Word paragraph styles into some order. The List Style determines that Heading 1 is followed by Heading 2 and that it is followed by Heading 3, and that the numbering for Heading 2 restarts after the occurrence of a Heading 1. Although there are 9 levels in any Word List Style, it is very uncommon for nine levels to be used in a document – PageSeeder only uses six levels. - **A List Style defines the information about how to number each level** – That includes the format of the number ( "1" or "a" or "i"), whether the number is preceded by text (eg “Chapter 1” or “Part A”), whether the number includes previous levels’ numbers (eg paragraph 1.4.3), and the indents (the distance from margin to number and from number to text). When you apply a numbered paragraph style to content, Word automatically applies the numbering according to the definition in the List Style and list level linked to that style, and you don’t need to access the List Style directly. All other paragraphs that you apply that numbered paragraph to will belong to the same List Style and its numbering will automatically increment from the previous paragraph in the same style. ## Create a List Style Ideally: - **When creating a new document** – - In the Word **Styles pane**, format the paragraph styles to include in your List Style – this formatting is for any content **other than numbering** on each paragraph. - Then, create a List Style before creating your content. - Then, apply paragraph styles that are included in your List Style to your content as you write. - **When dealing with legacy content** – The content is likely already using a List Style, but in some cases, the document content could have paragraphs which styles that are manually overridden, or paragraph styles might not have been applied consistently. > **Tip:** It’s important not to manually overwrite any paragraphs styles! > **Note:** The ways to create a new List Style are: 1. Create a Word paragraph style for each level in the list, for example `MyList1`,` MyList2`. See the images of the Define New List Style dialog below. 1. Select **Define New List Style** from the Multilevel List menu (**not** Define New Multilevel List). 2. Enter a name for the list template, for example `My List`. 3. Then from the **Format** menu, select **Numbering.** 4. Define the numbering format options for each level. 5. On the right of the dialog, link a unique Word paragraph style to each level. 2. Alternatively, users unfamiliar with Word multilevel lists, or List Styles might find it easier to modify, or refer to, the already-configured `word-import-config.xml`. Map the Word paragraph styles `List Number`, `List Number 2` etc. to PSML structures using the [\](microsoft_word_docx_import_config_usage.md) element (Note, if any numbering has been manually overridden in the DOCX, you might not see the same numbering, as PageSeeder  imports only logic of the numbering from Word). 1. For this, edit the default `word-import-config.xml` for your project on PageSeeder – click the wrench icon in the header bar, then in the main section, click *Project administration menu \> ***Template \> Template configuration**, then in the **Media types** table, **Word Import** column and in the **docx** row, click **default****.** 2. Modify the declarations in the `word-import-config.xml` and **Save** the changes. ![Define New List Style](/content/guide/publishing/ant_api/extensions/microsoft_word_docx_export_config_usage_files/define_new_list_style.png) ![Define New List Style – Define numbering options](/content/guide/publishing/ant_api/extensions/microsoft_word_docx_export_config_usage_files/define_new_list_style_define_numbering_options.png) ![Define New List Style - Link level to paragraph style](/content/guide/publishing/ant_api/extensions/microsoft_word_docx_export_config_usage_files/define_new_list_style_link_level_to_paragraph_style.png) ## Next steps – configure the import process When you have your List Styles, there are two configuration files needed for the import process: 1. [word-import-config.xml](microsoft_word_docx_import_config_default.md) – Specifies the mapping of Word paragraph styles to PSML elements. 2. `publication-config.xml` – Among other properties, this controls the way a “[Publication](../../../../reference/glossary/publications.md)” is auto-numbered in PageSeeder. ### Word import config file – `word-import-config.xml` The location of the default import config for a project is: ```text WEB-INF/config/template/[project-name]/document/docx/word-import-config.xml ``` The information below describes different ways that the `word-import-config.xml` file transforms DOCX format into PSML. In Word, styles can have multiple names, separated by commas. For the import, only the name before the first comma is processed. > **Note:** In this document, references to the **style** **`ID`**, are not the same as the** style `name`.** The style `ID` is what the import process uses internally. The `name` is what Word displays in the **Styles** pane in the user interface, One way to see these `ID` values is to “unzip” the `.docx` file, and open the `styles.xml` file. Here is an example from a `styles.xml` file for a Word paragraph style. The value for attribute `w:styleId` is what is mapped in the import config file, in element `` in its attribute `name`. ```xml ... ``` In the `word-import-config.xml`, the declaration for this Word paragraph style to import as a PSML `` element might look like this: ```xml ``` - Only refer to styles in use in the Word document. - The heading styles built-in to Word are special – refer to them using their **style** `ID` which is upper case, for example, ``. - Sometimes Word style names display as upper case in the Styles pane but are actually lower case – if a style doesn’t apply, try changing the reference to lower case. See the [default word-import-config.xml](microsoft_word_docx_import_config_default.md) document here. #### Create a `word-import-config.xml` ### Publication and the publication config file – `publication-config.xml` A “[publication](../../../../reference/glossary/publications.md)” is a hierarchical collection of [PSML](../../../../reference/glossary/psml.md) component documents joined by “embed” or “transclude” type [xrefs](../../../../reference/glossary/block_xref.md). When published, the components are resolved into a single document for numbering and presentation. Publications are at [group](../../../../reference/glossary/group.md) level. The `publication-config.xml` file **recreates** the **hierarchy logic** that is present in the Word List Style and uses that logic to process and generate the numbering you see displayed in PageSeeder. #### Recommended reading We recommend reading the following documentation to gain an understanding of the publication concept in more detail: - [Publication](../../../../reference/glossary/publications.md) - [Publication ID](../../../../reference/glossary/publication_id.md) - [publication-config.xml](../../../../reference/glossary/publication_config.md) - [Publications and publication types](../../../configuration/publication_types.md) – which includes instructions for creating a publication config under the heading [Publication configuration](../../../configuration/publication_types.md). For additional background, we recommend completing [How to configure publications](../../../../get_started/tutorials/how_to_configure_publications.md). The challenges of document numbering are widely recognized and the sample files of the tutorial help to explain how PageSeeder addresses this issue. #### Create a `publication-config.xml` ## Configurable import components > **Tip:** For an in-progress additional document to this page, see [Word DOCX - import schema reference](../../../../reference/advanced/schemas/word-import-config.md). The following components process the conversion: - `` – handles [MathML](microsoft_word_docx_import_config_usage.md) (equations), [footnotes](microsoft_word_docx_import_config_usage.md), and [endnotes](microsoft_word_docx_import_config_usage.md). - **``** – configures lists. - **``** – translates the implied semantics and structure of Word styles into PageSeeder objects. ### Store – \ In the import config, the `` element relates **only** to MathML, footnotes, and endnotes, to control the conversion of these into files or fragments. > **Note:** The import process for a Word document involves two configuration files. First is the conversion of the DOCX styles by processing the `word-import-config.xml`, then the resulting PSML content, other than that content already processed by the `` element, is separated into files and fragments through the `psml-split-config.xml` file. For more detail, see: - [PSML split config schema reference](../../../../reference/advanced/schemas/psml-split-config.md) - [PSML split config usage](../tasks/psml_split_config_usage.md) ```xml ``` > **Obsolete:** The `
`, `` and `
` elements that were previously under element `` are obsolete as of PageSeeder v6. #### `` This element generates files for `` objects that exist in the Word document. ```xml ``` The attributes for `` are: - `@select` – to disable the generation of `` content, set select to `"false"`, (default `true`). - `@output` – setting this attribute value to `"generate-files"`, places each `` object in a separate file, under a `/mathml` folder. Setting it to `"generate-fragments"`, places each equation in its own fragment, in a document with the path `mathml/mathml-[n].psml` (default `generate-fragments`). *Requires pso-docx version `0.7.8` or higher.* - `@convert-to-mml` – setting value to `"true"` converts equations to the original ``. If the value is `"false"`, objects retain the Office Open `` syntax (default `true`, and always `true` for `generate-fragments` option). #### `` This element configures Word footnote handling. ```xml ``` The attributes for `` are: - `@select` – to disable generation of footnote content, set select to `"false"` (default `true`). - `@output` – set value to `"generate-files"` to place each reference in a separate file under a `/footnotes` folder. Selecting `"generate-fragments"` places each footnote in its own fragment, in a `footnotes/footnotes.psml` document (default `generate-fragments`). #### `` This element configures Word endnote handling. ```xml ``` The attributes for `` are: - `@select` – to disable generation of endnote content, set this attribute value to `"false"` (default `true`). - `@output` – to place each reference in a separate file under an /`endnotes` folder, set this value to `"generate-files"`. To place each endnote in its own fragment, in a `endnotes/endnotes.psml` document, set this value to `"generate-fragments"` (default `generate-fragments`). ### Order and organize – \ Processes Word lists, and paragraph numbering, and some manual numbering. ```xml ``` #### \ Adds a `@role` attribute to a `` or ``, with the `value` of the Word paragraph style. To invoke, set the `@select` attribute to `true` (default `false`). This attribute enables meaningful lists that store a semantic or formatting value, such as “procedures” or "guidance", that can be used for processing, validation or presentation. ```xml ``` #### \ Controls the conversion of numbered paragraph styles in Word to numbered paragraphs or lists in PageSeeder. For numbered paragraphs, set the value of the `@select` attribute to `true`. If `false`, the value converts to `` or ``, depending on the type of numbered value. ```xml ``` The `"number"` in the `@value` attribute of the `` element corresponds to the position in the Word list hierarchy – use `1` to `6`. It converts to the `"value"` of the `@indent` on the PSML element ``. Paragraph numbering `"display"` is in the `@option` attribute for each `` element. See below for examples: - `"prefix"` – to generate a prefix with the value of the current numbering value for each of the Word numbered paragraphs. - `"numbering`" – to generate numbered paragraphs. - "`inline=[labelname]"` – wraps the Word paragraph number in an inline label. - "`text`" – puts the Word numbers in the paragraph content. ```xml <-- prefix or numbering or inline=[label] or text --> ``` **Example DOCX** ![Numbered list in Word](/content/guide/publishing/ant_api/extensions/microsoft_word_docx_import_config_usage_files/list-number-docx.png) **Example in PageSeeder document view mode** ![Numbered list in view mode](/content/guide/publishing/ant_api/extensions/microsoft_word_docx_import_config_usage_files/list-number-ps-view-mode.png) **Example PSML** ![Numbered list – PSML source](/content/guide/publishing/ant_api/extensions/microsoft_word_docx_import_config_usage_files/list-number-psml-source-xml.png) #### Word Style – List Paragraph Native Word paragraph style, **List Paragraph**, is a complex, difficult to control concept in Word – if possible, avoid using it! It imports by default as a [\](microsoft_word_docx_import_config_usage.md) element, with a `"number"` in the `@indent` attribute, which corresponds to the position in the Word list hierarchy. - **"Bullets" or “Numbering” list icons are selected** – the Word default paragraph style is **List Paragraph**. Where no other Word paragraph style, either a bulleted style or numbered style, is applied to the content, it imports as a `` element. - **No "Bullets" or "Numbering" selected** – Word paragraph imports in a [\](microsoft_word_docx_import_config_usage.md). Alternatively, one of the default Word paragraph styles List Continue, List Continue 2, List Continue 3, ... can be applied to import the content in a `` element. #### \ > **Note:** Where you don’t want your PageSeeder heading and paragraph numbers to automatically increment, before importing, convert the Word document to non-automated, or manual, numbering values. The `` element processes non-automated, manual numbering values in Word files. To convert manual paragraph numbering values in Word, set the `@select` attribute to `true`. ```xml ``` In the configuration from the default `word-import-configuration.xml` shown below, the `` element contains a `@match` attribute, that has to follow the normal conventions of XSLT regular expressions ([www.w3.org/TR/xslt20/#regular-expressions)](https://www.w3.org/TR/xslt20/#regular-expressions%29). *As of pso-docx v1.5.0 `@match` may contain a single group and only text matching this group is used for `@prefix` .* The `` element accepts 3 options: - `` – generates a `@prefix` attribute with the contents of the current numbering `"value"` for each of the Word paragraphs containing the regular expression value. If `@level` is specified generates an `@indent` or `@level` attribute with this number (overrides ``). *Requires pso-docx v1.5.0 or later for @level.* - `` – to generate an `` element with content equal to the current numbering `"value"` for each of the Word paragraphs containing the regular expression value. - `` – generates a `@numbered="true"` attribute. This is the configuration from the default `word-import-configuration.xml`: ```xml           ``` Any number of `` elements can be added, as long as the `@match` attribute is a valid regular expression (check [www.w3.org/TR/xslt20/#regular-expressions)](https://www.w3.org/TR/xslt20/#regular-expressions%29). > **Note:** - Matching wont work if the content uses any `List continue` styles or is mapped by default or directly to PSML ``. - There is no need to prefix regular expressions with `^` because the import automatically only matches the beginning of a line. ##### Import manual numbering in DOCX in a PSML `` From the default configuration shown above, values, that match this regular expression are output in an `` element with an attribute of `@label="numbering-lowercase"`: ```xml ``` ##### Import manual numbering in DOCX as a `prefix` attribute on a PSML ` or ` From the default configuration shown above, values that match any of the following regular expressions are output as the `"value"` of a `@prefix` attribute in a ` `or `` element: ```xml ``` **Import manual numbering in DOCX as a `prefix` attribute on a PSML **` or ` that has an attribute `level` value of `1` From the default configuration shown above, values that match the following regular expression group (the pattern between the parenthesis) are output as the `"value"` of a `@prefix` attribute in a `` element. For example `5a|{tab}` becomes ``. *Requires pso-docx v1.5.0 or later:* ```xml ``` **Example – Import manual numbering as attribute `prefix` on a PSML `` and ``** The following examples show the import of manual numbering in a custom Word document imported using the following import configuration: ```xml ``` **Example DOCX ** ![Import DOCX - Manual numbers as prefixes - Example](/content/guide/publishing/ant_api/extensions/microsoft_word_docx_import_config_usage_files/docx-import-manual-numbers-as-prefix-custom-example.png) **Example in PageSeeder document view mode** ![DOCX import – manual numbers as prefix – custom example - PageSeeder document view](/content/guide/publishing/ant_api/extensions/microsoft_word_docx_import_config_usage_files/docx-import-manual-numbers-as-prefix-custom-example-ps-document-view.png) **Example PSML** ![Import DOCX - Manual numbers as prefixes - Example PSML view 1](/content/guide/publishing/ant_api/extensions/microsoft_word_docx_import_config_usage_files/docx-import-manual-numbers-as-prefix-custom-example-psml-view.png) ![Import DOCX - Manual numbers as prefixes - Example PSML view 2](/content/guide/publishing/ant_api/extensions/microsoft_word_docx_import_config_usage_files/docx-import-manual-numbers-as-prefix-custom-example-psml-view-2.png) ##### Import manual numbering in DOCX as a `numbering` attribute on a PSML ` or ` Values that match the following regular expression output an `@numbering="true"` attribute. ```xml ``` ### Semantics and formatting – \ For general transformations of DOCX styles to PSML, the options are `, ` and ``. There are descriptions of the examples below. ```xml             ``` #### `` Determines the content to **NOT** process. For example, to discard the Table of Contents paragraphs from Word, use the following: ```xml ``` #### \ See examples above. ##### \ Process Word paragraph styles with no explicit mapping using `` or ``, and the following options for the `@value` attribute: - `"para"` – Word paragraph styles with no explicit mapping are output as a PSML `` element. - `"block"` – Word paragraph styles without an explicit mapping will be output as a PSML `` element with the `"value"` of a `@label` attribute equal to the Word paragraph style `ID` (**note**: the `ID` is different from Word paragraph style name). > **Note:** To get the style `ID` from the Word style `name`, Word strips underscores and spaces, but preserves hyphens. ##### \ Defines general rule for any Word character style not mapped with ``. `@value` supports the following: - `"none"` – Word character styles without an explicit mapping are stripped. - `"inline`" – this option converts Word character styles to a PSML `` element with the `“value”` of a `@label` attribute equal to the Word character style `ID` (**note:** the `ID` is different from Word character style name). ##### \ Capture Word [smart tag](http://office.microsoft.com/en-au/word-help/about-smart-tags-HP003083304.aspx) information as an inline label equal to the smart tag `ID`, by setting the `@keep` attribute value to `"true"`. Otherwise, the import will discard smart-tag markup. ##### \ To determine whether to process internal references as PSML `` or `` elements, set the `@psmlelement` attribute to a value of `"link"` or `"xref"` (default is `"xref"`). Using `"link"` also imports all bookmarks as `` elements. *Requires pso-docx v0.8.3 or higher.* #### \ These rules transform Word paragraph or character styles into the following PSML elements: - Word paragraph styles - `` - `` - `` - `` - `` - Word character styles: - `` - `` - `` - `` - `` There is a description of these rules below. ```xml ``` The rules above perform the following transformations. > **Note:** Creating a label through the import process requires adding that label to the [PSML document template](../../../configuration/psml/psml_document_template.md) or [label config](../../../../reference/folders_and_files/project_template/Label.md) in order to edit or search. - A Word paragraph style `ID` of `Heading1` transforms to `` with an attribute `@level="1"`. - A Word paragraph style `ID` `Heading2` transforms to ``. - A Word paragraph style `ID` `Heading3` transforms to an `` label with an attribute `@label="instruction"`. - A Word paragraph style `ID``Heading4` transforms to `` with an attribute `@label="requirement"`. - A Word paragraph style `ID` `Heading5` transforms to `` with an attribute `@level="5"`, and a `` element wrapper with attribute `@label="Section_highlight"`. - A Word paragraph style `ID` `HTMLCode` transforms to ``. - A Word paragraph style `ID` `HTMLpreformatted` transforms to ``. - A Word paragraph style `ID` `TableCaption` transforms to `` for all tables. - A Word paragraph style `ID` `Strong` transforms to ``. *Requires** pso-docx v1.1.0 or higher.* - A Word paragraph style `ID` `Emphasis` transforms to ``. *Requires pso-docx v1.1.0 or higher.* - A Word paragraph style `ID` `IntenseEmphasis` transforms to ``. *Requires pso-docx v1.1.0 or higher.* #### `` – `@psmlelement` ##### `"heading"` Possible child elements are: ```xml ``` - `` with attribute `@value` ranging from `"1"` to `"6"`. - `