Date: prev next · Thread: first prev next last
2016 Archives by date, by thread · List index


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’t you go for the tender? I can’t think of 
anyone I’d more highly recommend than yourself, and I’m reasonably certain you have some good ideas 
around how to fix the SalLayout mess... certainly you have the technical expertise and experience 
to tackle this. 

Just a suggestion :-)

Chris

On 1 Feb 2016, at 9:35 PM, Khaled Hosny <khaledhosny@eglug.org> wrote:

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 of this AFM stuff during text layout as far as I
can know and I don’t see how it can even be reused for such a task.

1. 
https://blog.documentfoundation.org/blog/2015/12/16/tender-for-cross-platform-fontshaping-stubs-for-layout-tests-201512-05/

Regards,
Khaled
_______________________________________________
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice


Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.