Unplanned
Last Updated: 28 May 2020 19:40 by ADMIN
Currently, importing a document with non-embedded TrueType font will result in a font instance with an empty font source. Support should be added for providing custom font data of TrueType fonts during document import.
Unplanned
Last Updated: 28 May 2020 12:26 by ADMIN
CellSelection.SetValue method causes memory leak of CellReferenceRangeExpression objects in some cases when cell value is referenced by formulas. The memory leak is small, but the remaining CellReferenceRangeExpression continue to listen to some events, causing performance issues when their number become large - the time to set the value increases with each set.
Duplicated
Last Updated: 28 May 2020 12:15 by ADMIN
Created by: Dimitar
Comments: 0
Category: WordsProcessing
Type: Bug Report
1

Borders are not correctly imported from HTML.

Workaround: Set borders in code:

var tables = document.EnumerateChildrenOfType<Table>();

var border = new Border(1, BorderStyle.Single, new ThemableColor(Colors.Black));

foreach (var table in tables)
{
    table.Borders = new TableBorders(border);

    foreach (var row in table.Rows)
    {
        foreach (var cell in row.Cells)
        {
            cell.Borders = new TableCellBorders(border);
        }
    }
}

Unplanned
Last Updated: 28 May 2020 08:20 by ADMIN
By specification, the URI property of URI Actions is encoded in 7-bit ASCII string. For this reason, our current implementation relies on that the property will be of type PdfLiteralString. However, in cases such as password-encrypted documents, the property may be encoded with PdfHexString which leads to InvalidCastException: 'Unable to cast object of type Telerik.Windows.Documents.Fixed.FormatProviders.Pdf.Model.Types.PdfHexString' to type 'Telerik.Windows.Documents.Fixed.FormatProviders.Pdf.Model.Types.PdfLiteralString'.', on document import.
Unplanned
Last Updated: 28 May 2020 08:16 by ADMIN
By specification, FitH destinations are defined with page and top position. A null value for top specifies that the current value of that parameter is to be retained unchanged. However, importing such a document with PdfProcessing leads to ArgumentOutOfRangeException:  'Index was out of range. Must be non-negative and less than the size of the collection.
Parameter name: index'.
Unplanned
Last Updated: 28 May 2020 07:58 by ADMIN
When importing document with text containing char code mapped to .notdef glyph name an ArgumentException: 'The encoding is not supported.' is thrown.
Unplanned
Last Updated: 27 May 2020 14:01 by Hector
Importing document containing TextBox widgets with NormalContentSource defining text properties, such as FontSize and Position, are exported with incorrect appearance when the value of the field is modified.
Unplanned
Last Updated: 27 May 2020 08:21 by ADMIN
NullReferenceException has thrown when importing a form XObject with null Resources in PDF dictionary.
In Development
Last Updated: 26 May 2020 11:05 by ADMIN
Implement text orientation for cell content import/export from/to XLSX format
Unplanned
Last Updated: 26 May 2020 10:54 by ADMIN
Created by: ANTONIO
Comments: 0
Category: PdfProcessing
Type: Feature Request
2
Add a PDF document validator to validate (before the import of the document) an existing PDF document.
Unplanned
Last Updated: 26 May 2020 09:25 by ADMIN

NullReferenceException when the FindOptions does not contain start cell

Workaround:

Set StatCell like this:

FindOptions options = new FindOptions()
{
    FindWhat = "Record",
    MatchEntireCellContents = true,
    StartCell = new WorksheetCellIndex(workbook.Worksheets[0], new CellIndex(0,0))

};
Completed
Last Updated: 26 May 2020 09:05 by ADMIN
Release LIB 2020.2.525 (05/25/2020)
Unplanned
Last Updated: 22 May 2020 09:51 by ADMIN
ADMIN
Created by: Deyan
Comments: 15
Category: SpreadProcessing
Type: Feature Request
17
Provide ability for working with comments in a spreadsheet document.
Duplicated
Last Updated: 21 May 2020 11:00 by ADMIN
Created by: Martin
Comments: 0
Category: WordsProcessing
Type: Feature Request
0

Revisions in WordprocessingML provide a mechanism for storing information about the evolution of the
document (i.e. the set of modifications made to a document by one or more authors).

Unplanned
Last Updated: 21 May 2020 10:12 by Denny

Hi Telerik,

 

I would like to request 1 feature to be added in Current RADGRID control which is to exporting grid data to into Excel 2016 version.

We need this feature because one of our supporting application will work only with  Excel 2016 version, where as the current RADGRID conversion only able to export to EXCEL 2007 (excel 12) format.

 

Thank you.

 

 

Unplanned
Last Updated: 20 May 2020 11:34 by ADMIN
Created by: Martin
Comments: 0
Category: WordsProcessing
Type: Feature Request
0
 

This element specifies that this run contains literal text which shall be displayed in the document. The delText
element shall be used for all text runs which are part of a region of text that is contained in a deleted region
using the del element.

This is the preview (This is deleted text) of the following XML:

<w:p>
	<w:r>
		<w:t xml:space="preserve">This is </w:t>
	</w:r>
	<w:del w:author="Cooper W.">
		<w:r>
			<w:delText>deleted text</w:delText>
		</w:r>
	</w:del>
</w:p>

 

In Development
Last Updated: 19 May 2020 15:15 by ADMIN
The decimal values are exported using the symbol defined in the thread culture. However, they should always use the period as a decimal symbol. The wrong value can lead to wrong resizing of the image inside the exported document.

Workaround: Change the current culture settings of the thread before exporting:
string cultureName = Thread.CurrentThread.CurrentCulture.Name;
CultureInfo cultureInfo= new CultureInfo(cultureName);
if (cultureInfo.NumberFormat.NumberDecimalSeparator != ".")
{
    cultureInfo.NumberFormat.NumberDecimalSeparator = ".";
    Thread.CurrentThread.CurrentCulture = cultureInfo;
}

Unplanned
Last Updated: 19 May 2020 12:55 by ADMIN
Created by: Yiannis
Comments: 3
Category: WordsProcessing
Type: Bug Report
0

Dear all,

 

It seems that the RtfFormatProvider generates invalid alternative text in the "{\listtext }" RTF group when saving a RadFlowDocument that contains numbered paragraphs.

The text seems to always be "{N}" when level N of the list is used.

While this is no problem for readers that adhere to the latest RTF standard, RichEdit-based controls and WordPad in Windows 8-10 have issues with it and do not load the list. These versions of RichEdit are otherwise capable of reading list tables.

Please note that I am not talking about loading the document to Windows 7 RichEdit, since that does not support list tables at all (it is stuck to the Word '95 "{\*\pn ...}" format).

I submit a simple list example that can be read by WordPad in Windows 10 and the outcome after loading and saving it back with RtfFormatProvider.

The outcome loads correctly in Word and RadRichtextBox, but not in WordPad. Removing or correcting the "{\listtext ...}" for each paragraph manually makes the list load properly in WordPad.

 

BTW, I strongly disagree with the nonexistent support for the Word '95 RTF numbering format, since it either forces us to use some other product or create our own code to parse and massage the RTF prior to loading into your products.

The problem is great, as many controls/products are still based on the RichEdit control (including some versions of our products).

It is not only old RTF data that needs migration, but pasted content from WordPad or other applications as well, since otherwise numbering is killed, without even displaying any text present in "{\pntext ... }" groups, intended for readers that do not understand "{\*\pn ...}".

Finally, to make things worse, even in Windows 10, RichEdit uses Word '95 format for saving single-level lists (resulting in content with mixed list formats).

 

Anyway, thank you for your time.

Unplanned
Last Updated: 19 May 2020 11:47 by ADMIN
 InvalidCastException when importing a file with missing space. The file contains no space between the objects declarations and the page content and this is why the exception occurs.
Completed
Last Updated: 15 May 2020 08:58 by ADMIN
Release LIB 2020.2.518 (18.05.2020)
The image size of EMF/WMF images is wrongly exported when exporting to PDF.
1 2 3 4 5 6