This behavior appeared after upgrading from LL29 to LL30. Installing the newest Service Pack did not solve the incorrect character spacings. Can you help me?
Regards,
Michael
crauchfuss
(combit Support - Christian Rauchfuß)
2
Hi Michael,
We’ll take a closer look at the behavior. However, it only seems to occur in printerless mode. Can you confirm this? If so - how is it displayed when the printerless mode will be deactivated for test purposes?
Is there any news on this topic? We currently have switched off printerless mode in LL30. But as already mentioned, this is not a permanent solution for our customers.
Regards,
Michael
crauchfuss
(combit Support - Christian Rauchfuß)
7
Hi Michael,
We are still in contact with our development department. The analysis of the behavior is taking longer than usual. We apologize for this and thank you for your patience.
Regards
Chris
1 Like
crauchfuss
(combit Support - Christian Rauchfuß)
8
Hi Michael,
we’ve got some response from our development, which we want to share with you:
As far as we can tell, the behavior is triggered in Microsoft’s RTF Control. We have tried various things to work around the behavior (e.g. individually influencing the character spacing or different RTF versions), but without success. The RTF Control does not take this into account. It seems to be related to the resolution of the screen DC or the graphics card. Only with a 4K display was the output as expected. The behavior is also the same in the older version LL29. So in our point of view there only two things we can provide: