This item is migrated to the Telerik Document Processing portal: 
http://feedback.telerik.com/Project/184/Feedback/Details/190082 
Please use the new item for commenting, voting and subscribing instead of this one.

Workaround:

private static void WorkaroundFieldsIssue(RadFlowDocument flowdocument)
{
    foreach (FieldCharacter fieldCharacter in flowdocument.EnumerateChildrenOfType<FieldCharacter>().ToList())
    {
        // only for start
        if (fieldCharacter.FieldCharacterType == FieldCharacterType.Start)
        {
            if (fieldCharacter.FieldInfo.Separator != null && fieldCharacter.FieldInfo.Separator.Parent == null)
            {
                Paragraph parent = fieldCharacter.FieldInfo.End.Paragraph;
                int index = parent.Inlines.IndexOf(fieldCharacter.FieldInfo.End);

                fieldCharacter.FieldInfo.End.Paragraph.Inlines.Insert(index, fieldCharacter.FieldInfo.Separator);
            }
        }
    }
}
This item is migrated to the Telerik Document Processing portal: 
http://feedback.telerik.com/Project/184/Feedback/Details/190083 
Please use the new item for commenting, voting and subscribing instead of this one.

Is there any way to easily see the comprehensive differences between two versions? We have an application that is still on version 2012.1.326 that we are intending to upgrade to the latest, but there is no simple way to tell what breaking changes might have been made. Our customer is asking us what features may no longer work as expected, but it would be practically impossible to go through every single set of release notes because there are so many between now and then. A simple replacement to "see what happens" isn't really feasible either because the application is so large and some of it was written by a third party.
---------------------------------------
We’ve introduced the Telerik API Analyzer tool that helps determine the problematic areas when upgrading a WPF, WinForms or ASP.NET Web-Forms application to a newer version of our controls. You can read more about the tool in this blog post: http://www.telerik.com/blogs/api-analyzer-helps-upgrading-telerik-projects.

This item is migrated to the Telerik Document Processing portal: 
http://feedback.telerik.com/Project/184/Feedback/Details/190086 
Please use the new item for commenting, voting and subscribing instead of this one.

The feature will be available in our official release Q1 2016.

This item is migrated to the Telerik Document Processing portal: 
http://feedback.telerik.com/Project/184/Feedback/Details/190089 
Please use the new item for commenting, voting and subscribing instead of this one.

This item is migrated to the Telerik Document Processing portal: 
http://feedback.telerik.com/Project/184/Feedback/Details/190091 
Please use the new item for commenting, voting and subscribing instead of this one.

The fix will be available in our next LIB release (v. 2016.01.125).

This item is migrated to the Telerik Document Processing portal: 
http://feedback.telerik.com/Project/184/Feedback/Details/190094 
Please use the new item for commenting, voting and subscribing instead of this one.

The AltChunk element is responsible for embedding external content into documents.
This item is migrated to the Telerik Document Processing portal: 
http://feedback.telerik.com/Project/184/Feedback/Details/190095 
Please use the new item for commenting, voting and subscribing instead of this one.

Fixed in LIB Version 2015.3.1130.
Note that the MinimizeButtonStyle used in the OutlookBar control is now renamed to OutlookBarMinimizeButtonStyle.

Will be available in Q1 2016 Release.

The font size in the table does not respect the CSS for the corresponding class. There is similar issue with <li /> element. 
This item is migrated to the Telerik Document Processing portal: 
http://feedback.telerik.com/Project/184/Feedback/Details/190102 
Please use the new item for commenting, voting and subscribing instead of this one.

'thead' HTML element represents table row that should be repeated at the top of each page. MS Word maps this to TableRow with RepeatOnEveryPage set to true. This works for both export and import.
This item is migrated to the Telerik Document Processing portal: 
http://feedback.telerik.com/Project/184/Feedback/Details/190104 
Please use the new item for commenting, voting and subscribing instead of this one.

This item is migrated to the Telerik Document Processing portal: 
http://feedback.telerik.com/Project/184/Feedback/Details/190107 
Please use the new item for commenting, voting and subscribing instead of this one.

This item is migrated to the Telerik Document Processing portal: 
http://feedback.telerik.com/Project/184/Feedback/Details/190237 
Please use the new item for commenting, voting and subscribing instead of this one.

This item is migrated to the Telerik Document Processing portal: 
http://feedback.telerik.com/Project/184/Feedback/Details/190003 
Please use the new item for commenting, voting and subscribing instead of this one.

The documents produced by WordsProcessing and SpreadProcessing are compliant with the specification. But, Open Office, Numbers and Pages (the default applications for working with .docx and .xlsx on MAC) are unable to open documents where the target attribute of the relationships of the documents is specified as an URI, instead of as a relative reference. According to the specification (Ecma Office Open XML Part 2 - Open Packaging Conventions) both formats are acceptable.

The issue is in the relationships parts, relationship element. The Target attribute can be either a URI (Target="/word/theme/theme1.xml") or a relative reference (Target="theme/theme1.xml") as stated in the specification. The document processing libraries use URI, which OpenOffice is unable to interpret, despite them being allowed by the specification.

The fix will be available in our official release Q2 2016.

 This is content stream operator that is used to close, fill and then stroke a PDF path geometry.
This item is migrated to the Telerik Document Processing portal: 
http://feedback.telerik.com/Project/184/Feedback/Details/190111 
Please use the new item for commenting, voting and subscribing instead of this one.