Replies: 2 comments 1 reply
|
I’m afraid I can’t follow the question as currently written. There seem to be several separate issues mixed together, and it’s not clear which output was produced by which code path or what result you expected in each case. Could you please rewrite the question and separate each issue into:
A minimal reproduction for each issue would also help. |
1 reply
|
Actually this is an issue with shaping. I’ll get it fixed asap. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Hi.
While trying to generate paths for emoji glyphs using
IGlyphRenderer, I ran into a few issues.Misaligned
👨👩👧👦With
👨👩👧👦, the path for the person at the back left is generated at a misaligned position.Rendered image
Actual:

Expected(Render by browser):

Steps to Reproduce
An emoji different from the entered text is displayed
🤷🏽♀️and🤷🏽, as well as☀︎and☀️, seem to identical.Since there is almost no difference between
🤷🏽♀️and🤷🏽at the IGlyphRenderer level, I checked their appearance when rendered with SixLabors.ImageSharp.Drawing.It is currently unknown whether the issues where the appropriate glyphs for
🤷🏽♀️and☀︎fail to render are the same issue.Since
🤷🏽♀️and🤷🏽likely have the same path in most fonts, I don't think they can be distinguished in the paths generated by IGlyphRenderer; however, while☀︎should have a Yu Gothic path,☀️appears to generate a path as a Segoe UI Emoji character.Rendered image
🤷🏽♀️and🤷🏽Actual:
Expected(Browser):

☀︎and☀️Actual:
Expected(Browser):

Steps to Reproduce
Environment
Windows 11 Pro 25H2
.NET 10
SixLabors.Fonts v3.1.1
(SixLabors.ImageSharp.Drawing v3.1.0)
SixLabors.ImageSharp v4.1.1)
How can I successfully generate the paths for these emojis?
All reactions