If you are experiencing problems with the MS Word import, you may find useful information about the most common issues in the following sections.
Note
If you are experiencing different types of problems with your MS Word import, please contact customer support for help.
If the import process is not complete, make sure to properly Prepare MS Word Document for Import. It needs to have a title and use headings correctly as a minimum.
If Paligo's Word import process completes successfully but the import folders contain no topics, or some topics are missing, it is likely due to incorrect formatting.
Make sure that your Word document has a title and uses headings correctly, as described in Prepare MS Word Document for Import.
If you prepare your MS Word document correctly, the import should create a topic for each section of content that has a heading. If you continue to experience problems, contact customer support for help.
If you imported a table from MS Word and the table extends beyond the boundaries of the Paligo editor, this is due to the table being too wide. You can still edit it in Paligo - use the scroll bar at the bottom of the Paligo editor to scroll horizontally to the additional cells.
For HTML outputs, Paligo will add a scrollbar feature to the web page so that your readers can scroll to cells beyond the display area.
For PDF outputs, the table will go off the edge of the page. For this reason, you should consider setting the table to display as landscape rather than portrait, see Rotate a Table (PDF). You may also need to redesign the table if it is too large for the page size, for example, you may need to create several smaller tables instead.
If you imported content from MS Word into Paligo and the list numbering is incorrect, the first thing to do is publish the content. The published content may have the correct numbering. This is because Paligo cannot use some of Word's numbering systems in the editor, but it can give a list item an override attribute with a number. This number is only applied when the content is published.
Another potential cause of incorrect numbering is that a list may be imported as several lists rather than one list. This can happen if the MS Word content has text or images that break the flow of the list and you used Word's "continue numbering" feature to make the list look correct. For example, let's say you had this list in MS Word:
The image has been added outside of the list item for step 3. This breaks the flow of the list, and step 4 is actually a new list. Word's "continue numbering" feature makes it look like a continuation of the previous list.
When this is imported into Paligo, you get step 4 numbered as 1, like this:
This is because step 4 is actually a new list and the "continue numbering" feature is not recognised.
To solve this, you can either:
-
Fix it in the MS Word file
We recommend that you insert the image (or any text between steps) as a new list item and then use backspace to delete the numbering. This will give you an indented image (or text) that is part of the preceding list item, which is correct formatting. Then step 4 will be a list item in the same list rather than a new list.
For details on adding content inside a list item, see Prepare MS Word Document for Import.
-
Use the XML tree in Paligo to move the image inside listitem 3. Then add list item 4 to the end of the first list. Finally, remove the extra orderedlist element (it represents the second list).
If your lists in MS Word use a soft return (shift + enter) to place content on the next line, it will be imported into Paligo inside a literallayout
element. You can see it in the Paligo editor as there is a shaded box around the content and, if you select it, you can see the literallayout element in the Element Structure Menu.
While this is valid, it is not the way text and images are usually added to a list item in Paligo.
The more commonly used structure for this content is:
<orderedlist> <listitem> <para>This is step one.</para> <para>In MS Word, this line was created by using a soft return at the end of the previous line.</para> </listitem> <listitem> <para>This is step two.</para> </listitem> </orderedlist>
So the difference is that the extra line of text in the step is inside an additional para
element rather than a literallayout
element. If the content in the list was an image, it would be inside a mediaobject
structure instead. But in both cases, they should be inside the list item.
To correct your content you can either:
-
Edit the lists in MS Word
Remove the soft returns and then add a new list item for the text or image. This will create an extra step that you do not want, but that is intended for now. Next, position the cursor at the start of the new list item and press backspace. This will make the text/image an indented part of the previous list item. In this form, it will import into Paligo cleanly, with no
literallayout
element.For details on adding content inside a list item, see Prepare MS Word Document for Import
-
Edit the lists in Paligo
For text between lists, add a
para
element inside thelistitem
element and then add your text content to that.For images between lists, either insert an image inside the
listitem
element or use the XML tree to move the mediaobject element into thelistitem
.
Paligo imports Microsoft Word number lists as ordered lists. If you want them to be imported as procedures, it may be possible to do that as a customization project (there is usually a fee for customization projects). Please contact customer support for details.
The Paligo editor always shows tables as portrait. For HTML outputs, wide tables are given a scroll bar so that users can access all of the data in the table. For PDF outputs, you can set them to display in landscape mode instead, see Rotate a Table (PDF).
Comments
0 comments
Article is closed for comments.