> Oh, I slipped to mention a change from my patch in previous post and
> committed one. In previous post in this list, I added a public
> function FT_List_GetNodeAt(). But, now I moved it into ttgload.c,
> as a private function. It is just because once we publish some
> function, we cannot
> I updated the simplest fix in my hand. I was going to commit it to
> head of git repository, but savannah is in some network trouble.
> Attached is the patch, but if anybody wants, I will make a "make
> dist" tarball which is ready to "./configure && make". please let
> me know.
Savannah
Dear Werner,
Oh, I slipped to mention a change from my patch in previous
post and committed one. In previous post in this list, I added
a public function FT_List_GetNodeAt(). But, now I moved it into
ttgload.c, as a private function. It is just because once we
publish some function, we cannot
Dear Werner,
Just I've committed the simpler patch.
Reading your comment carefully, "might not be working with the
platform whose default pointer is less than 32-bit" was already
commented :-).
Maybe just 16-bit compiler would not be sufficient, the compilers
supporting Intel tiny/small/medium
Dear Khaled,
Thank you for providing another example. It seems that
oriya.ttf is really including a recursive reference
(gid=8 refers gid=64 & gid=8).
I updated the simplest fix in my hand. I was going to
commit it to head of git repository, but savannah is
in some network trouble. Attached is
On Tue, May 10, 2016 at 08:32:48PM +0900, suzuki toshiya wrote:
> Dear Werner,
>
> > Should I consider overwriting (and extend if required)
> > storategy, to minimize the memory management?
>
> If we can assume the recurse_count in load_truetype_glyph()
> is always incrementally changed, it is
On Tue, May 10, 2016 at 11:19:04AM +0900, suzuki toshiya wrote:
> I guess the composite glyphs referring same component twice or more
> can cause this warning.
Yes, this what I reached to as well.
> I will try to fix it...
Thanks!
___
Freetype
Dear Werner,
The naming convention for the types, variables and functions
need further improvement (sorry for my poor English), and some
compiler warnings should be fixed, but anyway I've drafted
a proof of concept. I confirmed it does not complain DejaVu
but detects the recursive reference in
> It seems that the changeset 758d55e522eb426dad2f15adc1d945f7896d7b29
> (between 2.6.1 and 2.6.2) is the point that FT2 starts the complain
> against DejaVu. The changset was introduced to detected looped
> reference. [...]
Thanks for your analysis. It seems that the test to protect against
Hi,
It seems that the changeset 758d55e522eb426dad2f15adc1d945f7896d7b29
(between 2.6.1 and 2.6.2) is the point that FT2 starts the complain
against DejaVu. The changset was introduced to detected looped reference.
Checking TTX disassmbler output, DejaVu font has no looped reference
for U+033F.
10 matches
Mail list logo
