-
Notifications
You must be signed in to change notification settings - Fork 85
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Differences in the MSDF generation results... #50
Comments
please send the font ( shardailes.zip) to my email again. |
Sent. Thank you for looking at it. Yes, the A & B are both generated from the same Typo lib. I generate a batch of characters (32-254) using the Typo lib - most of which come out almost identical (as far as the eye can tell) to MSDFGen -- but there are some odd ones (in this case, A + X) that are completely different. I also have issues with some punctuation, and odd artifacts in some glyphs... As far as I can tell, stock windows fonts are fine -- this just may be something to do with the way in which we author our fonts for processing. Thank you |
@hexland , which version of your native msdf exe / what is your command line parameters these are my results from native msdf exe https://drive.google.com/open?id=0By55ijpaDeJ0TzM4bTQ2TEZxSFk (I have a problem about upload (drag-drop) result imgs to the GitHub) |
ping @hexland ;) |
I've encountered some differences in the generation of MSDF bitmaps between this Typography library, and the original C++ MSDFGen implementation from which it is adapted.
With certain fonts (hand made ones, using FontForge) - certain glyphs are producing different MSDF maps - but it is only certain glyphs... the majority appear to be OK.
For example...
LayoutFarm - MSDFGen -
Look pretty much equivalent (apart from the page size, but that's fine)
However, the same code generating glyph:
LayoutFarm - MSDFGen -
Any idea what could be going on?
Font --- shardailes.zip
The text was updated successfully, but these errors were encountered: