Hi Suzuki,
This email prompted me to check the official GSoC website. It still
lists FreeType as a participating organisation, with a link to the 2023
projects webpage. Should this perhaps be changed?
Regards,
Brad
On 22/2/24 17:10, suzuki toshiya wrote:
Dear Nitish,
I'm sorry, Werner and
Many-to-one: accent marks, e.g. umlauts
One-glyph-to-many-unicode-characters: ligatures, e.g. "ff", "fi".
I don’t see how these two cases are different. An accented glyph like
⟨ɑ̃⟩ is made up of two Unicode characters, ɑ+◌̃ (U+0251 U+0303);
similarly a ligated glyph like ⟨fi⟩ is made up of th
> Perhaps it is easier just to show you what I have - this is already
> functional and I can even switch COLRv1 palettes in ftgrid
> (screenshots the usual place).
…and where is this ‘usual place’? I can’t see screenshots anywhere.
Regards,
Brad
A long time ago I had some grad students write a compiler
infrastructure for TrueType bytecode. Maybe it's mostly bit-rotted,
but if someone were interested in working on this, I could try to
help.
When I get some time, I’d be happy to look into this. I’ve been doing some
compiler-adjacent stuff
Whoops, just realised I sent my previous message to Werner alone rather than
the whole list… let me re-send it:
A somewhat related question - colour fonts are used beyond
emoji's. While there are 5 kinds of emoji fonts now, and most
people are using one of 4... but if you check Google Fonts
A somewhat related question - colour fonts are used beyond emoji's. While there
are 5 kinds of emoji fonts now, and most people are using one of 4... but if
you check Google Fonts, there are 10 colour fonts, one is emoji, but 6 are
Arabic (useful for annotating the Quran...) and 3 are Latin. So
Ah, I forgot about TrueType bytecode. Indeed, that would be challenging…
Regards,
Brad
Thanks Werner, Hin-Tak! That explanation makes sense to me.
> If Craig's modifications to the auto-hinter code become mature it
would be very helpful if they got added to `ttfautohint`, too (however,
this wouldn't be a trivial thing to do, unfortunately).
Hmm, what would make it so hard?
Reg
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
Hi Werner,
Great to hear! I mentioned this example largely because I thought it
might be helpful for Craig to have a specific font/font size/character
combination which triggers the bug. (To recap: Noto Sans Regular, 20
ppem, ⟨ñ⟩.)
Regards,
Brad
On 7/7/23 15:34, Werner LEMBERG wrote:
Hello
Hi all,
On this issue, I’ve noticed a particularly egregious example in the past
few days: around 20 ppem, with autohinting enabled, ⟨ñ⟩ in Noto Sans
Regular consistently renders with a horizontal bar, so as to be
indistinguishable from ⟨n̄⟩. As Werner mentioned some time ago, this
particular
Hi Craig,
Really excited to see this! The demos look great.
- When the assumptions the algorithm makes are broken, it can do
extreme modifications to the glyph's shape. For example, this is what
happens when you tell it that the double quotes character should be
adjusted with the "one glyph
Hi Craig,
Thanks for the tip about using ftgrid for testing. The breaking point
of i and j is similar in my case. As for the settings, I just made
sure to press f to force auto-hinting mode.
Indeed, I also just enabled auto-hinting mode. The TrueType hinting for
those fonts seems fairly goo
Hi Craig,
Unfortunately, it’s been a while since I last thought about this issue,
so I don’t recall precisely how I reproduced it. My methodology was,
basically, ‘play around with ftgrid with forced auto-hinting until I
find a character with issues’. And I have a horrible feeling I might
have
Hi Werner,
Although I am curious to know— what fraction of the time would you
estimate various stages to take? From what I understand, it sounds
like roughly 50% would involve designing the database and 50%
implementing it, but it’s hard for me to know.
My gut feeling says it's about 30% design
Hi Werner,
I think that the development of a generic database format and its
integration into the auto-hinter is the main problem. The most
important question to answer is how to tell the auto-hinter what to
do, in a rather generic way.
Let's take letter 'i': What exactly is the auto-hinter su
Hi Werner,
As far as I can see it is hard to split the project for adding a
capability database to the auto-hinter …
Just speculating here… might it be possible to reduce the workload by
only focussing on a few characters at first? From what I can see the
single worst Latin-script diacritics
Hi all,
I hope I’m not too late with this, but I am very interested in helping
out with the GSoC project to improve the auto-hinting of glyphs with
diacritics and other small elements. I have been irritated by poor
rendering of characters such as ‘ã’ and ‘ḷ’ for quite a while, so would
be exc
18 matches
Mail list logo
