Re: [ft-devel] [Rendering Regressions] Outlines vs. Bitmaps

Thanks for the quick reply and clarification! :) I was thinking the same: having the option to force the inspection of bitmaps in addition to checking outlines (which happens wherever possible). On 18/03/2018 15:18:14, Werner LEMBERG wrote: > as suggested by Werner, I currently

Re: [ft-devel] [Rendering Regressions] Outlines vs. Bitmaps

> as suggested by Werner, I currently look into using outlines as a > (considerably faster) means to detect rendering regressions. I do > understand that the outlines of glyphs should definitely be checked. > However, I wonder if it is enough to guarantee "no rendering > regressions" by just

Re: [ft-devel] Contribution to freetype

> Maybe Werner already knows, it could be regarded as one of the > ancestors of ISO/IEC 14496-28: > https://blogs.adobe.com/CCJKType/2012/04/cfr.html Thanks for the remainder! Werner ___ Freetype-devel mailing list Freetype-devel@nongnu.org

Re: [ft-devel] CMake patches from Microsoft's vcpkg project

So I've been trying to make the CMakeLists.txt file a bit neater. CMake is sadly not an elegant build system... Here's what I have so far: https://github.com/madig/freetype2/blob/modernize-cmake-build/CMakeLists.txt I cribbed the SO version thing from

[ft-devel] [Rendering Regressions] Outlines vs. Bitmaps

Hi, as suggested by Werner, I currently look into using outlines as a (considerably faster) means to detect rendering regressions. I do understand that the outlines of glyphs should definitely be checked. However, I wonder if it is enough to guarantee "no rendering regressions" by just

Re: [ft-devel] Contribution to freetype

Maybe Werner already knows, it could be regarded as one of the ancestors of ISO/IEC 14496-28: https://blogs.adobe.com/CCJKType/2012/04/cfr.html Regards, mpsuzuki Khaled Hosny wrote: > On Sun, Mar 18, 2018 at 12:13:03PM +0100, Werner LEMBERG wrote: >>> In the namespace definition of XML, such

Re: [ft-devel] Contribution to freetype

> See the “Composite Fonts” section in: > https://msdn.microsoft.com/en-us/library/system.windows.media.fontfamily(v=vs.110).aspx Thanks a lot! Werner ___ Freetype-devel mailing list Freetype-devel@nongnu.org

Re: [ft-devel] Contribution to freetype

On Sun, Mar 18, 2018 at 12:13:03PM +0100, Werner LEMBERG wrote: > > In the namespace definition of XML, such strings looking like as URL > > are required as the identifiers, and often unreachable URL causing > > 404 error. But it is not broken in the conformance of XML spec. > > OK, thanks. I

Re: [ft-devel] Contribution to freetype

> In the namespace definition of XML, such strings looking like as URL > are required as the identifiers, and often unreachable URL causing > 404 error. But it is not broken in the conformance of XML spec. OK, thanks. I was just curious and tried to get more information :-) Werner

Re: [ft-devel] Contribution to freetype

Hi, slightly off-topic discussion... > Maybe I'm mistaken. Note that the `xmlns' link in those XML files, > > http://schemas.microsoft.com/winfx/2006/xaml/composite-font > > is broken. However, it contains the string `winfx', which is (or In the namespace definition of XML, such strings

Re: [ft-devel] Contribution to freetype

>> If I understand you correctly, an application that uses DirectWrite >> doesn't need `.compositeFont' files at all, right? What happens >> with applications that don't use DirectWrite? > > No, I don't think they have any value for DirectWrite. If > application is not using DirectWrite the

Re: [ft-devel] Contribution to freetype

On 3/18/2018 12:05 PM, Werner LEMBERG wrote: > >> Higher level would make use of ranges/language mapping for fallback. >> DirectWrite fallback is modeled very close if not identical to how >> this data is defined in .compositefont xml format. When using >> DirectWrite layout API, application can

Re: [ft-devel] Contribution to freetype

> Higher level would make use of ranges/language mapping for fallback. > DirectWrite fallback is modeled very close if not identical to how > this data is defined in .compositefont xml format. When using > DirectWrite layout API, application can rely on implicit fonts being > selected for

Re: [ft-devel] Contribution to freetype

On 3/18/2018 11:17 AM, Werner LEMBERG wrote: > > Adding support to FreeType would immediately enable *all* applications > to handle them without changes. What should a higher level do in your > opinion? Higher level would make use of ranges/language mapping for fallback. DirectWrite fallback is

Re: [ft-devel] Contribution to freetype

>> Technically, they are not fonts, but practically they are. It's >> not much different to, say, a CFF that consists of a bunch of >> subfonts. > > Okay, I guess I'll have to wait and see when this is implemented. > My understanding is that it's a way to define mapping for existing > fonts, so

Re: [ft-devel] Contribution to freetype

On 3/18/2018 10:25 AM, Werner LEMBERG wrote: > >>> The difficulty is not adding support for the VF format itself but >>> to find a good API that is generic enough for other purposes, too. >>> I'm thinking of handling files like Microsoft's >>> `GlobalSerif.CompositeFont'. Apple and Android

Re: [ft-devel] Contribution to freetype

>> The difficulty is not adding support for the VF format itself but >> to find a good API that is generic enough for other purposes, too. >> I'm thinking of handling files like Microsoft's >> `GlobalSerif.CompositeFont'. Apple and Android provide similar >> concepts. It's probably not the job

Re: [ft-devel] Contribution to freetype

On 3/18/2018 6:19 AM, Werner LEMBERG wrote: > > The difficulty is not adding support for the VF format itself but to > find a good API that is generic enough for other purposes, too. I'm > thinking of handling files like Microsoft's > `GlobalSerif.CompositeFont'. Apple and Android provide

Re: [ft-devel] Contribution to freetype

> There's nothing to implement during GSoC! Composite outline font > support is something completely different. > > > OK! Thank You Regards Parth ___ Freetype-devel mailing list Freetype-devel@nongnu.org

Re: [ft-devel] Contribution to freetype

>> >I'm thinking of handling files like Microsoft's >> >`GlobalSerif.CompositeFont'. Apple and Android provide similar >> >concepts. >> > >> >It's probably not the job of FreeType to digest such composite >> >fonts by itself (you'll need an external XML interpreter); >> >however, it would be very