On 07/01/2019 20:07, Alexei Podtelezhnikov wrote:
>>> I am testing with ftview and ftstring: statically linked - no
>>> problem. dynamically linked - yes problem.
>
> "make devel" defines T1_CONFIG_OPTION_OLD_ENGINE, which calls
> t1_decoder_parse_charstrings and it works.
> otherwise,
> > I am testing with ftview and ftstring: statically linked - no
> > problem. dynamically linked - yes problem.
"make devel" defines T1_CONFIG_OPTION_OLD_ENGINE, which calls
t1_decoder_parse_charstrings and it works.
otherwise, cf2_decoder_parse_charstrings is called and it does not
work. They
>> I'm still seeing the same problem (freetype from git, as of a
>> couple minutes ago; testing with my Xpdf code).
>
> I am testing with ftview and ftstring: statically linked - no
> problem. dynamically linked - yes problem.
>
> How is this even possible?
`strace' is probably your
> > > It appears that this got fixed between 2.9.1 and current head, which
> > > parses and renders "m" just fine. I have no idea what fixed it.
> >
> > master still has this problem for me.
> >
> > Can some body else please confirm if the font renders fine for them?
>
> I'm still seeing the same
On Thu, 03 Jan 2019 22:48:35 +0100
Albert Astals Cid wrote:
> El dijous, 3 de gener de 2019, a les 3:09:38 CET, Alexei
> Podtelezhnikov va escriure:
> > > > Adobe renders this "m".
> > >
> > > Thanks to all for checking.
> > >
> > > Alexei, can you take care of this?
> >
> > It appears that
El dijous, 3 de gener de 2019, a les 3:09:38 CET, Alexei Podtelezhnikov va
escriure:
> > > Adobe renders this "m".
> >
> > Thanks to all for checking.
> >
> > Alexei, can you take care of this?
>
> It appears that this got fixed between 2.9.1 and current head, which
> parses and renders "m" just
> > Adobe renders this "m".
>
> Thanks to all for checking.
>
> Alexei, can you take care of this?
It appears that this got fixed between 2.9.1 and current head, which
parses and renders "m" just fine. I have no idea what fixed it.
___
Freetype-devel
>> > By the way, does Adobe render this file properly? That would be a
>> > strong argument to support it too.
>>
>> Indeed. Let's make this the decisive argument.
>
> Adobe renders this "m".
Thanks to all for checking.
Alexei, can you take care of this? Right now I'm overwhelmed with
family
On Wed, 2 Jan 2019 11:20:15 -0500
Alexei Podtelezhnikov wrote:
> > > By the way, does Adobe render this file properly? That would be a
> > > strong argument to support it too.
> >
> > Indeed. Let's make this the decisive argument.
>
> Adobe renders this "m".
I can confirm that multiple
> > By the way, does Adobe render this file properly? That would be a
> > strong argument to support it too.
>
> Indeed. Let's make this the decisive argument.
Adobe renders this "m".
I wonder if this is actually a parser error when it produces a nonsense contour.
Contour 1
92 x: 456
>> Ok, so the font is not correctly formed, but it seems that freetype
>> can still render it "just fine".
>
> [...]
>
> By the way, does Adobe render this file properly? That would be a
> strong argument to support it too.
Indeed. Let's make this the decisive argument.
Werner
> > > I obviously have no idea how important the check for FT_CURVE_TAG_CUBIC
> > > is, just that for this particular font removing it makes it work.
> >
> > Below is the dump of the m outline data. The contour 1 contains a run
> > of four control points FT_CURVE_TAG_CUBIC (0x2), which is not how
El dilluns, 31 de desembre de 2018, a les 14:44:10 CET, Alexei Podtelezhnikov
va escriure:
> > I obviously have no idea how important the check for FT_CURVE_TAG_CUBIC is,
> > just that for this particular font removing it makes it work.
>
> Below is the dump of the m outline data. The contour 1
> I obviously have no idea how important the check for FT_CURVE_TAG_CUBIC is,
> just that for this particular font removing it makes it work.
Below is the dump of the m outline data. The contour 1 contains a run
of four control points FT_CURVE_TAG_CUBIC (0x2), which is not how a
Bezier curve
Hi, if try to render this pdf file
https://gitlab.freedesktop.org/poppler/poppler/uploads/0d2f71bf676d3136f8b4ffec534163c0/test.pdf
with poppler you'll see it's missing an m
https://i.imgur.com/EX6PUym.png
I can "fix" it with this patch
diff --git a/src/base/ftoutln.c
15 matches
Mail list logo
