This will allow watermarks to be set on the document pages.

The feature will be available in our official release 2015 Q2 .

I know it sounds a little bit wired, but think of it:

Often we have to debug our programs at client side. What if we just could open a Powershell console inside our WPF app and inspect variables or start some maintenance scripts? 

As a starting point for the integration look the sample of Doug Finke's book "Windows Powershell for Developers" where he shows in chapter 5 how to do it. The sample is available on github: https://github.com/dfinke/powershell-for-developers/tree/master/chapter05

It would be perfect, if you provide a powershell editor console control with commandline history and so on. So one has just to throw in the WPF-control, provide the root application object and then we go.

I think this would be a unique control in your set of components and useful for nearly every developer!

There're errors in the dutch translations-dll, the two I corrected locally by a custom LocalizationManager are:

Item GridViewGroupPanelText should be:
Versleep de kolomkoptekst en plaats deze hier om op deze kolom te groeperen

Item MoveFirst should be:
Verplaats Eerste

but there are probably more that need correction.

In the light of Microsoft announcing that they are open-sourcing the .NET framework[1], I think it will be really beneficial if you put your controls on GitHub, so the community can participate in the development. 
For example interested parties could implement solutions for more advanced scenarios themselves (I know you guys have to prioritize your work), instead of using ugly workarounds in their code. There are many cases where support for these scenarios is more appropriate inside the controls. Presently, any effort I would make with the provided source code for current release would be wasted when the next release arrives. Also, open discussion on how would be best to incorporate new features in the overall architecture would benefit everyone.

Another way of looking at this is when .NET becomes well supported on other platforms (Linux, OS X, ...) it would be hard to port your controls without the help of a larger team. The Linux community in general is especially proactive w.r.t. open source projects.

I hope you can agree that open development (discussions, code reviews, contributions, etc.) will give you a strong competitive advantage.

[1] http://blogs.msdn.com/b/dotnet/archive/2014/11/12/net-core-is-open-source.aspx

Tab stops for paragraphs and default tab stops for document.

I'd really like a WPF (and Silverlight) version of the Windows Phone Conversation View control.

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

A button that once clicked shows a circular menu with additional choices the user can select.

Add a new media encoding control that can create video files frame by frame (from images) together with an audio track. Maybe support avi, mp4, wmv...

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

Content in cells should be centered vertically and cells should have cell spacing and margins to make them look similarly to browsers.
This item is migrated to the Telerik Document Processing portal: 
http://feedback.telerik.com/Project/184/Feedback/Details/190033 
Please use the new item for commenting, voting and subscribing instead of this one.

Generally, allow more straightforward setters of style related properties without going through 2-4 levels of temporary objects.  For example, when dealing with tables, there is no obvious way to set line spacing or paragraph spacing globally for the table.  Should have TableCell.Blocks.AddText("New Text") instead of AddParagraph, which provides spacing you don't want or need.

Also, when you want to set the FontSize, FontWeight, and FontFamily all at once, there is no easy way to do that.  Also no global way to do that for a section, page, table, etc.

The above would make it a LOT easier to create documents programmatically.  I would like to see more parameterized constructors for common style attributes by type.  You will discover the challenges by creating a richer document from scratch with several tables, styles, left and right justified content on the same line, etc.  Same for easily setting header and footer content.

Thanks!  Great work so far, I love it!

Make legend item of BarSeries reflect it's visual style. For example, if I'll make a BarSeries with a border like this:
<Style TargetType="Border">
    <Setter Property="Background" Value="Transparent" />
    <Setter Property="BorderThickness" Value="1" />
    <Setter Property="BorderBrush" Value="{StaticResource chartRed}" />
</Style>

then there won't be a rectangle in a legend as expected (it will show a transparent one instead, without border).

REASON FOR DECLINATION:
The RadLegend is a standalone control which allows for customization of the legend item visuals (one can use the ItemTemplate property of the RadLegend to control the legend item's appearance or can retemplate the LegendItemControl). There is no direct link between the ChartView and the RadLegend control and the appearance of the legend elements can be done by framework means such as Style, DataTemplate and ControlTemplate. The suggested way of manipulating the look of the chart legend item is making use of the ItemTemplate property of the RadLegend and the MarkerGeometry property of the series legend settings. 

Make easy way to set Stroke/Fill for all columns in a specific BarSeries. I know about DefaultVisualStyle, but it's too cumbersome to use. For example, Infragistics's chart has this.

Just make use of properties like Background and Stroke.

REASON FOR DECLINATION:
We have decided to decline this feature request because the bar series can be styled via few different approaches, such as a chart palette, default visual style, default visual style selector, point template, point template selector. We consider the DefaultVisualStyle a very framework-friendly approach as it is easy to create and set up a style, in which you can manipulate any of the Border's properties, including adding Bindings to the actual business item. 

Currently, when setting a style to a table/table cell the following syntax is imported properly
.tdborder{border: 1px solid black}
However, if the order of the properties is changed (solid 1px black), the style will not be interpreted.

The fix will be available in our latest LIB release (v. 2015.1.0323).

The value will be skipped when importing the document (<table width=200>). If the size is defined (px or %) as follows <table width=200px> or <table width=200%> then the width value will be respected.

The fix is available in our latest LIB release (v. 2015.1.0316).

When document contains field element without the optional separator character, the import fails.

The fix is available in our latest LIB release (v. 2015.1.0316)