groege
commented
6 years ago I myself don't have an idea since I only ported the Code to net core, if it's the font resolver, the font itself or anything else I cannot say. Did you try using the original PDF sharp within a Windows Project using the same font? Feel free to let me know if you find anything, I gladly accept push requests, that improve on the code.
On Wed, May 23, 2018 at 3:08 PM, kuhlschrank notifications@github.com wrote:
I think the FontResolver-stuff creates some lining issues for text in paragraphs in table cells.
What I get using your assemblies (VerticalAlignment.Top, then .Bottom, then .Center) - Take a close look on the letter "g":
[image: image] https://user-images.githubusercontent.com/3627872/40426210-c4205d26-5e9a-11e8-9c6e-1cca13feca3a.png
What I get using the same document creation code using original MigraDoc/PdfSharp:
[image: image] https://user-images.githubusercontent.com/3627872/40426282-f335fa1c-5e9a-11e8-9d0a-80e8af26409f.png
Is this an issue I can fix on my side or is there generally some issue with the IFontResolver?
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/groege/PdfSharpCore/issues/17, or mute the thread https://github.com/notifications/unsubscribe-auth/AOoWRtwIITj1GvmmE9hxq94U82yE_Q-Xks5t1V9RgaJpZM4UKaiX .
I think the FontResolver-stuff creates some lining issues for text in paragraphs in table cells.
What I get using your assemblies (VerticalAlignment.Top, then .Bottom, then .Center) - Take a close look on the letter "g":
What I get using the same document creation code using original MigraDoc/PdfSharp (without FontResolver ofc):
Is this an issue I can fix on my side or is there generally some issue with the IFontResolver?