On Fri, Jul 24, 2020 at 4:25 PM Vincent Torri
wrote:
> hello
>
> On Windows, there is no mmap, but there is shared memory support, with
> CreateFileMapping and MapViewOfFile.
>
> If shared mem really improved loading of files on Unix, would you
> consider adding shared mem support on Windows too
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
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
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 provid
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 simil
On Mon, Sep 25, 2017 at 10:30 AM, Werner LEMBERG wrote:
>
> I've just committed Ewald's GSoC project to master. Please test!
>
Not sure if it's caused by the merge, but it gives a warning with gcc 7.2.0:
---
In file included from
/home/nsivov/devel/freetype/freetype2/src/psaux/psaux.c:35:0:
/h
On 18.05.2017 5:59, Chester Hsieh wrote:
> Hi, I'm Chester.
>
> I just start to use FreeType engine, and I'm interested in how it works
> with cache.
>
> Since it would be awesome if the FreeType has a internal cache mechanism so
> that once we query a character which had already been queried and
On 07.07.2016 19:56, Hin-Tak Leung wrote:
> I don't seem to have the very beginning of this thread so it is a bit
> difficult to see what's going on, anyway, there are
> a few things I like to respond to...
>
>
> On Thu, 7/7/16, freetype-devel-requ...@
On 06.06.2016 21:08, Qian Hong wrote:
> Hi folks,
>
> I am working on Wine support for a closed source Win32 application.
> This Win32 application bundle a freetype library to process fonts:
>
> https://www.reasoncoresecurity.com/freetype.dll-0aa9e1bd9e67aa9852df16152a83fcb1e7886d48.aspx
>
> In
On 03.12.2015 21:38, Werner LEMBERG wrote:
There is a misunderstanding, see above. `Native' ClearType doesn't do
y-only hinting! It's simply that advance width modifications are
ignored in Windows at a later stage, namely in the rasterizer.
I'm confused. Is this "native ClearType" actually
On 06.11.2015 1:09, Cosimo Lupo wrote:
Have you tried forcing Direct2D by setting "gfx.direct2d.force-enabled"
to "true"?
I did now, and it made no difference. That's a VM though, so maybe
software D3D rendering is considered too. gfx.direct2d.disabled is set
to false by the way.
_
On 05.11.2015 23:40, Nikolaus Waxweiler wrote:
gfx.font_rendering.cleartype_params.force_gdi_classic_for_families
indeed contained something by default, I tried to reset to empty string,
no change. Also if it really applies to specific family my guess would
be that RasterInfo font won't be affect
On 05.11.2015 22:06, Khaled Hosny wrote:
On Thu, Nov 05, 2015 at 07:43:21PM +0100, Werner LEMBERG wrote:
according to browserstack, the current release 41 of Firefox on
Windows 10 seems still to use the GDI framework, which implies font
rasterizer version 37, [...]
I suspect that browserstac
On 05.11.2015 21:15, Werner LEMBERG wrote:
Just tried that in a VM, and yes, your test page reports version 37,
compatible ClearType, no symmetrical smoothing.
Thanks for testing. How comes that Alexei reports something different
on an *older* Windows version? Note that on browserstack, bot
On 05.11.2015 20:35, Werner LEMBERG wrote:
Folks,
according to browserstack, the current release 41 of Firefox on
Windows 10 seems still to use the GDI framework, which implies font
rasterizer version 37, compatible widths ClearType, no supixel
positioning, and no vertical smoothing (i.e., B/W
15 matches
Mail list logo
