From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <9front-bounces@9front.inri.net> X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-0.9 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI autolearn=ham autolearn_force=no version=3.4.4 Received: from 9front.inri.net (9front.inri.net [107.161.22.3]) by inbox.vuxu.org (Postfix) with ESMTP id DB1892021E for ; Mon, 20 Jan 2025 18:55:50 +0100 (CET) Received: from ftrv.se ([45.76.35.157]) by 9front; Mon Jan 20 12:55:06 -0500 2025 Message-ID: <71EB7EFDD1FE6072977E6E7BE02A0B53@ftrv.se> DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ftrv.se; s=mail2; t=1737395703; bh=XhsxZH8eFdMiQ/jM1XmTNLIq3qlchf/OdNpWvUFiaVM=; h=Date:From:To:Subject:In-Reply-To; b=wEWC2006IfMMCkaFI8aIti6ODsK1jPwtJ8n6HS2HsaEfKpHRQpc9JFgTkvk89tmwc 47lWrcLmw3XZsfsOJbQcS5WjKttoO+pJ25M1oq5BKzGuXryIcR1BKLV2hlmVJcgHMj 4GtgDCnsY8OgPRzK6JIQmbB0/0ctzua7HjFTWa6tffHDE2CNXKRrrV1oHcu7pEZaYt tUJFEhWJIBWqtchNAMQmVcdqt9PQn1ELsk5SWTebqwO1VMc2A/WRrVASRCqQXWMpuO ZEy/KnIFwMEz3j+z1hHAIR5l7NFlw1nM1tg4dZkAScyd7OFU6DilSMPhpmm1c2cdFn DVepvI0dtd2Uw== Date: Mon, 20 Jan 2025 18:55:02 +0100 From: =?utf-8?q?Sigrid_Solveig_Hafl=C3=ADnud=C3=B3ttir?= To: 9front@9front.org In-Reply-To: <8302888013961FED3068DAF6DC307D4A@eigenstate.org> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: JSON module-scale polling standard Subject: Re: [9front] Truetypefs anti-aliasing Reply-To: 9front@9front.org Precedence: bulk > I the path forward may be to port truetypefs to this, and then > remove libttf -- Sigrid, thoughts? That's one way to do it, yeah. I am not exactly happy about truetypefs' code itself so I am not sure if doing it from scratch is easier or not. Somebody can try doing that - fnt already has a test tool that runs on 9front and can produce the whole glyph map as an image.