When the current SpanLayoutBox is split (for example by inserting space), the DocumentPosition created with trackDocumentChangeEvents option (with some of the constructor accepting the boolean 'trackDocumentChangeEvents' parameter) jumps back with two symbols.
We've run into the following problem with the RadDocumentEditor: 1. Turn on bold 2. Type some characters. 3. Turn off bold. 4. Insert some text using the Insert method in Telerik.Windows.Documents.Model.RadDocumentEditor. The inserted text is bold; it should ​have no formatting.
Tab stops with visible tab leader (dot, hyphen, underscore) are not exported to PDF. Steps to reproduce: - Start with empty document - In Paragraph Properties dialog, choose Tabs - In Tab dialog, enter Tab stop position = 2, Leader = underscore, and press Set. Press OK - Add a word, press Tab, add another word - Export the text to PDF Expected: the words are separated with underscores in the exported PDF. Actual: the words are separated with blank space in the exported PDF.
When hyperlink is within another annotation so that the outer annotation touches the hyperlink annotation, editing the hyperlink with Insert Hyperlink dialog moves parts of the text of the hyperlink, or the outer annotation. Reproducible with Comments and Bookmarks. Steps to reproduce: Variant 1: 1. Insert Hyperlink 2. Enter some text after the Hyperlink (eg. ' Test') 3. Select the Hyperlink and the text and Insert Comment 4. Edit the target of the hyperlink with the Insert Hyperlink Dialog Expected: The text is not changed. Actual: Space between Hyperlink and the text is moved before the Hyperlink ------------------------------------------------ Variant 2: 1. Insert three words and make the middle hyperlink. 2. Insert comment or bookmark over the hyperlink 3. Edit the target of the hyperlink with the Insert Hyperlink Dialog Expected: Annotations are not reordered Actual: Comment (bookmark) annotations change their places.
The unit that is used by default is px. Allow modification to the default unit, say pt.
Comment references - comments without start and end, just a position in the document, are not imported from docx and RTF document. RTF: such comments don't have their annotation start ('\atrfstart') and end ('\atrfend'), and only have '\atnid' tag. In the specification such comments are referred as 'annotation is associated without an annotation bookmark". Docx: such comments are denoted with 'commentReference' element. Steps to reproduce: 1. In MS Word, add comment without having a selection in the document. 2. Export the document to RTF or docx. 3. Open the exported document in RadRichTextBox. Expected: The comment is imported. Actual: The content is not imported.
Current editing style properties are not modified by Font dialog. Also applying through methods of RadRichTextBox or RadDocumentEditor does not work.
Paragraphs with applied Normal style are currently exported to RTF with \s0 tag. Instead, this tag could be omitted.
If the document contains a simple field without run inside, the import process fails. <w:fldSimple w:instr="page" w:dirty="true"/> The same document with a run inside the field does not cause an error <w:fldSimple w:instr="page" w:dirty="true"> <w:r> <w:t>1</w:t> </w:r> </w:fldSimple>
The thmx file extension is associated with Microsoft Office 2007/2010 themes.The themes are stored in *.thmx files, and the built-in Office themes are stored this way in C:\Program Files\Microsoft Office\Document Themes 12\. The format of a thmx file itself is a ZIP-based format (just like the OpenXML file format). With the use of the thmx templates, it is possible for users to create uniform looking documents in Word (also in Excel and PowerPoint). Workaround: Currently, exporting of RadDocument style sheet is supported only to custom XAML format (http://docs.telerik.com/devtools/wpf/controls/radrichtextbox/features/styles/style-sheets ).
The fix will is available in our LIB release (v. 2015.03.1109).
If an RTF file contains hyperlink with backslashes in the URI, it is imported broken. Usually, similar hyperlinks are pointing to a local file. As a workaround, another syntax may be used. For example, "file:///".
When you are registering an embedded font using the FontManager class, the font family is not rendered. The issue is observable only in WPF.
When a field result fragment has multiple lines only the first and the last paragraph get the proper paragraph style properties.
Add ability to combine revisions from different authors into a single document.
Create different options for pasting(keep formatting, merge formatting, use destination styles). At this point, the document default styles are not copied in the document fragment, thus their loss is observed. When DocumentInheritsDefaultStyleSettings is true and the font settings are like set to different font size/font family, copied text is pasted to MS Word with Verdana font, size 12. Loss of formatting is also observed when copying from RadRichTextBox and pasting in MS Word - the default styles differ.
Add ability to select last paragraph symbol in Section and TableCell. Currently there is no document position after the last paragraph symbol in a document/section/table cell. This means it cannot be part of a DocumentSelection.
When symbol is inserted in underlined word, the underline color of the inserted symbol is always black and doesn't respect the underline color of the word. Also, when Track Changes is ON and some symbols are inserted, the underline color is black instead of being red. Probably the root cause is the same for both behaviors.
When misspelled word is corrected with the spell checker, and the word is just before the comment range end, the comment range end is moved after the previous word. Steps to reproduce: 1. Open RichTextBox and type the following sentence: "This sentence has a wrong speling". 2. Select the entire sentence and click "New Comment" button. 3. The comments range start marker displays before "This...." and comment range end marker displays after "...speling" 4. Right click on word "speling" to change "speling" to "spelling" Result: The spelling gets fixed as expected, but the comment range end moves before the word "spelling".