-
Notifications
You must be signed in to change notification settings - Fork 17
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
Align::*Right doesn't work quite right? #37
Comments
Thank you for using. I will try your code. Please give me some time. (I crezy busy my main business, so it will takes time 🙇♂️🙇♂️🙇♂️) |
Thanks @takkaO -- in case it's helpful, below is some demo code. And here is the reduced URWGothic-Book.h. Attached is a pic of the output. You can see that the left side of the Align::TopRight section is not even. However the right side of Align::TopLeft section is even. So it would seem that there is a difference when the align is left or right in terms of how it computes the edge of the character. Attached is also a pic of the "1" and "2" digits in fontforge, in case that's useful.
|
Also experiencing this with the stock NotoSans_Bold font. Font size doesn't matter, although it's more difficult to see at small sizes. |
I was using URW Gothic Book. This font, as far as I know, has fixed-width numerals.
When I use Align::TopRight or Align::BottomRight for the numerals, however, the alignment changes when a "1" is the last digit drawn to the screen.
E.g. drawing the string "90" and "91" will cause the 9 to be in a slightly different place. The other combinations (92, 93, 94, etc) all align as expected.
If I use that font in LibreOffice and align right, it works as expected.
Here is the original TTF.
Here is the stripped-down version (out of fontforge) that I'm actually using.
Any ideas? Is this a confusion on my part about what to expect from AlignRight? Maybe it goes by the actual glyph contents, rather than the specified character width?
The text was updated successfully, but these errors were encountered: