When a TrueType font is defined, the mapping of character codes to glyph indices depends on the built-in cmap table mappings defined in the font and the Encoding property defined in the PDF dictionary.

However, the current implementation maps all characters with cmap tables for Microsoft Symbolic and Macintosh Roman, which causes incorrect mapping results, e.g. space characters are mapped to an Ê glyph.

The issue is also described in the following public item: TryGetCharCode for OpenTypeFont uses wrong cmap and returns wrong charcode.

Workaround: Change the font  of the TextBoxField's widget appearance:
foreach (var widget in field.Widgets)
{
    widget.TextProperties.Font = FontsRepository.Helvetica;
}

The Hyperlink field is wrongly exported when the Code fragment is divided into several text fragments.

Actual:

Expected:

Workaround: Iterate the document content after importing it into RadFlowDocument in order to modify the Code fragment:

bool isBetweenStartAndSeparation = false;
string fieldInfoText = string.Empty;
int startIndex = 0;
IEnumerable<Paragraph> paragraphs = document.EnumerateChildrenOfType<Paragraph>();
foreach (Paragraph paragraph in paragraphs)
{
	foreach (InlineBase inline in paragraph.Inlines.ToList())
	{
		if (inline is FieldCharacter)
		{
			FieldCharacter fieldCharacter = inline as FieldCharacter;
			if (fieldCharacter.FieldCharacterType == FieldCharacterType.Separator)
			{
				isBetweenStartAndSeparation = false;
				Run run = new Run(this.document)
				{
					Text = fieldInfoText
				};

				paragraph.Inlines.Insert(startIndex, run);
			}
			else if (fieldCharacter.FieldCharacterType == FieldCharacterType.Start)
			{
				isBetweenStartAndSeparation = true;
				startIndex = paragraph.Inlines.IndexOf(inline) + 1;
				fieldInfoText = fieldCharacter.FieldInfo.GetCode().Trim().ToLowerInvariant();
			}
		}
		else if (isBetweenStartAndSeparation)
		{
			paragraph.Inlines.Remove(inline);
		}
	}
}

The Nonbreaking space is exported as a Unicode character instead of the appropriate Control word.

Actual: "\n160?"

Expected: "\~"

According to the RTF specification: The valid values for the "\ls" index are from 1 to 2000.

They are currently exported from zero or "\ls0".

Make it possible to import HTML file with an external style sheet, without the need to handle the LoadStyleSheetFromUri event in HtmlImportSettings. If the URL is correct the data can be internally downloaded.

The cell contains the following data in OOXML:

<f>SUM(1,2,3)</f> - The formula
<v>6</v> - the calculated value

The formula value is imported, but the calculated value is skipped. The feature will be useful if Manual calculation option is supported: https://feedback.telerik.com/Project/184/Feedback/Details/191275-spreadsheet-add-support-for-different-calculation-options-automatic-or-manual

When calling SpreadExporter.CreateWorkbookExporter method and referencing Trial assemblies an exception is thrown: System.ArgumentException: 'An item with the same key has already been added.'

This behavior is observed both with the NuGet packages and DLLs.

It is not observed with Trial DLLs version 2020.3.1019

When exporting a document referencing PdfProcessing`s .NET Standard assemblies with PdfComplianceLevel set an exception is thrown.

When merging or splitting files that contain the "159 '\u009f'" char, ArgumentException("The encoding is not supported.") is thrown.

This issue can also result in ArgumentException in client applications with the message: currentIndirectObject should be null.

Workaround:

Use PdfFormatProvider or reflection to register the char (check the comments).