> Over at Python Pillow, we’ve had a user asking about
> https://www.dafont.com/brush-king.font. When Pillow calls
> FT_Glyph_Stroke on any of the letters abcdeghkmpqrvwz, FreeType
> returns Array_Too_Large. [...]
> So, my question - is there something I’ve done incorrectly in the
> above
> My problem arises when different faces have different baselines, and
> some faces (especially CJK) has weird baselines as CJK scripts
> technically don't have a concept of baselines. This causes the text
> using different faces to be offsetted vertically. I've thought of
> choosing the lowest
Hi,
I'm working on a renderer using FreeType. The renderer creates a list of
FT_Faces, and query each face to find a suitable glyph for a given codepoint.
This glyph is then rendered into a bitmap and stored for later use. When text
is rendered, the renderer calculates the position of the
> One question, is c++ built libfreetype binary completely compatible?
> It seems the opposite is (c++ built ft2-demos can use c-built
> freetype) is.
I think that in general it is possible to use C libraries as-is in C++
but not vice versa.
> Basically I am thinking of doing a
>
>
On Sunday, 16 July 2023 at 07:54:11 BST, Brad Neimann
wrote:
> ...Can anyone explain what’s
> happening here? I would expect that, if the diacritic is to be hinted as
> a horizontal bar, that would occur only at the smallest sizes, and would
> equally affect the combining diacritic too.
> * i modified benchmark program not to report 'time per op’ but
> rather 'cumulative time per N iterations'
> * changed the table design
> * sentence 'smaller values are better’ is present
> * embed a small CSS fragment at the top of the page
> * linked to the original baseline and benchmark
> I’ve attached an interesting hinting problem seen ‘in the wild’.
> [...] I would expect that, if the diacritic is to be hinted as a
> horizontal bar, that would occur only at the smallest sizes, and
> would equally affect the combining diacritic too.
The Noto fonts use `ttfautohint` for
On Sunday, 16 July 2023 at 07:13:20 BST, Werner LEMBERG wrote:
> > I added a "-s" command line option to both ftview and ftgrid to swap
> > rsvg out with skia and run the same binary twice, one with "-s" and
>.> one without, just to look at them side by side. Fixed the pixel
> positioning
On Fri, 14 Jul 2023 at 00:49, suzuki toshiya wrote:
> > The pkg-config interface should take care of everything easily. Debian
> and Ubuntu have the relevant qt5 pkg-config files. Other distributions
> should too.
>
> Does pkg-config give the information for the pathname of moc?
> (the original
> Btw, anybody done QT6 build of ftinspect lately?
Well, looking into `src/ftinspect/{meson.build,CMakeLists.txt}` I only
see build support for Qt5. Apparently, Qt6 support was tested
experimentally only.
Charlie, can you comment, please?
Werner
> [...] I seem to have found a problem with the rsvg/cairo-based hook
> with the Google Nabla color font.
>
> [...] I found that rsvg+cairo hook renders it B/W [...]. Strangely
> enough, with the skia-based hook, I see the expected color look.
> [...] this seems to suggest that the SVG in this
Btw, anybody done QT6 build of ftinspect lately?When I was writing the
makefile, I had to install some qt5*-devel packages. I did some qt3/qt4 stuff a
long time ago, so I kept those, but uninstalled most of qt5-dev stuff when I
see qt6 being installed as part of half-yearly upgrade. I am on
>> I would expect that, if the diacritic is to be hinted as a
>> horizontal bar, that would occur only at the smallest sizes, and
>> would equally affect the combining diacritic too.
>
> Somebody more knowledgeable can correct me, but I think combining
> diacritics happens with:
>
> Outline1
Yes, the moc location on fedora 38 can be queried with:
pkg-config Qt5Core --variable=host_bins
If this works correctly on other systems, we should set
MOC=`pkg-config Qt5Core --variable=host_bins`/moc
Or put PATH=${PATH}:`pkg-config Qt5Core --variable=host_bins` and MOC=moc ?
I am more inclined
On Sunday, 16 July 2023 at 07:02:50 BST, Werner LEMBERG wrote:
> > That fundamentally means it is not possible to switch the renderer
> > hook on a per current glyph level, keeping the current face?
>.I don't think so – who wants that except weird FreeType demo
> programs? :-)
> Moazin,
> another small patch for ft2-demos. Should be obvious/trivial.
Thanks, applied!
> I had a quick look at swapping the renderer hook on the fly. It
> seems that it is set when the module is loaded (i.e. the first font
> that needs it, I think), and I actually cannot see when it is
> unloaded,
> I added a "-s" command line option to both ftview and ftgrid to swap
> rsvg out with skia and run the same binary twice, one with "-s" and
> one without, just to look at them side by side. Fixed the pixel
> positioning discrepancies. Patch posted online below
>
>
>
I’ve attached an interesting hinting problem seen ‘in the wild’. The
image shows text ⟨ɑ̃ ɛ̃ ẽ ø̃⟩, rendered with Firefox 116.0b5 in font
Noto Sans Regular at zoom levels varying from 100% to 210%. (Although I
can reproduce the problem with ftstring too, as long as I force
auto-hinting). Note
18 matches
Mail list logo
