Skip to main content


 

Symptoms


When users are trying to paste a copied content from Microsoft Word with rich formatting (Tables, Highlights, Font formatting), the OOTB rich text editor is not fully accepting the operations.

Pasting the highly formatted content from Microsoft word causes loss of spaces between the words, which in turn causes spelling mistakes. This is a very common and very important practice in our organization, as the content is usually composed in Microsoft Word to eliminate any spelling or formatting mistakes, due to high level of sensitivity related to the content, in terms of audience and matter involved in the workflow.

Apart from that, people have also noticed additional spacing/gaps or increased margins/padding after pasting the content, especially the table structures.


 

Diagnoses


K2 labs feedback:

This is unfortunately not possible as the copy/paste part is done by Telerik code and also the nature of a Word doc vs Web has limitations on presenting the rich formatting, as a Word doc is not HTML based

as a workaround You can use Google Docs - Word to create a table and paste it into the rich text control. This way the table is actually HTML and rendered correctly within the Telerik controls

Please send this response back as a workaround as it is out of our hands regarding the formatting of non HTML Word content.

 

Resolution

K2 labs feedback:

This is unfortunately not possible as the copy/paste part is done by Telerik code and also the nature of a Word doc vs Web has limitations on presenting the rich formatting, as a Word doc is not HTML based

as a workaround You can use Google Docs - Word to create a table and paste it into the rich text control. This way the table is actually HTML and rendered correctly within the Telerik controls

Please send this response back as a workaround as it is out of our hands regarding the formatting of non HTML Word content.
"




 

This is also an issue with any existing Rich Text fields that are filled using SharePoint OOB Rich Text editor.  The HTML created for the text references the default SharePoint theme/style for that particular site/page.  Explicit fonts/sizes/color etc., are not set unless manually set by the user in the editor.  K2 needs to be able to use the default SharePoint theme as its own, as an option in these Rich Text files.  This would be an issue for any user trying to create a SmartForm containing any existing Rich Text field containing data entered using the OOB SharePoint Rich Text interface.


Reply