On 02.02.2016 11:58, Khaled Hosny wrote:
> Personally I’d do a mixture of the two, a 7th (8th? I think we have 6 or
> 7 SalLayout implementations already) SalLayout that uses HarfBuzz
> (reusing the existing HarfBuzz integration code as much as possible)
> then gradually switch existing platforms t
I’m just trying to understand what is this about for now.
Regards,
Khaled
On Tue, Feb 02, 2016 at 07:18:28AM +1100, Chris Sherlock wrote:
> This does seem a bit odd… unless we want to make AFM parsing cross-platform?
>
> The only thing that I’m aware implements AFM parsing is
> PrintFontManager,
On Tue, Feb 02, 2016 at 10:15:07AM +0100, Miklos Vajna wrote:
> Hi,
>
> I think the problem to solve is that we have different layout on Linux,
> Windows and OS X, which means it's next to impossible to write unit
> tests that assert the text is laid out correctly, since there can be
> small diffe
Would it be helpful to look at the way that OutputDevice handles laying out
text?
When I was looking at this code early last year I found that I had to try to
understand what OutputDevice did before I could come even *close* to
understanding what SalLayout was attempting.
For instance, the DX
Hi,
I think the problem to solve is that we have different layout on Linux,
Windows and OS X, which means it's next to impossible to write unit
tests that assert the text is laid out correctly, since there can be
small differences today. The hope is that this is the root cause of e.g.
the chart te
This does seem a bit odd… unless we want to make AFM parsing cross-platform?
The only thing that I’m aware implements AFM parsing is PrintFontManager, which
is only used by Unix-based platforms.
Could we get some clarification around this?
Oh, and also - Khaled, once this is clarified why don’
I just came across this tender [1] and it is not quite clear to me what
is it about. Am I right in thinking this is about having a shared
cross-platform implementation of VCL text layout API (the dreaded
SalLayout et all)? If so I don’t understand what AFM stuff is doing here
since we don’t use any
