This feature includes: table of figure, table of tables etc. TOC field contains PageRef fields inside it. To update it, we will need pagination (layout) support and PageRef fields implementation. Also TOC update can be influenced by TC fields presence in the document. Implement export to PDF.
Our application works with a document storage and we use RadRichTextBox to allow users edit and view the documents. Unfortunately, many documents cannot be opened due to the following exception we get:
Unable to cast object of type 'Telerik.Windows.Documents.Model.FieldRangeStart' to type 'Telerik.Windows.Documents.Model.AnnotationRangeEnd
As result we receive complains from our users. Could you please facilitate with solving it?
I have attached a simple test application with the problematic document as well the stacktrace.
The attached sample project below demonstrates a possible workaround for PAGE and NUMPAGES fields when exporting to PDF. The demo shows how to generate document from scratch containing PAGE and NUMPAGES fields and export it to PDF.
/> doesn't raise the HtmlImportSettings.LoadFromUri event on import, as we currently require type="text\css" to be specified explicitly.
typeattribute, but is actually now recommended practice.
Think of improving the message of the exception we throw if no data is loaded.
Workaround: set type explicitly:
Add support for shapes, and especially for shapes with textual content. In OOXML, shapes are represented by the wps:wsp element, and shapes with textual content by <wps:txbx>, <w:txbxContent>. Such shape can be added to a Word document using the Insert -> Text -> Text Box -> Draw Text Box, or through a shape's context menu -> Add Text. Do not confuse these shapes with Text/Rich Text content controls (see https://feedback.telerik.com/Project/184/Feedback/Details/190057 )
Currently some properties are supported only in their shorthand forms, and others - only in their longhand forms: - 'background' shorthand is not supported. - 'margin' shorthand is not supported. - 'border' shorthand is supported, but 'border-bottom-color', 'border-bottom-style', 'border-bottom-width', 'border-left-color', 'border-left-style', 'border-left-width', 'border-right-color', 'border-right-style', 'border-right-width', 'border-style', 'border-top-color', 'border-top-style', 'border-top-width', 'border-width' are not supported.
When the document contains an image that is defined as an external resource but is not available in the specified location and cannot be found, a KeyNotFoundException is thrown. Handle this exception and replace the missing image with a default one for such cases. Consider exposing an option to notify the user about this error.
When the imported html contains an attribute of the type width="", Wordsprocessing throws ArgumentException and does not import the document.
Importing an image from HTML with URI as a source, which has applied only width or height and exporting it to PDF (which forces getting the image data so it can be drawn) leads to an incorrect value of 1 (a default value) for the dimension that is not specified.
When the document contains an image with extension, which is not among the supported ones, a KeyNotFoundException is thrown during Import.
An ArgumentException is thrown when importing HTML containing standard and non-standard pseudo classes or pseudo elements. The concreete scenario is the following: .myclass::-webkit-scrollbar or .myclass::-ms-expand The message of the exception is similar to this: "Unexpected character found at position [X]: ".. scrollbar::>>-<<webkit-scrollbar"".