Same with the arabic test around minute 26 ص و
-
-
Actually when the font size was increased to 40 (at 26:22) the problem is largely gone. When it's scaled back to 17 the clipping issues appears again.
2 replies 0 retweets 1 like -
-
Replying to @daniel_carvalho @wisam910
So first-pass look at this, it just seems like DirectWrite reports sizes 1 pixel off. Maybe I am missing something, but that's what it seems like? This is why it disappears at 40 - because 1 pixel doesn't make a difference.
1 reply 0 retweets 0 likes -
I will go through my code though and try to ensure that it isn't me doing something wrong first. But either way the fix will be trivial (either fix wherever I'm accidentally subtracting 1, or add 1 to the DirectWrite size reporting).
1 reply 0 retweets 0 likes -
OK so all is well - it's just that the size was reported in float, and obviously refterm is using integer pixel coordinates. So rounding instead of truncating was all that was necessary!
1 reply 0 retweets 5 likes -
Thanks for spotting this, I will check in the fix.
2 replies 0 retweets 1 like -
The fix made it into the V2 release as well, so if you'd like to see the fixed version, you can run it:https://github.com/cmuratori/refterm/releases/tag/v2 …
1 reply 0 retweets 1 like -
-
I like the way you support Hindi in refterm, because Windows has some horrible support for Hindi too, I can tell as I am a native speaker of the language and had nightmares while using it on windows.
1 reply 0 retweets 2 likes
Awesome! Also, if you have any Hindi text that does not display properly in refterm, please feel free to file an issue on the GitHub.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.