Post AY1Y8GgOHeV3zI7qds by mart_e@mamot.fr
 (DIR) More posts by mart_e@mamot.fr
 (DIR) Post #AY1TZkXYsljkdZHT3A by mart_e@mamot.fr
       2023-07-24T05:34:58Z
       
       0 likes, 0 repeats
       
       Any idea why is #lagrange showing me this message? I don't think these are present in @ploum 's article 🤔 gemini://ploum.net/2023-07-23-pour-une-poignee-de-followers.gmiIs it lagrande trying to have unique identity on each #gemini  website?
       
 (DIR) Post #AY1TZlYf6AD9nGnrP6 by mart_e@mamot.fr
       2023-07-24T14:39:07Z
       
       0 likes, 0 repeats
       
       @jk 👋 thanks for making #lagrange. I am not sure to understand what is the purpose of the glyphs needed in above message☝️ @Vasco
       
 (DIR) Post #AY1TZmIOM8n656CNgO by jk@skyjake.fi
       2023-07-24T15:00:01Z
       
       0 likes, 0 repeats
       
       @mart_e @Vasco Hmm it may be a bug. Perhaps most of those characters were missing on a previously viewed page?U+156C: Canadian Syllabics TthiU+FF08: Fullwidth Left ParenthesisU+202F: Narrow No-Break Space (NNBSP)U+23BA: Horizontal Scan Line-1U+29BB: Circle with Superimposed XU+5BC6: 密 CJK Unified IdeographU+7387: 率 CJK Unified IdeographU+8A66: 試 CJK Unified IdeographU+9A57: 驗 CJK Unified Ideograph
       
 (DIR) Post #AY1TruvwykIM5HLqOO by jk@skyjake.fi
       2023-07-24T15:03:29Z
       
       0 likes, 0 repeats
       
       @mart_e @Vasco I checked the page myself and it appears U+202F is the missing one for me (without ‘notosans-set’ enabled).
       
 (DIR) Post #AY1VaPYWaTwZkkAs6a by mart_e@mamot.fr
       2023-07-24T15:22:40Z
       
       0 likes, 0 repeats
       
       @jk hmm maybe. I have tried removing the fonts from my system and reaccessing the page and I have only the U+202F left.I came from an aggregator. Are the missing glyphs errors kept from page to page?
       
 (DIR) Post #AY1Y8GgOHeV3zI7qds by mart_e@mamot.fr
       2023-07-24T15:31:07Z
       
       0 likes, 0 repeats
       
       @jk ok I succeeded to reproduce.- Go to gemini://warmedal.se/~antenna/ (4 missing glyphs) - clicked @ploum 's article (still 4 missing)- restart lagrange (only 1 missing)I don't know if it's a bug or expected. Do you want me to report it on github?
       
 (DIR) Post #AY1Y8HWr8aT2c0fkQ4 by jk@skyjake.fi
       2023-07-24T15:51:11Z
       
       0 likes, 0 repeats
       
       @mart_e @ploum Thanks but no need to report. I checked the code and this is the expected behavior.Perhaps the warning dialog is a little too vague, because the warnings apply to _any_ text rendered by the app (could be UI as well), and the warnings are only reset when fonts are (un/re)loaded.For now, I can rephrase the message a little to make it clear that the missing glyphs weren't necessary on the current page.
       
 (DIR) Post #AY1ZLT7BTM0kGQW4eW by mart_e@mamot.fr
       2023-07-24T16:04:48Z
       
       0 likes, 0 repeats
       
       @jk that would be totally enough, thanks for the additional info :)
       
 (DIR) Post #AY1bkuKfcCtppF5ATg by ploum@mamot.fr
       2023-07-24T16:07:37Z
       
       0 likes, 0 repeats
       
       @mart_e @jk @Vasco : I also always have this warning with Lagrange. I guess it is shown when some non-ascii UTF-8 characters are used.
       
 (DIR) Post #AY1bkv2cym3s1ZeGzg by jk@skyjake.fi
       2023-07-24T16:31:48Z
       
       0 likes, 0 repeats
       
       @ploum  It depends on which Lagrange fontpacks are installed. By default, the app comes with a limited set of fonts. "notosans-set" is big but it fixes most capsules' glyph warnings.You can also just disable the warnings altogether if you don't intend to install additional fonts (Preferences > Content > Font glyph warnings).@mart_e @Vasco
       
 (DIR) Post #AYEqWTIMm0SBjtGJqC by swansinflight@mastodon.nz
       2023-07-31T01:48:24Z
       
       0 likes, 0 repeats
       
       @jk @ploum @mart_e @Vasco yeah I just found this browser snd added that font pack to rectify that exact warning.