From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.ciao.gmane.io!not-for-mail From: Newsgroups: gmane.emacs.devel Subject: Re: Ligatures Date: Mon, 18 May 2020 19:24:41 +0200 Message-ID: <20200518172441.GD31606@tuxteam.de> References: <20200517124125.000013a4@web.de> <97C7EAB7-10AB-4702-ABC8-EB6C1C50ABDB@gnu.org> <20200517165953.000044d2@web.de> <83lflqblp0.fsf@gnu.org> <83ftbybio3.fsf@gnu.org> <83zha69xs2.fsf@gnu.org> <83367x9qeq.fsf@gnu.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="IMjqdzrDRly81ofr" Injection-Info: ciao.gmane.io; posting-host="ciao.gmane.io:159.69.161.202"; logging-data="3716"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Mutt/1.5.21 (2010-09-15) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Mon May 18 19:25:51 2020 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jajWQ-0000q3-Hr for ged-emacs-devel@m.gmane-mx.org; Mon, 18 May 2020 19:25:50 +0200 Original-Received: from localhost ([::1]:59978 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jajWP-0006a7-In for ged-emacs-devel@m.gmane-mx.org; Mon, 18 May 2020 13:25:49 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:38124) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1jajVM-0004f5-LU for emacs-devel@gnu.org; Mon, 18 May 2020 13:24:44 -0400 Original-Received: from mail.tuxteam.de ([5.199.139.25]:59987) by eggs.gnu.org with esmtps (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.90_1) (envelope-from ) id 1jajVL-0001EP-8f for emacs-devel@gnu.org; Mon, 18 May 2020 13:24:44 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=tuxteam.de; s=mail; h=From:In-Reply-To:Content-Type:MIME-Version:References:Message-ID:Subject:To:Date; bh=NcpHkps6tPZbiO0qlFcQp9mXeT5SmoZZXzpmXgHUo8I=; b=kQ60VtwrORe/AOTyiEvSlCQ3LcGlE2p6dOD9+8uFLGctr4odFAXhupue6V/hrxZAXVdz0pfiV6eXmUsCl4aJe6aQHfrca51MygDOHaQT7fCUs7W6AfSBD9X6KSvWGKIyifPafoRYyU8QVzwJc14IGqXzXoykF7rAtgcKycYY4lfjP5Ut5czgjoFZl3gm16LSF5P2U0QnYtX7728dZZHCrrfjvMOOoXcujXifjpoPEYukp5YLe7R9iVox0sJQAYfbBpeHY80FZy3frwkuOC/ZaKXBNuUEIdKW8tEb0rBN2B+nJQeGtpjWDEeIUNcWc0hwO1fRhyaaZnU2gh5URAs4NA==; Original-Received: from tomas by mail.tuxteam.de with local (Exim 4.80) (envelope-from ) id 1jajVJ-0001SW-9G for emacs-devel@gnu.org; Mon, 18 May 2020 19:24:41 +0200 Content-Disposition: inline In-Reply-To: Received-SPF: pass client-ip=5.199.139.25; envelope-from=tomas@tuxteam.de; helo=mail.tuxteam.de X-detected-operating-system: by eggs.gnu.org: First seen = 2020/05/18 11:33:59 X-ACL-Warn: Detected OS = Linux 3.1-3.10 X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001 autolearn=_AUTOLEARN X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:250788 Archived-At: --IMjqdzrDRly81ofr Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, May 18, 2020 at 01:05:53PM -0400, Stefan Monnier wrote: > [ I know nothing about the underlying APIs and such, so speaking here > only as a random user. ] [...] > So, maybe we don't need very much info: all we need is a boolean which > tells us whether the glyph should be treated atomically or not. > When not treating it atomically, we would (somewhat arbitrarily) divide > the glyph horizontally into N equal sized "subglyphs" and draw the > cursor on the corresponding subglyph. I'm somewhat out of my depth here, but I have the hunch that some "ligatures" aren't "just stacked horizontally". > If Harfbuzz could tell us more precisely how to divide the glyph into > subglyphs, we could do a better job, of course. On a very superficial glance it seems they can [1] Cheers [1] https://github.com/harfbuzz/harfbuzz/blob/master/docs/usermanual-cluste= rs.xml -- tom=C3=A1s --IMjqdzrDRly81ofr Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAl7CxNkACgkQBcgs9XrR2kZPzwCcC0NDO4jHE7YeBQFhKJ4k63xZ oT8An3bnRPxXkft63fnKLJUf28vAxrkf =lJkQ -----END PGP SIGNATURE----- --IMjqdzrDRly81ofr--