Guillaume Ayoub

Thanks a lot for this very useful answer. The problem you have is caused by a bitmap font. Since version 56, WeasyPrint supports bitmap fonts, that’s why the rendering was...

@lar-ry Is there a way we could help you solving this problem?

> I had to continue using version 55 because this font was required. OK, I understand. The bug is actually caused by another font, a bitmap font installed on your...

> I want to try, what do I need to do? Thank you! Here’s what you can do: - Install WeasyPrint 56.1 - Open `C:\Users\larry\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.10_qbz5n2kfra8p0\LocalCache\local-packages\Python310\site-packages\weasyprint\pdf\fonts.py` - Add `open('C:\\Users\\larry\\font-' + font.hash,...

Thank you very much for your time, I can now reproduce your bug! I’ll come back as soon as I find a way to fix it.

The bug should now be fixed. The 宋体 font includes both bitmap characters and vector characters. We should use the vector variant (see #1736), removing the bug. Moreover, the crash...

> Has anyone tested Lasem? It's exactly what we need, thanks for the link. So sad it's a C library that's not widely included in Windows GTK+ bundles or in...

> I'm currently working on a Markdown extension that uses the offline rendering of KaTeX. That's a good idea! Thanks for sharing. > Despite these warnings, the rendering is still...

> This is to inform the community that [**math2svg**](https://github.com/pandoc/lua-filters/tree/master/math2svg) is now available as an officially Pandoc adopted Lua filter: Good to know, thanks a lot for sharing this information!

> It's because of `colspan="65534"` Then I suppose it’s not struck, it’s just extremely slow :smile:. There’s an optimization waiting to be found.