Do you understand the Rx calculations?
Not without a lot of time to introduce myself to the code :-)
They are wrong if integer overflows, aren't they?
Yes, it seems so, but up to now we haven't had a bug report.
So there will be artifacts, possibly very small ones, when
SMulDiv_NoRound
On Wed, Jun 13, 2012 at 9:22 AM, Werner LEMBERG w...@gnu.org wrote:
It's probably a good idea to fix Rx also. What about this:
old:
Rx = ( ras.precision * Dx ) % Dy;
new:
Rx = ( ( ras.precision % Dy ) * ( Dx % Dy ) ) % Dy;
Let's not rush with this and just say that your fix
Let's not rush with this and just say that your fix is incomplete
for now.
OK.
I have a completely new ftgrays implementation without '%' that
works quite nicely.
Aah, great to hear!
Werner
___
Freetype-devel mailing list
Alexei Podtelezhnikov-2 wrote:
On Tue, Jun 5, 2012 at 7:20 AM, jola hans-jochen@lhsystems.com
wrote:
Alexei Podtelezhnikov-2 wrote:
The only potential change in question is this:
The only potential change in question is this:
http://git.savannah.gnu.org/cgit/freetype/freetype2.git/commit/?id=7baeeafcec7fd2267191937e14c1f753424beb89
Your guess was not wrong! This morning I repeated the tests, I had
conducted yesterday. I had been in a hurry and obviously mixed
On Wed, Jun 6, 2012 at 7:25 AM, Werner LEMBERG w...@gnu.org wrote:
The only potential change in question is this:
http://git.savannah.gnu.org/cgit/freetype/freetype2.git/commit/?id=7baeeafcec7fd2267191937e14c1f753424beb89
Your guess was not wrong! This morning I repeated the tests, I had
On Mon, Jun 4, 2012 at 4:38 AM, jola hans-jochen@lhsystems.com wrote:
the bug was obviously introduced with the transition from 2.3.12 (working)
to 2.4.0 (showing the bug). HTH.
The only potential change in question is this:
Alexei Podtelezhnikov-2 wrote:
The only potential change in question is this:
http://git.savannah.gnu.org/cgit/freetype/freetype2.git/commit/?id=7baeeafcec7fd2267191937e14c1f753424beb89
It was supposed to fix bug http://savannah.nongnu.org/bugs/?29335
Do you mind reverting this change
On Tue, Jun 5, 2012 at 7:20 AM, jola hans-jochen@lhsystems.com wrote:
Alexei Podtelezhnikov-2 wrote:
The only potential change in question is this:
http://git.savannah.gnu.org/cgit/freetype/freetype2.git/commit/?id=7baeeafcec7fd2267191937e14c1f753424beb89
It was supposed to fix bug
Hi Alexei,
the bug was obviously introduced with the transition from 2.3.12 (working)
to 2.4.0 (showing the bug). HTH.
Alexei Podtelezhnikov-2 wrote:
This is clearly a bug in BW rasterizer. Can you help to git bisect it?
You know two versions with and without a bug.
On Thu, May 31, 2012
This is clearly a bug in BW rasterizer. Can you help to git bisect it?
You know two versions with and without a bug.
On Thu, May 31, 2012 at 10:38 AM, jola hans-jochen@lhsystems.com wrote:
To make use of new API (kerning etc.) I upgraded from FT 2.1.10 to FT 2.4.8
and then 2.4.9. When
To make use of new API (kerning etc.) I upgraded from FT 2.1.10 to FT 2.4.8
and then 2.4.9. When rendering some PostScript Type 1 fonts with these
versions some artefacts show up. As an example ITC Kabel was rendered at
font sizes 106, 212, 318, an 423 pixels (files K001013T.PFB and
K001013T.PFM
12 matches
Mail list logo
