4,494
edits
Fonts: Difference between revisions
Jump to navigation
Jump to search
→Rendering APL on websites
(JetBrains Mono) |
|||
| Line 132: | Line 132: | ||
</syntaxhighlight> | </syntaxhighlight> | ||
The <syntaxhighlight lang=shell inline>Apl385.ttf</syntaxhighlight> font file must be placed in the same directory as the HTML file, and all APL code must be wrapped in <syntaxhighlight lang=html inline><pre></syntaxhighlight> or <syntaxhighlight lang=html inline><code></syntaxhighlight> elements. | The <syntaxhighlight lang=shell inline>Apl385.ttf</syntaxhighlight> font file must be placed in the same directory as the HTML file, and all APL code must be wrapped in <syntaxhighlight lang=html inline><pre></syntaxhighlight> or <syntaxhighlight lang=html inline><code></syntaxhighlight> elements. | ||
== Bad rendering == | |||
The [[wikipedia:Blink browser engine]] instructs the [[wikipedia:HarfBuzz]] text shaping engine to prefer fidelity in typeface over fidelity in glyph shape. As a consequence, text using a font that lacks the <syntaxhighlight lang=apl inline>≢</syntaxhighlight> glyph ([[Tally]], [[Not Match]]) often ends up looking like <syntaxhighlight lang=apl inline>≡/</syntaxhighlight> (Match reduction), causing great confusion. The issue affects diverse things like Android WebView, Chromium Embedded Framework, all [[wikipedia:Electron (softwareframework)|Electron]] apps, [[wikipedia:Qt software)|Qt software)]], as well as many popular web browsers, like Amazon Silk, Google Chrome, Microsoft Edge, Brave, Opera, Vivaldi, and the Yandex Browser. | |||
In browsers, it is possible to mitigate the problem by overriding the used font, for example using a user style manager, or by setting the browser to override fonts. | |||
== Changing font in Dyalog RIDE == | == Changing font in Dyalog RIDE == | ||