💾 Archived View for bbs.geminispace.org › s › Lagrange › 14399 captured on 2024-03-21 at 18:04:42. Gemini links have been rewritten to link to archived content
⬅️ Previous capture (2024-02-05)
-=-=-=-=-=-=-
Today the iOS developer Beta rolled out with some new emoji ZWJ sequences for Phoenix, Lime, Brown Mushroom, Broken Chain, etc
I'm curious if I can expect these to be viewable in Lagrange eventually? How long does it take for the Noto Emoji font to update?
In a related question, how does Lagrange decide when to use a Unicode character for a link icon? I noticed that ◉ and ◎ can be used as link icons, but not ⦿, and I have no idea why.
Example:
Jan 26 · 8 weeks ago
Only the first of the three glyphs mentioned (bullseyes) renders on my XFCE terminal, with any of the fonts I have in a freshly-installed void linux.
🐐 satch [OP] · Jan 26 at 23:29:
Here is a screenshot so people can see what I'm talking about without using Lagrange.
I should clarify that only the first glyph renders as a Unicode glyph, and it has nothing to do with Lagrange -- I am talking about the raw XFCE terminal with DejaVu Sans Mono font!
Sorry if I am OT
🚀 skyjake [mod...] · Jan 27 at 05:15:
@satch At least the Phoenix and Lime were published in Unicode 15.1, and there is a version of Noto Emoji available that supports 15.1 (since late September 2023). I'll have to download and test it in Lagrange, and update the relevant fontpack(s).
The Noto Emoji font seems to update pretty regularly, but of course, I also need to update my copy of it included with Lagrange.
how does Lagrange decide when to use a Unicode character for a link icon?
It's just a set of hardcoded character ranges. I can add the ⦿ as an allowed link icon.
@stack Lagrange does not use system fonts on most operating systems, for better portability. Only on macOS and Windows I'm accessing a couple system fonts directly, because a) those are available in .ttf format and 2) at a specific unambiguous file path.
🍵 michaelnordmeyer · Jan 27 at 08:49:
Using Noto Emoji broke at least RTL rendering in Lagrange:
— bbs.geminispace.org/s/Lagrange-Issues/16
🚀 skyjake [mod...] · Jan 27 at 08:59:
Note that Noto Emoji is always bundled with Lagrange. That issue was with the separately installed fontpack.
🍵 michaelnordmeyer · Jan 27 at 19:30:
@skyjake It was installed from gemini://skyjake.fi/fonts/noto/. Is there a difference between the bundled and the download one? I installed it because the default Lagrange emoji are limited and especially don't support male/female/person variants.
🚀 skyjake [mod...] · Jan 29 at 06:22:
@michaelnordmeyer When it comes to the gender variants, I'm not sure if Lagrange can render them. HarfBuzz should be able to select the right glyphs based on the ZWJ code points, but it might be hindered by the lower-level TrueType library I'm using.
The configuration with Noto Emoji specifically is more complicated than you might think. Lagrange actually bundles BOTH an older and a newer version of it. The newer bundled one is used as a fallback if the old one does not have some glyph (because I prefer the look of the old version). If you install the Noto Emoji fontpack from the library, then you have three copies of Noto Emoji available.
At that point, the fontpack priority values determine which instance of the font is used for a particular glyph. The fontpack from the library has a lower priority than the old bundled Noto Emoji, but higher than the newer bundled one. So: installing the fontpack from the library overrides only the newer bundled Noto Emoji, and the old copy still has the highest priority.
In other words, installing the Noto Emoji from the library should only give you additional glyphs that are missing from the bundled old font.
If this sounds complicated, yeah it is, and I'm not surprised it's causing some unexpected behavior.
