> My librsvg2 is current - 2.56.0 :-(.
>
> What svg font does it work well with? I think I should do Valgrind
> on a font that works, to see what is leaking.
I use version 2.52.9 as installed by default on my OpenSUSE GNU/Linux
box. This works fine for simple cases like
`ArefRuqaaInk-Regular.tt
> context:
> https://summerofcode.withgoogle.com/proposals/details/6CaOVRhz
I can't access this. I get an 'Access denied' error.
> I am assuming that the list of character adjustments is small enough
> to store in-memory without issues. This changes completely if a
> file was needed instead.
My librsvg2 is current - 2.56.0 :-(.
Found "-k czq 500" is okay, but "-k czq 400" fails 5 times on out of memory,
and leaks in cairo_recording_surface_create from FT_Glyph_To_Bitmap, according
to valgrind. "-k czq 380" is just not runnable (and valgrind warns of "set
address range perms: large
Hin-Tak,
SVG rendering is handled by librsvg. If that buffer does not have correct
dimensions set, you might have all kinds of crashes. Therefore, try updating
that library. You might have a faulty version.
Alexei
One more interesting point - "ftview 500 ..." is okay (showing top 1/3 of
nodef and bits of perhaps one more glyph). Then even doing the arrow key to
advance 1 glyph gives me memory allocation errors.
On Tuesday, 23 May 2023 at 07:31:49 GMT+8, Hin-Tak Leung
wrote:
On Monday, 22 May
Thanks, I got it working
On Sun, May 21, 2023 at 12:49 AM Werner LEMBERG wrote:
>
> > (3) Go to directory `subprojects/freetype2/include/freetype/config`
> > and modify file `ftoption.h`; you need to comment out options
> > `FT_DEBUG_LEVEL_ERROR` and `FT_DEBUG_LEVEL_TRACE`.
>
> Oops! I
context: https://summerofcode.withgoogle.com/proposals/details/6CaOVRhz
I want to share my idea for the database format and get feedback on it.
I am assuming that the list of character adjustments is small enough to
store in-memory without issues. This changes completely if a file was
needed ins
On Monday, 22 May 2023 at 17:43:35 GMT+8, Werner LEMBERG wrote:
> works just fine (`-kZ` switches off SVG rendering). And yes, B/W (or
> rather gray-scale) output is expected since FreeType doesn't support
> 'COLR' v1 rendering.
"-k cz " in combination with -l N does what c and z says, togglin
[Please communicate via the 'freetype-devel' mailing list!]
Hello Ahmet,
> -Moved three fonts and texts that used in harfbuzz
> benchmark. (https://github.com/harfbuzz/harfbuzz/tree/main/perf)
For the time being it is OK to add such large files. However, for
benchmarking FreeType's glyph re
> You guys seem to be talking about something different than what I am
> experiencing? I found that it is "-l 1" (antializing) which is
> consuming a lot of memory then segfault. Any of 0,2-6 are fine, and
> all of them b/w (despite it being a colour font). Git head differs
> from 2.13 only in
10 matches
Mail list logo