@AT1
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): CELLSNET-55715
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.
@AT1
Hi,
Your issue( CELLSNET-55715) has been resolved and the fixed functionality will be released with version 24.6.
Here is the resulting file generated using the latest function: CELLSNET-55715.pdf (23.1 KB)
The issues you have found earlier (filed as CELLSNET-55715) have been fixed in this update. This message was posted using Bugs notification tool by johnson.shi
I have just found out that it does not work with some characters, e.g. “」” “ー”. They don’t come at the beginning of the line when creating PDF from Excel.
Also, IsHangingPunctuation = false; does not work at all.
foreach (TextParagraph p in textbox.TextBody.TextParagraphs)
{
p.Font.Name = "MS Gothic";
p.TextOptions.LanguageCode = CountryCode.Japan;
p.IsEastAsianLineBreak = true;
p.IsHangingPunctuation = false;
}
@AT1
We can reproduce the issue by testing it on the latest version v24.6 using the following sample code. Found that TextParagraph.IsHangingPunctuation Attribute does not work when converting files to PDF. Please refer to the attachment. out_net.zip (43.6 KB)
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): CELLSNET-56104
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.
Thank you for your feedback and the suggested text to demonstrate the incorrect characters positions. We have logged it with your existing ticket (“CELLSNET-56104”) in our database. We will evaluate your issue soon. Once we have an update or figure it out, we will let you know here.
@AT1
After carefully studying the way Excel handles punctuation, we optimized the handling of punctuation to make it more suitable for Excel’s processing mode.
The fixed functionality will be released with version 24.7.
The issues you have found earlier (filed as CELLSNET-56104) have been fixed in this update. This message was posted using Bugs notification tool by johnson.shi
I have tested version 24.7. I still find some characters in wrong positions.
Would you please list up here all the characters that are handled in version 24.7?
The following is MS Word Asian Typography options. I would like to see the difference compared with them.
Cannot start line
!%),.:;?]}¢°’”‰′″℃、。々〉》」』】〕゛゜ゝゞ・ヽヾ!%),.:;?]}。」、・゙゚¢
Thanks for your reply.
I have just created a text that contains some characters that our clients use quite often. Apparently it does not cover all the characters but this is the best I can do for you now.
Also an outcome of Excel is attached so that you can see the differences.
We have tested and found that the issue still persists with certain characters in the text strings you provided. Some characters are being rendered in the wrong positions within the text box during the Excel to PDF conversion.
We will thoroughly evaluate the issue from all aspects. 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): CELLSNET-56207
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.
@AT1
Your issue(CELLSNET-56207) has been resolved and the fixed functionality will be released with version 24.8.
The following is the result file generated using the sample code: CELLSNET-56207.pdf (28.7 KB)
Thank you very much for the fix. I had a look at the result file and found that the following line is the same as before. Have you decided not to handle this for some reasons?
@AT1
The “ー” in this line was missed in a previous fix. This has been fixed. While we have fixed most common punctuation, we may not be able to cover all punctuation. If you find punctuation that needs to be fixed, please contact us. CELLSNET-56207-fix.pdf (28.7 KB)
The issues you have found earlier (filed as CELLSNET-56207) have been fixed in this update. This message was posted using Bugs notification tool by johnson.shi