Dyalog Forums

I've been looking at Stefan Kruger's excellent Learning APL at https://xpqz.github.io/learnapl/intro.html
and noticed that there is a problem with the display of Tally at
https://xpqz.github.io/learnapl/manip.h ... epth-match
in Chrome and Opera, though it displays properly in Firefox.
(Incidentally, the text displays OK in Windows Notepad.)

Before taking the matter up with Chrome and Opera, I wanted to make sure that there were not any other considerations that need to be taken into account.

Nicholas

It's the font, and Google does not care.

It is a well known issue with the glyph renderer under Chrome.
The story so far:

• https://bugs.chromium.org/p/chromium/issues/detail?id=620629
• https://github.com/harfbuzz/harfbuzz/issues/1092

As things stand, the only way forward seems to be to switch to a different font. Which, in itself, is a problem because, as far as I know, there are no working monotype fonts with good APL glyphs.

Hi Nicholas,

Could you try your problematic browsers again? Trying to serve up the APL365 font from the book itself to see if that helps.

Many thanks,

Stefan

Maybe its just coincidence but I'm claiming the credit for getting this sorted. Two days ago I reported it as a browser problem in each of Edge, Opera and Chrome - pointing out to each of them that it was OK in Firefox and Windows Notepad - and today they all display tally correctly!

The fact that they all changed together suggests, perhaps, that they were all using the same faulty code from a single source.

Nicholas

This is in Chrome Version 98.0.4758.82 (Official Build) (64-bit) and in Edge (same version) as far as I can tell, it's still broken:

Stefano,

How are you displaying your example - can you send me a link?

I'm using Windows 10, 32 bit on my PC and 64 bit on my laptop, both correctly displaying tally at
https://xpqz.github.io/learnapl/manip.h ... epth-match
Does this display correctly for you?
Incidentally, the version of Edge is probably 98.0.1108.50.

Nicholas

Unfortunately, tt does not:

This is with Edge, same version as before. Cache cleared with a Ctrl-F5 to make sure the new version of the page was loaded.

Nicholas, countless people have reported this to Google, and in their arrogance they have managed to ignore all these reports for several years.

No way they are going to change that any time soon, and even if they did, before the change can reach you in the best of worlds, it would take considerable time.

Assuming this is a PC-only issue for Chrome. I use Chrome (Version 98.0.4758.80 (Official Build) (x86_64)) on a Mac (MacBook Air ca. 2020) and everything appears copasetic. In the past, to be sure, it did not work...