Hello,

I'm using Telerik Documents Processing 2023.1.410

With WordsProcessing, if I add a table in a footer it will automatically add a space after the table

Here an example, my table is the same size as my image in background and I removed all margin of the section:

Here the code:

Footer footer = section.Footers.Add(HeaderFooterType.Default)
section.PageMargins = new Padding(0,96,96,0);
section.FooterBottomMargin = 0;

Table table = footer.Blocks.AddTable();
TableRow row = table.Rows.AddTableRow();
TableCell cell = row.Cells.AddTableCell();
Paragraph paragraph = cell.Blocks.AddParagraph();
paragraph.Inlines.AddRun("Something");

I didn't any properties to manage spaces around a Table like in Paragraph.

It can be reproduced without the image

Work around:

If I add a new paragraph at the end and remove all spaces of this paragraph then it works

Here the code added:

paragraph = footer.Blocks.AddParagraph();
paragraph.Spacing.SpacingAfter = 0;
paragraph.Spacing.SpacingBefore = 0;
paragraph.Spacing.LineSpacing = 0;

Regards,
Hervouet Thomas

The value of the TextBoxField is not visible until the field is clicked.

Workaround: Force content update:

foreach (var widget in textBoxField.Widgets)
{
    widget.RecalculateContent();
}

If the update still doesn't fix the issue, change the font prior to setting the value of the field:

foreach (var widget in textBoxField.Widgets)
{
    widget.TextProperties.Font = FontsRepository.Helvetica;
}

InvalidCastException is thrown when a name start character is followed by a literal string start character.

System.InvalidCastException: Unable to cast object of type 'Telerik.Windows.Documents.Fixed.FormatProviders.Pdf.Model.Types.PdfInt' to type 'Telerik.Windows.Documents.Fixed.FormatProviders.Pdf.Model.Types.PdfName'.

When some character is not supported by the font, the fallback mechanism should try finding some other font that is capable of rendering the unsupported character. However, RadPdfProcessing fallback mechanism does not always find the correct font which sometimes result in wrong glyph visualization or in missing glyph.

Workaround: Font that supports these special characters may be used. This way the fallback mechanism will not be needed to export the PDF text.

When Separation color space with "name" set as None it is falling back to an "alternateSpace" (color space) instead.

From the Pdf specification:
A Separation color space is defined as follows:
[ /Separation name alternateSpace tintTransform ]

Observed:

The None value is ignored and the color space fallbacks to the Lab color space.

According to PDF specification, the field value should be specified in the "V" entry of the corresponding PDF dictionary. However, some PDF producers are skipping this entry and are setting only the Widgets appearance states. As most viewers manage to show the radio button and checkbox as selected, we should handle this scenario and import the field values based on the related widgets when this value is not explicitly set with the field's V entry.

For some documents, the clippings and colors of the geometries are modified on an import-export scenario.