Infro,
i think you were right. I printed the following info.
dpi = 200 pointsize = 16 ROWS = 35, width = 28, pitch = 28 Stride = 28
num_grays = 256
dpi = 300 pointsize = 16 ROWS = 52, width = 43, pitch = 43 Stride =
44num_grays = 256
dpi = 300 pointsize = 12 ROWS = 40, width = 32, pitch = 32 Stride = 32
num_grays = 256
as we can see for second one width and stride are different.
How can this be tackled ?
Thanks
Varun
On Fri, Jun 11, 2010 at 11:31 AM, varun shrivastava <[email protected]>wrote:
> i didn't understood fully what you said,
>
> i am creating the cairo surface of same width and heigth as
>
> int stride = cairo_format_stride_for_width(CAIRO_FORMAT_A8,
> bitmap->width);
> cairo_surface_t *surface =
> cairo_image_surface_create_for_data(bitmap->buffer, CAIRO_FORMAT_A8,
>
> bitmap->width, bitmap->rows, stride);
> cairo_surface_write_to_png(surface, "A.png");
>
>
> Thanks
> Varun
>
>
> On Fri, Jun 11, 2010 at 11:17 AM, Infro <[email protected]> wrote:
>
>> If I had to take a guess, I would say that the 16pt @ 300dpi was
>> copied/drawn incorrectly, specifically, that the source data had a smaller
>> width than the destination, and that created the "slanted" effect.
>>
>> As from my sample, the 12 starts in the top right corner and proceeds to
>> the bottom left corner, which is my guess.
>> ex.
>> (source is 1-8, desitnation is 1-0)
>> 1234567812
>> 3456781234
>> 5678123456
>> 6712345678
>> 1234567812
>>
>
>
_______________________________________________
Freetype mailing list
[email protected]
http://lists.nongnu.org/mailman/listinfo/freetype
