I use a sample program to merge cells.
If I save this workbook as Excel file, the
display is correct. But when save as PDF file, it lose some text.
you will see “123456” at the first line, and below is “890”, so where
Both 4.9 and 4.9.1 have this problem.
The program below:
Workbook book = new Workbook();
Worksheet sheet = book.Worksheets;
sheet.Cells.CreateRange(0, 0, 10, 3).Merge();
Cell cell = sheet.Cells[0, 0];
Style sty = cell.GetStyle();
sty.IsTextWrapped = true;
Hi,<?xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" />
Thank you for sharing the template file.
We have found your mentioned issue after an initial test. We will look into it and get back to you soon. Your issue has been registered in our internal issue tracking system with issue id: CELLSNET-17226.
Thank You & Best Regards,
Please try the attached version.
We have figured out your issue now.
Thanks for your help.
My issue was resolved.
But I’ve found another problem that I can’t open the generated PDF file neither using “PDF-XChange PDF Viewer” nor “SumatraPDF”. But I can open it with “Adobe Reader”, “Foxit Reader” and “apvlv”.
This was not exist in version 4.9.1
"PDF-XChange PDF Viewer" is faster than “Adobe Reader”, many of people use this program to view PDF file.
“SumatraPDF” is the fastest.
We tested and used Sumatra PDF1.1 and PdfXCHANGE Viewer , they show the pdf files correctly.
Could you provide your template file(s) here so that we can check your issue soon. Also, please try the latest version of the 3rd party Pdf viewer i.e. PdfXCHANGE 2.0.
I just use the code above(First one in this thread) to generate a sample PDF file.
I use Sumatra PDF1.1 and PDF-XChange PDF Viewer 2.0
Update: I can open it with Sumatra PDF1.1 and can view this file now.
May be my computer has some problems.
Thanks for your quick reply.
PS: When do you release new versions including this improvement?
Hopefully, we can release our next official version(that will include your desired functionality) before the end of this month. By the way, you may use the fix as long as you want, it will behave like an official release and will work fine with your license, no issue at all.
Please ignore my previously attached version/fix v184.108.40.206 as
there was an internal bug in it (we found).
Please use the new fix
v220.127.116.11 (attached) in which we have fixed the bug.
sorry for any inconvenience.