Marcin Ziąbek

It seems that this issue is not about QuestPDF itself but SkiaSharp. I suggest looking at the SkiaSharp repository to hopefully find an answer and share it with others 😀

In such environments, you need to host your own font files and load them in the runtime. [Please take a look](https://www.questpdf.com/documentation/patterns-and-practices.html#accessing-custom-fonts)

Thank you for testing. So... it looks like it is really an issue of SkiaSharp and there is not much we can do 😥

@ekjuanrejon That's great! Please do share the solution as it may be valuable for others. We may even put it within the documentation 😁

This is interesting! 😁 `Italic` uses different set of predefined glyphs within the font file. Whereas, `Capitals` are more like a text modification. I need to think more if this...

Hello 😁 I am currently working on the text shaping capability and unicode support. It should be available around version 2022.05. A next version after that will provide improved support...

@UserIsAmitHasan I have added unicode support in the 2022.6 release. Would you like to make a try? 😁

The Unicode text is fully supported via the HarfBuzzSharp library. However, it is possible that the current font does not contain certain glyphs, e.g. emojis. I am considering adding font...

Hello 😁 Unfortunately, you are right. Currently, QuestPDF offers limited support for languages that require more advanced text shaping capability. I am planning to improve this in one of the...

> Will this case also applied to chinese/japanese characters? As far as I understand, Chinese/Japanese characters are not connected with each other and do not need to be shaped. Therefore,...