-
Notifications
You must be signed in to change notification settings - Fork 29
docs: add kb on spire office truncated text issue #1847
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
petar-i-todorov
wants to merge
2
commits into
master
Choose a base branch
from
petodoro/spire-office-truncated-text
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,78 @@ | ||
--- | ||
title: Text Truncation in Rendered Reports When Using Spire.Office with Telerik Reporting | ||
description: "Learn how to fix text truncation issues in Telerik Reporting when using the Spire.Office libraries in the same application." | ||
type: troubleshooting | ||
page_title: Fix Text Truncation When Using Spire.Office with Telerik Reporting | ||
slug: text-truncation-spire-office-reporting | ||
tags: reporting, spire, office, text, truncation, stringformat, gdi | ||
res_type: kb | ||
--- | ||
|
||
## Environment | ||
|
||
<table> | ||
<tbody> | ||
<tr> | ||
<td>Product</td> | ||
<td>Progress® Telerik® Reporting</td> | ||
<td>Spire.Office</td> | ||
</tr> | ||
<tr> | ||
<td>Version</td> | ||
<td>19.2.25.1001</td> | ||
<td>8.12.2 or earlier</td> | ||
</tr> | ||
</tbody> | ||
</table> | ||
|
||
## Description | ||
|
||
When using the Telerik Reporting in the same application that processes MS Office documents and PDF files with Spire.Office libraries, the text in the rendered reports gets truncated unexpectedly. | ||
|
||
This issue occurs even when the Spire.Office operations are performed on completely unrelated documents before rendering the Telerik report. | ||
|
||
## Cause | ||
|
||
The issue is caused by Spire.Office modifying the global state of `System.Drawing.StringFormat.GenericTypographic`. After Spire.Office processes documents, the `GenericTypographic` method no longer returns a `StringFormat` object with the expected format flags. | ||
|
||
**Expected StringFormat flags:** | ||
- `StringFormatFlagsLineLimit` | ||
- `StringFormatFlagsNoClip` | ||
- `StringFormatFlagsNoFitBlackBox` | ||
|
||
**Actual StringFormat flags after Spire.Office usage:** | ||
- `StringFormatFlagsLineLimit` | ||
- `StringFormatFlagsNoClip` | ||
- `StringFormatFlagsNoFitBlackBox` | ||
- `MeasureTrailingSpaces` (additional flag) | ||
|
||
The extra `MeasureTrailingSpaces` flag causes incorrect text measurement in Telerik Reporting's GDI wrapper, leading to text truncation in some scenarios. | ||
|
||
## Solution | ||
|
||
To resolve this issue, manually remove the `MeasureTrailingSpaces` flag from the `GenericTypographic` StringFormat after using Spire.Office operations and before rendering Telerik reports: | ||
|
||
````C# | ||
using Telerik.Reporting; | ||
using Telerik.Reporting.Processing; | ||
|
||
// Spire.Office operations | ||
Spire.Doc.Document document = new Spire.Doc.Document(); | ||
var wordDocPath = "./wordtest.docx"; | ||
var pdfFilePath = System.IO.Path.Combine("../../../", "wordtest.pdf"); | ||
|
||
document.LoadFromFile(wordDocPath); | ||
Spire.Doc.ToPdfParameterList toPdf = new Spire.Doc.ToPdfParameterList(); | ||
document.SaveToFile(pdfFilePath, toPdf); | ||
document.Close(); | ||
|
||
// Fix the StringFormat issue caused by Spire.Office | ||
System.Drawing.StringFormat.GenericTypographic.FormatFlags &= ~System.Drawing.StringFormatFlags.MeasureTrailingSpaces; | ||
|
||
// Telerik Reporting operations | ||
// ... | ||
```` | ||
petar-i-todorov marked this conversation as resolved.
Show resolved
Hide resolved
|
||
|
||
## Additional Information | ||
|
||
This issue affects only older versions of Spire.Office that use the GDI+ engine for text rendering. Starting from version `9.2.0`, it does not rely on GDI+. |
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.