Hello Team,
We are facing the Character Misalignment issue in Excel when converting into PDF.
We attatched the source file for your reference. Kindly try to fix the issue ASAP.
Excel_Issue_OriginalFile.zip (110.7 KB)
Issue_Addon.zip (257.7 KB)
Hello,
Thank you for providing the source Excel files and the sample output for our review.
We have successfully reproduced the issue you described. During the Excel to PDF conversion process, we observed significant character rendering failures where text in the headers, tables, and diagram labels is replaced by empty square boxes (tofu). While the document layout and graphical elements remain intact, the text content is currently unreadable due to these missing glyphs.
Our initial analysis suggests this is caused by a font substitution or character encoding failure during the rendering process. We are now investigating the root cause to ensure all characters are correctly mapped to their corresponding glyphs in the output PDF.
We have opened the following new ticket(s) in our internal issue tracking system and will deliver their fixes according to the terms mentioned in Free Support Policies.
Issue ID(s): CELLSJAVA-46689
You can obtain Paid Support Services if you need support on a priority basis, along with the direct access to our Paid Support management team.
1 Like
@Manish7320
This issue has been fixed in the latest version. Here are the results generated using version 26.3.
Excel_Issue_OriginalFile-26.3.0_java.pdf (280.8 KB)
Please use the latest version to perform the check. If you encounter any other issues, please contact us.
1 Like
Hello Team,
Thanks for releasing version 26.3.
After updating the version in our pom.xml file and deploying, we are still not getting the expected result. We have shared the pom.xml file we are using
pom.xml_file_aspose.zip (1.3 KB)
kindly support us to fix this issue ASAP
@Manish7320
We will conduct a further investigation based on the attachments you have provided and will notify you immediately of any developments.
Thank you for your feedback. We are glad to hear that the initial fix in the latest version has been helpful for your project.
Our team is currently reviewing the additional details you provided to ensure all character alignment nuances are fully resolved. We will keep you updated on the progress of this investigation and provide a follow-up as soon as more information becomes available.
@Manish7320
pom.xml
<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
<modelVersion>4.0.0</modelVersion>
<groupId>com.example</groupId>
<artifactId>pom-test</artifactId>
<version>0.0.1-SNAPSHOT</version>
<!-- Java -->
<properties>
<maven.compiler.source>1.8</maven.compiler.source>
<maven.compiler.target>1.8</maven.compiler.target>
</properties>
<!-- Aspose -->
<repositories>
<repository>
<id>AsposeJavaAPI</id>
<name>Aspose Java API</name>
<url>https://repository.aspose.com/repo/</url>
</repository>
</repositories>
<dependencies>
<dependency>
<groupId>com.aspose</groupId>
<artifactId>aspose-cells</artifactId>
<version>26.3</version>
</dependency>
</dependencies>
</project>
Test Code:
Workbook book = new Workbook("Excel_Issue_OriginalFile.xlsx");
book.save("Excel_Issue_OriginalFile_pom_java.pdf", SaveFormat.PDF);
After reviewing the attachments you provided and removing the content unrelated to this issue, the actual generated results still appear normal. Please proceed by following the pom.xml configuration I have outlined to see if you can reproduce the problem.
Hello @duojie.yang,
Thank you for your support.
We tried the steps you provided, but the changes are still not reflected after deployment. Kindly help us resolve this issue. For your reference, we have attached the screenshot along with the POM files used in our application.
image.png (25.6 KB)
pom.xml_Files.zip (3.6 KB)
Thank you for the update and for providing the screenshot and POM files for our review. We appreciate your patience as we continue to look into this matter.
I have received the additional details you shared regarding the persistent misalignment in version 26.3. I am passing this information directly to our development team to ensure they can identify why the fix is not reflecting in your specific environment.
We will conduct a deeper analysis based on the configuration files you provided. As soon as we have further insights or a revised resolution, we will update you immediately through this thread.
1 Like
@Manish7320
If you still encounter problems using the provided simple pom.xml file, please check if the fonts “MS Gothic” and “Meiryo UI” exist and if they are available on the machine you are running the program on.
Hello @duojie.yang
Yes, the both fonts “MS Gothic” and “Meiryo UI” exist and running in our machine.
Thank you for confirming that MS Gothic and Meiryo UI are correctly installed on your system. This information is very helpful for our ongoing investigation.
Since the issue persists on your end despite the update, we are looking into why the rendering engine is not achieving the same results in your environment as it did in our initial tests. We are currently evaluating the font substitution logic and environment-specific rendering settings to identify the root cause.
We will keep you updated on our progress as we continue to investigate this behavior. Thank you for your patience.
@Manish7320
Could you please provide the problematic PDF file you generated? This will help us further investigate the issue.
@Manish7320
Thank you for providing updated information for our investigation.
We will conduct a more in-depth analysis based on the documents you provided. We will notify you immediately via this post once there are any new findings or solutions.
1 Like
@Manish7320
An investigation revealed that this issue has been fixed in the latest version.
You may be using an older version, such as 24.7.
Please update to the latest version to test if the issue is resolved.
You can confirm the version used to generate the PDF file by viewing the generated PDF file: Open the PDF file with Adobe: File → Properties
Or you can directly add print codes:
String version = com.aspose.cells.CellsHelper.getVersion();
System.out.println("Cells Version : " + version);
Hello @duojie.yang ,
We understand that the current version in our system is 24.7. However, when we attempted to update the version to 26.3 in the pom.xml file and redeployed, the changes did not reflect in our system. Our concern is to understand why version 26.3 is not being applied, and for this purpose, we have already shared the related documentation.
@Manish7320
After reviewing your pom.xml file, I noticed that not all <dependency> entries related to aspose-cells specify a version number.
You might try modifying the file and then running a test to see if this resolves the issue. I performed my testing within the Eclipse environment; typically, after updating version numbers, the project automatically updates and rebuilds itself.
At this point, you should be able to see an entry similar to “aspose-cells-xx.x.jar” within the “Maven Dependencies” directory of your project.
Additionally, you could try printing out the current version number before executing any code related to aspose-cells.
Given the complexity of your pom.xml file structure, I recommend considering the creation of a minimalist project solely for testing purposes. For specific instructions on how to do this, please refer to my previous response(Recommended: This aids in troubleshooting).
Hello @duojie.yang
image.png (25.5 KB)
"As per your suggestion, we generated a log and can confirm that the updated version is reflected there as well. However, we are unsure of the next steps to proceed.