Hello

Calling MailMerge on a document with a nested repeating group throws NullReferenceException when a merged value contains a line terminator.

All of the following are required to reproduce the crash:

• The group («BeginGroup:Items» … «EndGroup:Items») is nested inside an outer group
• The field whose value contains the newline sits in a later table cell than the group's begin marker
• The value belongs to a non-last record

I have attached a minimal repro demonstrating the bug.

PdfFormatProvider: Table cells are exported with the wrong width when the table is nested in another table and the cells of the nested one have a preferred width set to 100%.

Workaround: Clear the cell PreferredWidth property.

This is happening because the cell with preferred width 100% takes all the available width and all other columns are rendered with no available width which causes the height of the table to grow big.

WORKAROUND: Either clear the cell PreferredWidth property or set it to value which is smaller than 100%.

Merging/importing PDFs with duplicate field names can create one logical RadioButtonField containing widgets from multiple source field nodes. The first node initializes its widget options. Reused duplicate nodes can add additional widgets without assigning RadioOption instances.

The widgets then contain valid "/Off" appearance states, but their model Option property is null. During export, FieldPropertiesExporter accesses widget.Option.Value, causing a "NullReferenceException: Object reference not set to an instance of an object."

Empty paragraphs are exported to PDF with a bigger font size.

Embedding files in a specific order within a PDF can cause an issue when accessing the embedded files in Adobe Acrobat.

When inspecting the main PDF in Adobe Acrobat and attempting to open a specific embedded file, the following dialog is displayed:

Workaround

Embedding the files in a different order may prevent the issue from occurring and can serve as a temporary workaround.

Text is exported to PDF with a larger font size when it has a paragraph style linked to a character style with a fixed size.

InvalidDataException is thrown when importing an XLS document with malformed compressed picture data in the drawing layer.

InvalidCastException is thrown when importing a document that contains structure elements (StructElem) with StructureType (/S) defined with an incorrect integer type (PdfInt) instead of the expected PdfName type.

Endless loop on PDF export when an empty string is assigned to text fields with no source /V and auto-sized default appearance (/DA with 0 Tf).

Workaround: Instead of an empty string (""), set the value to null. Or don't set it at all and leave it unmodified.

When the table is nested in another table with fixed-width and the nested one has more than one cell in the row, where the one has a preferred width set to auto and the other has content that split on more than one row, then the first cell is exported with a wrong width.

For example, when some PDF file has uncompressed contents we may import it and apply better compression to the stream objects. Ensure that all the content inside the document is compressed.

Currently, we have the following options for PDF export optimizations:

• ImageQuality
  

  pdfFormatProvider.ExportSettings.ImageQuality = ImageQuality.Low;

• ImageCompression
  

  pdfFormatProvider.ExportSettings.ImageCompression = new ImageFilterTypes[] { ImageFilterTypes.FlateDecode };

• StreamCompression
  

  pdfFormatProvider.ExportSettings.StreamCompression = new StreamFilterTypes[] { StreamFilterTypes.FlateDecode };

• FontEmbeddingType (Q2 2024)
  

  pdfFormatProvider.ExportSettings.FontEmbeddingType = FontEmbeddingType.Subset;

  We introduced an option of exporting subsets of True Type Fonts (*.ttf) for the .NET Standard version of the library.

PdfFormatProvider: Paragraph-style tab stops are not fully ignored during export, causing unexpected tab positions.

If a PDF with a TextBoxField is created with a corresponding Widget, the text is actually long enough to be broken in more than one line and AllowScroll is set to true, upon opening the file in Adobe, the text is not visible. The field actually does have an appearance which can be seen upon inspection of the document but for some reason it is not visualized.

Another issue seems to be a different manifestation of the same problem: When the text is long and AllowScroll is false, the text will be visible, but will be misplaced. The issue is caused by the length of the text because the same field with a shorter text that can fit in the widget's rectangle will be displayed correctly. 

When the text is long and AllowScroll is false, the text will be visible, but will be misplaced. The issue is caused by the length of the text because the same field with a shorter text that can fit in the widget's rectangle will be displayed correctly.

WordsProcessing: RtfFormatProvider: Does not export "cellx" correctly when table LayoutType is FixedWidth.

XlsFormatProvider: LeftoverDataException when importing a specific document. 'Initialisation of record 0x55(DefaultColWidthRecord) left 2 bytes remaining still to be read.'

The named ranges are not updated after rows or columns are inserted.

When a row or column is inserted in a worksheet that has cells referred from another worksheet, the formula should be updated so it refers to the same values as before the insertion or removal of cells.

The Indent property of Table is not respected by PdfFormatProvider.