Hi everyone,
I'm on Q4OS (Debian-based) with Trinity Desktop, and as per title, I have a weird issue since I started using Q4OS back in May, and I still haven't been able to solve it: in some (not all) applications, instead of some kind of characters (more specifically, emojis and italics) tofu boxes appear, and I already installed fonts-noto with all its dependencies.
I opened this thread in the Q4OS Support Forum: https://www.q4os.org/forum/viewtopic.php?pid=27828#p27828 and they told me it's a Trinity related bug, as it also happens on a pure Debian fresh install with TDE.
How can it be solved?
TIA
On Wednesday 11 December 2024 22:07:36 padota1663--- via tde-users wrote:
Hi,
can anyone help me?
Thanks
Hi,
I've been using TDE for years on Debian and Debian-based distributions and I see no such "Tofu boxes".
I'd guess this is a font problem, but I doubt we can help without any more information from your side:
I have a weird issue since I started using Q4OS back in May, and I still
haven't been able to solve it
So this *may* be a Q4OS problem. I remember from a (short) try that they did not implement a standard TDE and did not install some packages.
in some (not all) applications, instead of some kind of characters (more
specifically, emojis and italics) tofu boxes appear
It may help if you give a list of some applications that show the problem. this would at least let us test if these applications show the problem on our machines.
I already installed fonts-noto with all its dependencies
Why specifically noto? Here noto emoji seems to work, at least in LibreOffice.
Thierry
Hi Thierry,
I didn't know that the Q4OS Team used a non standard TDE, in fact they straight out told me it's a TDE issue, as you can read from my post in their forum, of which I left the URL.
As for the applications which display the issue, Dolphin and VLC are the most notable ones, Firefox does not have this issue, for example.
I installed noto-fonts because many solutions that came up googling around suggested to do so.
Thanks
On Saturday 14 December 2024 15:51:01 padota1663--- via tde-users wrote:
Hi Thierry,
(...)
As for the applications which display the issue, Dolphin and VLC are the most notable ones, Firefox does not have this issue, for example.
Dolphin and Firefox I don't use, so I can't say.
With VLC I see no tofu box. You see them in filenames?
If so, were these files created on Linux or some other operating system? I remember having seen such things with chinese or russian file names, when bo font was available to render them.
I have quite a huge number of fonts on my machine (not that I really want them, but various software install them).
It's also not clear to me what sort of font is used by whom: trutype fonts are used by my wordprocessors, but in /usr/share/fonts there are also cMap, cmap, opentype, type1 and X11. I'd say display uses X11 but in my system I never tinkered with them. And they should not ne TDE related (in my understanding, which may be wrong!).
I have not re-read all this thread, but if the problem occurs in Q4OS + TDE, but not in Debian + TDE, then its either a Q4OS problem or linked to their implementation of TDE.
Thierry
Hi Thierry,
the files have been created on this same machine which has the issue, so directly on Linux.
I have, at least for the moment, avoided to install every available font from the repos, as I have limited space, even if I thought of giving it a shot.
I already tested creating a new user and changing the theme, as deloptes instructed me to test it, but it didn't solve nothing.
The guys at Q4OS forum told me these exact words:
"We have performed some testing and we can confirm a bug in Trinity desktop related to UTF-8 named files. While the file names are displayed correctly in Plasma applications and desktop, the same file names shows unknown characters in Trinity apps.
We have also made testing on pure Debian/TDE installation with the same result. So the bug is not native Q4OS, but Trinity desktop one. We would suggest you to report it for Trinity developers directly https://trinitydesktop.org/ . Thanks for reporting."
This is why I came here reporting this issue.
Regards
On Saturday 14 December 2024 18:35:13 padota1663--- via tde-users wrote:
Hi Thierry,
(..)
The guys at Q4OS forum told me these exact words:
"We have performed some testing and we can confirm a bug in Trinity desktop related to UTF-8 named files. While the file names are displayed correctly in Plasma applications and desktop, the same file names shows unknown characters in Trinity apps.
OK. then could you possibly zip, gz or some other archive process one or two files that show this problem and post them here (even empty files if the problem shows only in the file name)?
I could then look if the problem happens here too.
I use UTF-8 and did not see such problem.
Thierry
Here is a .tar which contains the "problematic" font in the name, the files and the folder inside it also have this issue, and the same goes for some text inside one of the files: https://filebin.net/b3chfxansirq461w
On Monday 16 December 2024 01.06:48 padota1663--- via tde-users wrote:
Here is a .tar which contains the "problematic" font in the name, the files and the folder inside it also have this issue, and the same goes for some text inside one of the files: https://filebin.net/b3chfxansirq461w
Hi Padota,
I can confirm that I too see tofu boxes in TDE (snapshot2).
This machine has TDE for one user and xfce for the other, so I checked and the tar file has a readable name in xfce - so there *is* a TDE issue.
However, the filenames inside the archive (snapshot3) so show strage caracters also in xfce.
Thierry
Thierry via tde-users wrote:
This machine has TDE for one user and xfce for the other, so I checked and the tar file has a readable name in xfce - so there *is* a TDE issue.
As I wrote earlier, several years ago I was looking into similar issues and found out that TDE supports a version of UTF, that does not cover all chars, but I do not recall the details.
Interesting is following test.
1. create a text file with file name and content with the problematic chars 2. execute file command on the file
e.g
file ~/охлюви.txt охлюви.txt: Unicode text, UTF-8 text, with very long lines (485)
Let us see what is the output
I tested with the example you posted:
- create a text file with file name and content with the problematic chars
- execute file command on the file
e.g
file ~/охлюви.txt охлюви.txt: Unicode text, UTF-8 text, with very long lines (485)
Let us see what is the output
but I don't have any issues with cyrillic fonts, here is the output:
a@scatorcio:~/Scaricati$ file ~/Scaricati/охлюви.txt /home/a/Scaricati/охлюви.txt: ASCII text a@scatorcio:~/Scaricati$
I also correctly see cyrillic text displayed in the applications where I don't see "𝘙𝘪𝘰𝘮𝘢" displayed.
Hi, I am away from my computer for a few days, but basically plane 0 of the unicode standard is displayed correctly while other planes are likely to be handled incorrectly. Plane 0 contains most of "normal" characters, so that's why Cyrillic is displayed correctly. The Rioma characters are in plane 1 and hence not displayed correctly. Cheers Michele
On December 22, 2024 1:32:52 AM GMT+09:00, padota1663--- via tde-users users@trinitydesktop.org wrote:
I tested with the example you posted:
- create a text file with file name and content with the problematic chars
- execute file command on the file
e.g
file ~/охлюви.txt охлюви.txt: Unicode text, UTF-8 text, with very long lines (485)
Let us see what is the output
but I don't have any issues with cyrillic fonts, here is the output:
a@scatorcio:~/Scaricati$ file ~/Scaricati/охлюви.txt /home/a/Scaricati/охлюви.txt: ASCII text a@scatorcio:~/Scaricati$
I also correctly see cyrillic text displayed in the applications where I don't see "𝘙𝘪𝘰𝘮𝘢" displayed. ____________________________________________________ tde-users mailing list -- users@trinitydesktop.org To unsubscribe send an email to users-leave@trinitydesktop.org Web mail archive available at https://mail.trinitydesktop.org/mailman3/hyperkitty/list/users@trinitydeskto...
Hi Michele, Thank you very much for the above details.
I'll be keeping an eye on this thread and on TGW to see how it progresses.
Regards
Sorry Thierry,
I think you pasted some link to some screenshot in your message but somewhat they got lost, is it possible?
On Saturday 21 December 2024 17:34:49 padota1663--- via tde-users wrote:
Sorry Thierry,
I think you pasted some link to some screenshot in your message but somewhat they got lost, is it possible?
There were two screenshots. I Can see them in my mail on the list. Anyway, what they showed has been confirmed by others, so it's not important.
On 2024/12/16 09:06 AM, padota1663--- via tde-users wrote:
Here is a .tar which contains the "problematic" font in the name, the files and the folder inside it also have this issue, and the same goes for some text inside one of the files: https://filebin.net/b3chfxansirq461w
There is indeed a problem in TDE: Konqueror and Konsole show tofu boxes, while xfce-terminal (within the same session) shows the italics "Rioma" folder, although some of the files inside still shows some numbered tofu boxes. Windows 11 displays these ones as some "power arm" symbol.
I have created an issue on TGW to track this.
Cheers Michele
Michele Calgaro via tde-users wrote:
There is indeed a problem in TDE: Konqueror and Konsole show tofu boxes, while xfce-terminal (within the same session) shows the italics "Rioma" folder, although some of the files inside still shows some numbered tofu boxes. Windows 11 displays these ones as some "power arm" symbol.
I have created an issue on TGW to track this.
I was trying to refresh my memory today, but I couldn't, but I recall there was something around the state of UTF implemented in TDE ... could it be it was 32bit and therefor not able to show all the characters? May be the answer is hidden in TQt.
There is indeed a problem in TDE: Konqueror and Konsole show tofu boxes, while xfce-terminal (within the same session) shows the italics "Rioma" folder, although some of the files inside still shows some numbered tofu boxes. Windows 11 displays these ones as some "power arm" symbol.
I have created an issue on TGW to track this.
I was trying to refresh my memory today, but I couldn't, but I recall there was something around the state of UTF implemented in TDE ... could it be it was 32bit and therefor not able to show all the characters? May be the answer is hidden in TQt.
You have a good memory Emanoil, and yes the problem could well be in TQt Unicode support. See https://mirror.git.trinitydesktop.org/gitea/tde/tqt3/issues/162
Cheers Michele
Michele Calgaro via tde-users wrote:
You have a good memory Emanoil, and yes the problem could well be in TQt Unicode support. See https://mirror.git.trinitydesktop.org/gitea/tde/tqt3/issues/162
Great thank you and Obata san ... I was off with about 16bits but I hope my memory serves me in the next 50+ years like it did in the past :)
There are still some issues with some of the parsers, but they are not related to the "tofu" boxes in this particular case.
Michele Calgaro wrote:
On 2024/12/16 09:06 AM, padota1663--- via tde-users wrote:
Here is a .tar which contains the "problematic" font in the name, the files and the folder inside it also have this issue, and the same goes for some text inside one of the files: https://filebin.net/b3chfxansirq461w
There is indeed a problem in TDE: Konqueror and Konsole show tofu boxes, while xfce-terminal (within the same session) shows the italics "Rioma" folder, although some of the files inside still shows some numbered tofu boxes. Windows 11 displays these ones as some "power arm" symbol.
I have created an issue on TGW to track this.
Cheers Michele
Ciao Michele, thank you very much, I'll keep an eye on this thread for news :)
Can you please share here the link of the opened issue? I went to https://scm.trinitydesktop.org/gitea/explore/repos but I can't seem to find anything, if I'm wrongdoing something (i.e. I visited the wrong link) please let me know.
I'd like to also say thank you to everyone who is participating for their effort.
BR padota1663
Nevermind, I found it: https://mirror.git.trinitydesktop.org/gitea/TDE/tde/issues/218
On 12/14/24 9:35 AM, padota1663--- via tde-users wrote:
"We have also made testing on pure Debian/TDE installation with the same result. So the bug is not native Q4OS, but Trinity desktop one. We would suggest you to report it for Trinity developers directly https://trinitydesktop.org/ . Thanks for reporting."
There are a lot of us using TDE on Debian, and apparently none of us have the problem. So if the Q4OS folks are being truthful with the above, it seems likely the problem is with their customized TDE. So you might consider installing TDE from the TDE repo, and see if the problem still exists.
Dan Youngquist via tde-users wrote:
There are a lot of us using TDE on Debian, and apparently none of us have the problem. So if the Q4OS folks are being truthful with the above, it seems likely the problem is with their customized TDE. So you might consider installing TDE from the TDE repo, and see if the problem still exists.
I have a similar problem on one of my PCs - there it mangles the names of some directories. I couldn't understand why. It is also Debian.
Years ago I was looking into some of the parsers and they need improvement especially for the reason of mangled chars.
I would not exclude this issue in TDE which may appear or not depending on circumstances we do not know.
BR
Hi Dan,
thanks for the suggestion, I posted a link to a .tar file above, in an answer to Thierry, so you guys can check it and the files / folders inside; if the response will be that none of you encounters the issue, I'll do some testing in a freshly installed pure Debian VM with TDE installed from the repos.
Regards
On Sat, 14 Dec 2024 14:51:01 -0000 padota1663--- via tde-users users@trinitydesktop.org wrote:
I didn't know that the Q4OS Team used a non standard TDE, in fact they straight out told me it's a TDE issue, as you can read from my post in their forum, of which I left the URL.
I would guess that they didn't want to actually *say* "We have no idea what's going on here, so let's bat it upstream."
As for the applications which display the issue, Dolphin and VLC are the most notable ones, Firefox does not have this issue, for example.
Hmmm. By "Dolphin", do you mean the non-default TDE file management program, or the default KDE file management program, or the Gamecube emulator?
The reason I ask is that VLC is a QT5 or QT6 program depending on version, and two of the Dolphins are as well. That would point to some problem with QT5 or QT6, since Firefox is GTK. If it's TDE's Dolphin, that isn't the problem, though.
Does Konqueror have any problems, or is it OK?
I installed noto-fonts because many solutions that came up googling around suggested to do so.
It actually isn't bad advice, and would have fixed most common missing-glyphs problems. However, I don't think that's what you have here.
You said in one of your earlier messages that this was affecting italic text. Are you absolutely certain? That's exceptionally weird and points to a problem with the widget libraries, or fontconfig, or X font handling.
Have you changed any font settings on your system? That includes font settings in the TDE Control Center, in any other program, or any setting that's related to fontconfig.
Have you removed any fonts from your system, either by uninstalling through the package manager or just deleting their files?
Have you installed any fonts other than Noto?
Did you install the programs that are having trouble through the system package manager, or through some other method (like flatpak or compiling your own copies)?
Have you ever installed any themes or created any settings for QT5/QT6?
E. Liddell
I would guess that they didn't want to actually *say* "We have no idea what's
going on here, so let's bat it upstream."
Mmmhh, so you suspect they straight out decided to not give a damn and investigate further? I hope that's not the case, but who knows...
By Dolphin, I mean the file manager, which wasn't the TDE default, I set it as default as I find it highly more comfortable to use than Konqueror, I didn't mean the Gamecube emulator.
I'm not absolutely certain it's affecting Italic text, at least not **only** Italic, at the moment I just witnessed that it affect a kind of text which seems like Italic to me; however, I just posted, in my last answer to Thierry, a link to a .tar archive whose name contains the affected characters, the same goes for the files and folders inside it, and even one of the text files contains some affected letters inside, so feel free to check it out and do tests with it.
I never changed any default fonts, let alone remove some of them, only installed noto as additional fonts after googling around for a solution, didn't install nothing else.
The programs which are giving issues were preinstalled with the system since first boot.
Never installed any additional themes or created settings for QT5/QT6.
Regards
On 12/15/24 6:23 PM, padota1663--- via tde-users wrote:
By Dolphin, I mean the file manager, which wasn't the TDE default, I set it as default as I find it highly more comfortable to use than Konqueror, I didn't mean the Gamecube emulator.
Not a solution to your issue, but worth a comment. Configuring TDE the way it was meant to be used with:
Control Center:
Peripherals->Mouse->General Single-click to open files and folders
Desktop->Window Behavior->Focus Focus Policy: Focus Follows Mouse [ ] Auto raise [ ] Delay focus [x] Click raise active window
Konqueror:
Configure tree-view in the detail pane.
With that config, I've found konqueror to be quite possibly the most elegant, efficient and capable file-manager I've used in 2+ decades of using every desktop and file-manager going.
One key point that many miss is how to select without activating/launching the file under the mouse in the details pane. The key is to click in the "Name" column to the right of the text in the empty-space (or to the right of the text in any other column).
Konqueror is so well thought out that you can accomplish more with fewer mouse-clicks or keystrokes than in any other I've found. It is a real joy to use once you understand its nuances. It truly was designed that way. To accomplish every task in the most efficient manner possible.
Dolphin didn't appear until kde 3.5 was already mature. It was a stripped-down file-manager aimed at being easier to use for new users than konqueror. It was, but it gave up a majority of what makes konqueror such a supreme file-manager.
Never installed any additional themes or created settings for QT5/QT6.
Installing the themes is the easy part, applying them to the application within TDE can be a trick. For Qt5, the too qt5ct (Qt5 config tool) works really well and you likely have a package for your distribution. It is a gui application that allows you to preview the theme and it then writes a small config file. If you are adventurous, you can modify the themes it provide to your liking without much trouble.
Sorry none of this solves your original problem completely, but consider both the use of konqueror and the Qt5ct tool to resolve some of the tangential issues raised. Good luck.
On 2024/12/12 06:07 AM, padota1663--- via tde-users wrote:
Hi,
can anyone help me?
Ciao Padota, this seems most likely a font rendering issue, you probably need the correct font family installed. I have the same issue when I try to display Korean characters in a plain debian VM. Installing the correct font and making sure to use it should probably fix the problem, but if you can create an issue on TGW and upload a file for testing, I will do a bit more research on this.
Cheers Michele
Ciao Michele,
the issue is that I don't specifically know the exact font which causes this issue; moreover, as I just told Thierry, this doesn't happen universally, so this leads me to think it's not a fonts issue, but rather some kind of bug elsewhere.
The only solution I came up with is installing every single fonts package in the .deb repos, but that means hogging up several gigabytes of drive space without the certainty of solving the issue, so for now I set that aside.
Sorry if I ask but what is TGW? Do you mean the Gitea bug reporting site? I already signed up to that site, but I don't see nowhere a button to file an issue / bug report, otherwise I'd have already opened a case, and attached the related evidence, just like I did in the Q4OS forum.
I made a screenshot of what I see when I enter in Gitea, but I don't know how to attach it here.
Thanks
Ciao Padota,
Sorry if I ask but what is TGW? Do you mean the Gitea bug reporting site? I already signed up to that site, but I don't see nowhere a button to file an issue / bug report, otherwise I'd have already opened a case, and attached the related evidence, just like I did in the Q4OS forum.
Yes, the Gitea bug reporting site. TGW = TDE Gitea Worksspace.
After reading all the emails on the mailing list, it may be better you zip one or two of the files that are giving you problems and attached them to an email, so we can try them out on our systems and see what happens here. So far, the description is not clearly pointing to one direction specifically, so we need to find out more. In general, I experience "tofu" boxes with non-Western languages if I don't have the right language font installed. I have seen this in many applications and various OS, even not linux.
So if you can share a few files (even empty, just with the same name), we could try to figure out more about it. Cheers Michele
I attached a download link to my last answer to Thierry, it's a .tar file whose name contains the "bad" characters, same goes for the files and folders inside, and even the text in some of the files; if you have troubles downloading, let me know.
Regards
On Sat, Dec 14, 2024 at 03:03:45PM -0000, padota1663--- via tde-users wrote:
Ciao Michele,
the issue is that I don't specifically know the exact font which causes this issue; moreover, as I just told Thierry, this doesn't happen universally, so this leads me to think it's not a fonts issue, but rather some kind of bug elsewhere.
It might be helpful to know which *specific characters* are causing the issue.
Can you copy and paste some of these filenames into an email and post them here? Make sure your email is sending UTF-8 and not some legacy charset.
Hi Steve,
I just sent a download link in my last answer to Thierry, it's a .tar which name is affected; the name is: 𝘙𝘪𝘰𝘮𝘢.tar.bz2, feel free to download and test it.
Regards
On Mon, Dec 16, 2024 at 12:29:21AM -0000, padota1663--- via tde-users wrote:
Hi Steve,
I just sent a download link in my last answer to Thierry, it's a .tar which name is affected; the name is: 𝘙𝘪𝘰𝘮𝘢.tar.bz2, feel free to download and test it.
Those characters come through as
MATHEMATICAL SANS-SERIF ITALIC CAPITAL R MATHEMATICAL SANS-SERIF ITALIC SMALL I MATHEMATICAL SANS-SERIF ITALIC SMALL O MATHEMATICAL SANS-SERIF ITALIC SMALL M MATHEMATICAL SANS-SERIF ITALIC SMALL A
Is that what you are expecting?
Yes, it's correct, these are the letters I expect to see.
I see that an issue has been created on TGW by Michele in the meantime.
padota1663--- via tde-users wrote:
I opened this thread in the Q4OS Support Forum: https://www.q4os.org/forum/viewtopic.php?pid=27828#p27828 and they told me it's a Trinity related bug, as it also happens on a pure Debian fresh install with TDE.
It doesn't happen here when I install from scratch. I usually use UTF-8 US English for installing and after this I add German, Bulgarian, Russian etc. But I do not use Dolphin and I do not have any other DE installed.
How can it be solved?
Hard to say where the issue is. Usually it happens when the fonts used do not have the required symbols. What language and locale settings do you have? What Theme, which fonts are configured? Does it happen on native TDE apps?
In your case it seems to be related to the filesystem. There are the so called console fonts used.
There were some issues in the past with wrong encodings or double encoding of characters and I recall many of these were fixed, but I am sure there are still some places where it is not perfectly done. From the screenshots it seems it has to do with the theme and the font settings. Does it change, when you change those? I suggest you write down a test scenario and try it with new user.
Also look here ... might be the same https://mirror.git.trinitydesktop.org/gitea/TDE/tdebase/issues/236
BR
Hi deloptes,
I immediately chose, during installation, to install IT-IT UTF-8, this installed the locale alongside EN-US UTF-8, then I removed EN-US as it was causing some issues (my system crashed once, and when I reset, it reverted back to having EN-US as default, so I removed it); can this be the issue? I hope not, since, as I stated before, in Firefox everything displays correctly, in other applications like Dolphin, Konsole and VLC this isn't the case.
This is the output of locale run as root:
root@scatorcio:~# locale LANG=it_IT.UTF-8 LANGUAGE= LC_CTYPE="it_IT.UTF-8" LC_NUMERIC=it_IT.UTF-8 LC_TIME=it_IT.UTF-8 LC_COLLATE="it_IT.UTF-8" LC_MONETARY=it_IT.UTF-8 LC_MESSAGES="it_IT.UTF-8" LC_PAPER=it_IT.UTF-8 LC_NAME=it_IT.UTF-8 LC_ADDRESS=it_IT.UTF-8 LC_TELEPHONE=it_IT.UTF-8 LC_MEASUREMENT=it_IT.UTF-8 LC_IDENTIFICATION=it_IT.UTF-8 LC_ALL= root@scatorcio:~#
But wait... When you said "Does it happen on native TDE apps?" you had me thinking... So I double checked, and I found that, for VLC for example, both "q4os-vlc" and "vlc" installed; the same goes for Konsole (I have "konsole-trinity" but not "konsole" installed) and Dolphin ("dolphin-trinity" instead of "dolphin"); but this is strange, 'cause also Firefox has "q4os-firefox" and "firefox" installed, and it doesn't have this issue.
Should I try installing the "pure" versions of these programs and remove the customized ones?
I use the Debonaire theme, which is the default on Q4OS, the "general" font is Noto Sans UI 9.
In the meantime, I'm gonna create a test user and change its theme and font settings, to see if the issue arises even with a new user; I'll also check the link you posted.
PS: sorry, how do I insert links, images and quotes in my messages?
Thanks
Hi deloptes,
I checked the link, but in that case the system locale was different from the TDE language, which is not my case; I also created a brand new test user, it also has the same issue of tofu boxes; even changing the default theme and logging back in doesn't solve the issue, I don't know if it has to do with the customized apps, even with the new user.
Regards
padota1663--- via tde-users wrote:
I checked the link, but in that case the system locale was different from the TDE language, which is not my case; I also created a brand new test user, it also has the same issue of tofu boxes; even changing the default theme and logging back in doesn't solve the issue, I don't know if it has to do with the customized apps, even with the new user.
What is exactly the font that you use to create this file name? It seems some kind of italic font. Can you check in kcharselect - type the name of the font, so that it loads and see how the chars are being represented
On Tue, 17 Dec 2024 12:47:38 +0100 deloptes via tde-users users@trinitydesktop.org wrote:
padota1663--- via tde-users wrote:
I checked the link, but in that case the system locale was different from the TDE language, which is not my case; I also created a brand new test user, it also has the same issue of tofu boxes; even changing the default theme and logging back in doesn't solve the issue, I don't know if it has to do with the customized apps, even with the new user.
What is exactly the font that you use to create this file name? It seems some kind of italic font. Can you check in kcharselect - type the name of the font, so that it loads and see how the chars are being represented
Judging from an earlier message in this thread, they're using mathematical symbols, which happen to look like italic letters in whatever font they're using, to fake italics. They are *not* really letters according to the Unicode standard, and *not* in an italic font in the normal sense, and I would consider using them to substitute for real letters in a filename to be . . . technically not misuse, but a Really Bad Idea anyway. It still shouldn't cause things to break, but I don't find the breakage (or the confusion surrounding it, since the OP seems unaware of the semantics of the codepoints they're using) particularly surprising.
E. Liddell