Sam Hocevar

Change does not look good at all. If you don’t use `bbox` in the generated segment, you have no way to ensure the extra point is outside the path.

If anyone’s using this patch, `master` has diverged a lot and this PR no longer merges cleanly, so I merged @jgagnaire’s branch here: https://github.com/loic-sharma/BaGet/compare/master...samhocevar:feature/apiv2?expand=1

Are you using the NuGet package or a more recent version from GitHub?

This will be hard to implement properly, but I’ll try to investigate this. In the meantime, you may be interested in https://github.com/mozilla/twemoji-colr which is a version of twemoji that Emoji.Wpf...

I had a closer look and it was caused by the ligatures not being properly applied. It should work properly with Emoji.Wpf 0.3.3:  There are still some problems with...

Hello! Unfortunately, I have been unable to reproduce the issue so far. Could you maybe answer a few questions? - what is your version of the Segoe UI Emoji font?...

Yes, this is a bug (same as issue #18). It happens because there are two ways to write the Anchor emoji in Unicode: either `U+2693` alone (⚓), or `U+2693 U+FE0F`...

This is a bit puzzling. Do you have an `xmlns:x` entry as well, in order to use `x:Name`?

I’m afraid I was unable to reproduce the problem. Could you maybe share your project, or attach a minimal repro case? Thanks in advance!

Thanks for the reproduction code! I could find the problem.