9front - general discussion about 9front
 help / color / mirror / Atom feed
From: ori@eigenstate.org
To: 9front@9front.org
Subject: Re: [9front] truetypefs
Date: Fri, 06 Nov 2020 08:07:45 -0800	[thread overview]
Message-ID: <DE94C11436C68CBCBFBA854E5353F045@abbatoir.fios-router.home> (raw)
In-Reply-To: <012440E4E4FD8FD9B1E1955DA8640092@sdf.org>

> Hi all,
> 
> truetypefs used to crash for me; it used to happen when trying to display
> some non-ASCII glyph, e.g., an accented vowel: à.

So, I remember looking into this a while back, and I asked aiju
about it at the time -- here's the response:

 aiju  | Ori_B: there is a dumb corner case i didn't expect any font to hit
 aiju  | but some fonts hit it anyway
 Ori_B | oh?
 aiju  | Ori_B: where ALL the points on a curve are off-curve
 aiju  | this might be the same bug
 Ori_B | oh... hm.
 aiju  | it's probably not too hard to figure out but i have all this shit paged out right now
 Ori_B | I can verify that at least.
 aiju  | i think you need to pick two points and calculate the average and use that as a starting point
 Ori_B | that sounds reasonable.
 aiju  | i literally just didn't implement it because i figured no font would do this shit
 Ori_B | yeah, it's some unicode junk that I appear to have accidentally gotten into the
         file, so I didn't hit it on a common glyph.
 Ori_B | should we also return a 'bogus glyph' instead of killing font rendering?
 Ori_B | '?', pjw face, something?



      parent reply	other threads:[~2020-11-06 16:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-30 17:45 truetypefs nicolagi
2020-10-31 11:42 ` [9front] truetypefs cinap_lenrek
2020-11-06 16:07 ` ori [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=DE94C11436C68CBCBFBA854E5353F045@abbatoir.fios-router.home \
    --to=ori@eigenstate.org \
    --cc=9front@9front.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).