My last post implied that I ego-surfed and found a Wikipedia chat entry about me, but thatâs not the case. I was searching for information on how to remove a system-protected font from Windows 10, and seeing as I often post solutions to obscure technical issues on here, I had hoped I recorded my how-to last time. The libel posted by some Australian Wikipedia editor came up during that search.
Once upon a time, Microsoft didnât care if you removed system fonts, but at some point, it began protecting Arial, whose design, for reasons Iâve gone into elsewhere, Iâve always considered compromised. There was one stage where you could replace Arial with something else called Arial, and as I had a licence for a very, very old Agfa version of Helvetica (do people remember CG Triumvirate?!), I decided to modify its file name to fool Windows into thinking all was well.
The last time Windows did an updateâversion 1909âI had to resort to a safe-mode boot and taking control of the font files as admin, but I really could not remember the specifics. The problem is that when you install the ânewâ Arial, the existing roman one is used by quite a few applications, and you donât really replace itâyour only solution is to delete it.
With version 2004, safe mode is quite different, and the command prompt and Powershell commands I knew just didnât cut it. I realize the usual solution is to go into the registry keysâIâve used this one for a long, long timeâand to remove or modify the references to the offending fonts at HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Fonts. Iâve also used the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\FontSubstitutes key to make sure that Helvetica does not map on to Arial (in fact, I make sure Arial maps on to Helvetica). Neither actually works in this case; they are ignored, even bypassed by certain programs. And, really, neither deletes the file; they just attempt to have Windows not load them, something which, as I discovered, doesnât prevent Windows from loading them.
By all means, use these methods, but be prepared for the exception where it doesnât work. The claim that the methods âdeleteâ the fonts is actually untrue: they remain in C:\Windows\Fonts.
The other methods that do not work are altering the equivalent keys under WOW6432node (which get intercepted and directed from the 32-bit keys anyway), using an elevated command prompt to delete the files (at least not initially), or doing the same from safe mode (which is very different now, as safe mode is in the same resolution and the Windows\Fonts folder displays as it does in the regular modeâso you cannot see the files you have to remove). You cannot take ownership of the font files through an elevated Powershell (errors result), nor can you do this from safe mode. Nothing happens if you delete FNTCACHE.DAT from the system32 directory, and nothing happens if you delete ~fontcache files from the Local directory.
What was interesting was what kept calling arial.ttf in the fontsâ directory even after âmyâ Arial was loaded up. The imposter Arial loaded in most programs, but for the Chromium-based browsers (Vivaldi, Edge), somehow these knew to avoid the font registry and access the font directly. This was confirmed by analysing the processes under Process Monitor: sure enough, something had called up and used arial.ttf. This Wikihow article was a useful lead, getting us to delete the fonts under the Windows\WinSxS folder, and showing how to take ownership of them. I donât know if altering these ultimately affected the ones inside Windows\Fonts, but I followed the instructions, to find that the original Arial was being accessed by three programs: Vivaldi, Keybase, and Qt Qtwebengineprocess. I shut each one of these down and removed the Arial family.
Reboot: it was still there. Then it hit me, and I posted the solution in the Microsoft Answers forum (perhaps inadvertently prompting a Microsoft programmer to make things even harder in future!). Another user had told me it was impossible, but I knew that to be untrue, since it had been possible every other time.
The solution is pretty simple: since you canât see the full Windows\Fonts directory with Windows Explorer, then I needed another file manager.
Luckily, I had 7zip, which I opened as an administrator. It allowed me to go into the folder and view all its contents, not just the fonts called up under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Fonts, which we know is not an accurate representation of the fonts being used by the system. From there I could finally delete the offending four fonts without changing the ownership (which makes me wonder if the Wikihow advice of changing the owner under Windows\WinSxS wound up affecting the Windows\Fonts files). Once again, I had to close Keybase, Vivaldi and Qt Qtwebengineprocess.
It took from c. 4 p.m., when my desktop PC updated to v. 2004 (my laptop had been on it for many weeks; soon after its release, in fact) to 2 a.m., with a break in between to cook and eat dinner. Iâm hoping those hours of having typographic OCD helps others who want to have a font menu where they determine what they should have. Also, user beware: donât delete stuff that the system really, really needs, including an icon font that Windows uses for rendering its GUI.
Using Google as a last resortâexcept this search, which I did again as an illustration, now displays in CG Triumvirate rather than Arial. Normally, Google is a big Arial user (Arial and sans-serif are in the CSS specs) and Chromium browsers are all too happy to circumvent the registry-registered fonts and go straight into your hard drive.
Jack Yan is not a notable typeface designer. He has never laid a hand on mouse or trackball to operate a font editing application. He tells some graphic designer employees of his what he wants them to draw with software, and has them do all the work of drawing and solving all the design problems involved in creating and designing a typeface and its fonts. As a professional typeface designer myself, Yan’s involvement in type design and font production does not qualify him as a typeface designer. Not even close.
The user is called James Arboghast, whom Iâve never heard of in any of my years in the type design business.
Now, you can argue whether Iâm notable or not. You might not even like my designs. But given that Arboghast has such a knowledge of our inner workings, then maybe it would suggest that I am?
Based on the above, which is libellous, let me say without fear of committing the same that, in this instance, Mr Arboghast is a fantasist and a liar.
Iâve no beef with him outside of this, but considering that I was the first typeface designer in this country to work digitallyâso much so that Joseph Churchward, who is indisputably notable, came to me 20 years ago to see if we could work togetherâthere were no âgraphic designer employeesâ around who had the skills. At least none that I knew of when I was 14 years old and deciding which bitmaps to light up on an eight-by-eight grid.
There were still no such people around when I began drawing stuff for submission to ITC, or when I began drawing stuff that I digitalized myself on a hand-held scanner. I certainly couldnât afford employees at age 21 when I asked my Mum to fork out $400 to buy me a really early version of Fontographer. And there were still no such people around when I hand-kerned 1,000 pairs into my fonts and did my own hinting. Remember, this was pre-internet, so when youâre a young guy in Wellington doing this work in isolation, you had to know the skills. I might even have those early drawings somewhere, and not that long ago I found the maths book with the bitmap grid.
If I didnât know about the field then I certainly would have been found out when the industry was planning QuickDraw GX and I was one of the professional typeface designers advising on the character sets, and if I didnât know how to solve design problems, then the kerning on the highway signsâ type in this country would not comply with NZS. (The kerning is terrible, incidentally, but government standards are government standards. It was one of those times when I had to turn in work that I knew could be far, far better.) I’d also have been seriously busted by my students when I taught the first typeface design course in New Zealand. Every single retail release we have has been finished by me, with all the OpenType coding done by me. All the alternative characters, all the ligatures, all the oldstyle numerals and accented characters in languages I canât begin to fathom. Latin, Cyrillic and Greek. Iâve tested every single font weâve released, whether they are retail or private commissions.
The only time a team member has not been credited in the usual way was with a private commission, for a client with whom I have signed an NDA, and that person is Jasper Luki, a very talented young designer with whom I had the privilege to work at the start of his career in the 2010s.
The fact that people far, far more famous than me in the type field around the world, including in his country, come to me with contract work might suggest that, if Iâm not notable, then Iâm certainly dependable.
And people wonder why I have such a low opinion of Wikipedia, where total strangers spout opinions while masquerading as experts. The silver lining is that writing the above was a thoroughly enjoyable trip down memory lane and a career that Iâm generally proud of, save for a few hiccups along the way.
I hadn’t expected this reply Tweet to get so many likes, probably a record for me.
I knew my parents couldnât afford The Lettering Book, so I went without, which forced me to create my own typeface designs. Later I became the first digital typeface designer in this country.
It is true. That book was NZ$4·99 in 1979, when it was offered through the Lucky Book Club at school, at a time when many books were still priced in cents. Some kids in the class got it, and I admit I was a bit envious, but not having a book in an area that interested you can drive creativity. While my parents didn’t make a heck of a lot in the 1970sâwe flatted and didn’t own our own car at this pointâthey would have splashed out if I really insisted on it. After all, they were sending me to a private school and their sacrifice was virtually never going out. (I only recall one night in those days when my parents had a “date night” and my maternal grandmother looked after meâand that was to see Superman II.) But when you grow up having an understanding that, as an immigrant family that had to largely start from scratch in a new country, you have a rough idea of what’s expensive, and five bucks for a book was expensive.
As an adultâeven when I was a young man starting out in my careerâI did not regret not having this book.
Someone in the thread asked if I ever wound up buying it. I never did: as a teenager I managed to get my hands on a very worn Letraset catalogue, which ultimately proved far more interesting. But it is good to know that, thanks in large part to my parents’ and grandmother’s sacrifices, and those in my partner’s family who helped her in her earlier years, we could afford to buy this book if anyone in our family asks for it.
Were we fleeing anything when we came to Aotearoa? We left Hong Kong in 1976 because my parents were worried about what China would do to the place. In other words, what’s happening now is what they hoped for me to avoid. They called it, in the 1970s. And here I am.
It took two months but I finally got there.
Vivaldi now displays type normally though the browser interface is slightly messed up. But Iâll take good type display, thanks. On the MacType forums, a user in China called wmjordan was in the same boat but had found a solution. In their words:
For the recent version of Vivaldi 2.10, 2.11, you need to create a shortcut, and modify the command line, append the "--disable-lcd-text" parameter behind the executable name, and MacType will work on the web page content window. The "--disable-features=RendererCodeIntegrity" parameter is recommended by snowie2000.
I used the latter method, but the type was still quite poor for me. I had to do one more thing: start Vivaldi in Windows 8 compatibility mode.
Itâs messed up the top of the browser a little but itâs a small price to pay to have everything readable again.
Snowie2000, the main dev for MacType, says a registry hack is their preferred workaround, at github.com/snowie2000/mactype/wiki/Google-Chrome#workaround-for-chrome-78.
It turns out that Chrome 78 (and presumably Chromium 78, too) did indeed have a change: âStarting from Chrome 78, Chrome began to block third-party DLLs from injection. But they provided a way to disable the protection either from the command line or by policy.â
I was right to have investigated which version of Vivaldi represented the change earlier (it was 2.9, which equated to Chromium 78). After testing wmjordanâs suggestions out on 2.9, I upgraded to 2.11, and it was still fine. Opera GX is still the more resolved browser (works as it should out of the box) but there are some aspects of Vivaldi that Iâm familiar with after two-and-a-half years (to the day). Looks like Iâll be going back to it for my main browsing, but I know Iâve found another great browser along the way, and Iâve updated my Firefox, too.
That was confusing. Yesterdayâs blog post was representative of my thinking: given that certain people were upset when Chromium took away the Directwrite toggle in 2016, and type rendering on Chromium-based Vivaldi deteriorated significantly for me with v. 2.10 (it turns out v. 2.9 was the turning-point), then did Chromium only switch fully to Directwrite for me earlier this year? Luckily I wrote a caveat: âThereâs a possibility that what I saw from 2017 actually was Directwrite, and whatever theyâre using now is yet another technology that no one has made any note of.â
Snowie2000, one of the developers of MacType, suggested I try Cent Browser, arguably the only Chromium browser that still has a Directwrite toggle: you could still disable it in favour of GDI.
Cent Browser by default is marginally better than what I was seeing on Edge, Vivaldi 2.10 and others, but once I turned Directwrite off, I saw a very different display, with far heavier type.
Cent Browser, Directwrite switched off
Cent Browser, default
Edge
It wasnât what I expected to see, and without taking issue with those who support GDI rendering in Chromium, it lacked fidelity (at least for me) with what the type looked like in print. I can see clearly why it has its adherents: it is superior to the default. But, in other words, what I experienced on Vivaldi between 2007 and January 2020 was using Directwrite, and whatever is going on now is using something else, or ignoring other settings on my PC.
Yesterday I theorized that if the change happened between Chromium 77 and 78, then I should see that in the source browser. I installed a v. 77 from the repository. As you know, these are stand-alone and can run without a full installation. What I saw was the inferior rendering, so the âswitchâ didnât happen then. It may have happened, as I was told on the Vivaldi forums, with Chromium 69, something I am yet to confirm.
Therefore, whatever Chromium is doing isnât something thatâs been documented, to my knowledge, except for here. And Opera and Opera GX, if they are based on Chromium 79, seem not to be afflicted by this bug. Or they are interacting with other programs I have in order to keep the type rendering faithful, with decent hinting and contrast.
The question is: what is causing the far inferior type display on Chromium today?
PS.: Trials on Chromium 68 and 69âthey’re the same (i.e. poor type display). This may have gone on for quite some time.âJY
After considerable searching, the bug that I reported to Vivaldi, and which they cannot reproduce, appears to be one that the general public encountered back in 2016, when Chromium took away the option to disable its Directwrite rendering. I donât know why Iâve only encountered it in 2020, and as far as I can tell, my experience is unique.
Itâs a good position to be inânot unlike being one of two people (that I know of) who could upload videos of over one minute to Instagram without using IGTVâthough itâs a mystery why things have worked properly for me and no one else.
When I switched to Vivaldi in 2017, I noticed how the type rendering was superior compared with Firefox, and it was only in January this year when it became far inferior for me. Looking at the threads opened on type rendering and Chromium, and the screenshots posted with them, most experienced something like this in 2016âa year before I had adopted Vivaldi. If my PC worked as theirs did, then I doubt I would have been talking about Vivaldiâs superior display.
There’s a possibility that what I saw from 2017 actually was Directwrite, and whatever they’re using now is yet another technology that no one has made any note of.
Iâve posted in the Vivaldi and MacType forums where this has been discussed, as my set-up could provide the clue on why things have worked for me and not others. Could it be my font substitutions, or the changes Iâve made to the default display types in Windows? Or the fact that I still have some Postscript fonts installed from the old days? Or something so simple as my plug-ins?
Tonight I removed Vivaldi 2.11 and went to 2.6. I know 2.5 rendered type properlyâBembo on the Lucire website looks like Bembo in printâso I wondered if I could narrow down the precise version where Vivaldi began to fail on this front. (As explained earlier, after 2.5, no automatic updates came, and I jumped from 2.5 to 2.10.)
It was 2.9 where the bug began, namely when Vivaldi moved from a Chromium 77 base to a 78 one. This is different to what Ayespy, a moderator on the Vivaldi forums, experienced: version 69 was when they noted a shift. Yet Opera GX, which works fine, has a browser ID that claims itâs Chrome/79.0.3945.130 (though I realize they can put whatever they like here). Brave, Chrome and Edge look awful.
We can conclude that not all Chromium browsers are created equally (goes without saying) but I understand that the rendering isnât something that each company (Vivaldi, Opera, etc.) has fiddled with. Therefore, something Iâm doing is allowing me to have better results on Opera, Opera GX and Vivaldi versions up to 2.8 inclusive.
I wonder if itâs time to return to Firefox after an absence of two years and five months. After getting the new monitor, the higher res makes Firefoxâs and Opera GXâs text rendering fairly similar (though Chrome, Vivaldi and Edge remain oddly poor, and Vivaldiâs tech people havenât been able to replicate my bug). Thereâs a part of me that gravitates toward Firefox more than anything with a Google connection, and I imagine many Kiwis like backing underdogs.
Here are some examples, bearing in mind Windows scales up to 125 per cent on QHD.
Vivaldi (Chrome renders like this, too)
Opera GX (and how Vivaldi used to render)
Firefox
Opera renders text slightly more widely than Firefox, but the subpixel rendering of both browsers is similar, though not identical. Type in Firefox arguably comes across with slightly less contrast than it should (especially for traditionally paper-based type, where I have a good idea of how itâs âsupposedâ to look) but Iâm willing to experiment to see if I enjoy the switch back.
In those 29 months, a lot has happened, with Navigational Sounds having vanished as an extension, and I had to get a new Speed Dial (FVD Speed Dial) to put on my favourite sites. FVD uninstalled itself earlier today without any intervention from me, so if that recurs, Iâll be switching to something else. I donât like computer programs having a will of their own.
A lot of my saved passwords no longer work, since I change them from time to time, and it was interesting to see what Firefox remembered from my last period of regular use. Iâll have to import some bookmarks, tooâthat file has been going between computers since Netscape.
The big problem of 2017âFirefox eating through memory like crazy (6 Gbyte in a short time)âcould be fixed now in 2020 by turning off hardware acceleration. Itâs actually using less right now than Opera GX, and thatâs another point in its favour.
I also like the Facebook Container that keeps any trackers from Zuck and co. away.
I did, however, have to get new extensions after having resided in the Vivaldi and Opera space for all that time, such as Privacy Badger.
If I make Firefox the default I know Iâll have truly switched back. But that Opera GX sure is a good looking browser. I might have to look for some skins to make common-garden Firefox look smarter.
The Dell P2418D: just like the one I’m looking at as I type, but there are way more wires coming out of the thing in real life
Other than at the beginning of my personal computing experience (the early 1980s, and thatâs not counting video game consoles), Iâve tended to have a screen thatâs better than average. When 640 Ă 360 was the norm, I had 1,024 Ă 768. My first modern laptop in 2001 (a Dell Inspiron) had 1,600 pixels across, even back then. It was only in recent years that I thought my LG 23-inch LCD, which did full HD, was good enough, and I didnât bother going to the extremes of 4K. However, with Lucire and the night-time hours I often work, and because of a scratch to the LG that a friend accidentally made when we moved, I thought it was time for an upgrade.
Blue light is a problem, and I needed something that would be easier on the eyes. At the same time, an upgrade on res would be nice.
But there was one catch: I wasnât prepared to go to 27 inches. I didnât see the point. I can only focus on so much at any given time, and I didnât want a monitor so large that Iâd have to move my neck heaps to see every corner. On our work Imacs I was pretty happy to work at 24 inches, so I decided Iâd do the same for Windows, going up a single inch from where I was. IPS would be fine. I didnât need a curved screen because my livelihood is in flat media. Finally, I don’t need multiple screens as I don’t need to keep an eye on, say, emails coming in on one screen, or do coding where I need one screen for the code and the other for the preview.
Oddly, there arenât many monitor manufacturers doing QHD at 24 inches. There was a very narrow range I could choose from in New Zealand, with neither BenQ nor Viewsonic doing that size and resolution here. Asus has a beautifully designed unit but I was put off by the backlight bleed stories of four years ago that were put down to poor quality control, and it seemed to be a case of hit and miss; while Dellâs P2418D seemed just right, its negative reviews on Amazon and the Dell website largely penned by one person writing multiple entries. I placed the order late one night, and Ascent dispatched it the following day. If not for the courier missing me by an hour, Iâd be writing this review a day earlier.
I realize weâre only hours in to my ownership so there are no strange pixels or noticeable backlight bleed, and assembly and installation were a breeze, other than Windows 10 blocking the installation of one driver (necessitating the use of an elevated command prompt to open the driver executable).
With my new PC that was made roughly this time last year, I had a Radeon RX580 video card with two Displayport ports, so it was an easy farewell to DVI-D. The new cables came with the monitor. A lot of you will already be used to monitors acting as USB hubs with a downstream cable plugged in, though that is new to me. It does mean, finally, I have a more comfortable location for one of my external HDs, and I may yet relocate the cable to a third external round the back of my PC.
Windows 10 automatically sized everything to 125 per cent magnification, with a few programs needing that to be overridden (right-click on the program icon, then head into âCompatibilityâ, then âChange high DPI settingsâ).
Dellâs Display Manager lets you in to brightness, contrast and other settings without fiddling with the hardware buttons, which is very handy. I did have to dial down the brightness and contrast considerably: Iâm currently at 45 and 64 per cent respectively.
And I know itâs just me and not the devices but everything feels faster. Surely I can’t be noticing the 1 ms difference between Displayport and DVI-D?
I can foresee this being far more productive than my old set-up, and Ascentâs price made it particularly tempting. I can already see more of the in- and outbox detail in Eudora. Plantin looks great here in WordPerfect (which I often prep my long-form writing in), and if type looks good, Iâm more inclined to keep working with it. (It never looked quite right at a lower res, though it renders beautifully on my laptop.)
I feel a little more âlate 2010sâ than I did before, with the monitor now up to the tech of the desktop PC. Sure, itâs not as razor-sharp as an Imac with a Retina 4K display, but I was happy enough in work situations with the QHD of a 15-inch Macbook Pro, and having that slightly larger feels right. Besides, a 4K monitor at this sizeâand Dell makes oneâwas outside what I had budgeted, and Iâm not sure if I want to run some of my programsâthe ones that donât use Windowsâ magnificationâon a 4K screen. Some of their menus would become particularly tiny, and that wonât be great for productivity.
Maybe when 4K becomes the norm Iâll reconsider, as the programs will have advanced by then, though at this rate Iâll still be using Eudora 7.1, as I do today.
Surprisingly, Vivaldi hadnât notified me of any updates for monthsâI was on v. 2.05, and had no idea that they were up to 2.10. Having upgraded manually, I noticed its handling of type had deteriorated. Here is one paragraph in Lucire:
My font settings had also changed.
Coincidentally, I downloaded Opera GX last night to have a go, and it displays type in the way Iâm used to:
Since both are Chromium-based, and Opera is sensitive about privacy as Vivaldi is, I decided to make the change and see if I like the new browser better. I was used to Operas of old being independent, not Chromium-based, but the good news is I could use the same plug-ins.
Iâm missing Vivaldiâs easy screenshot process and its clipping (Opera GX has something similar but introduces an extra step of saving the file) but so far the browsers arenât too different in terms of everyday functionality. Opera GXâs extensionsâ window isnât as well organized and I have to scroll to tinker with the settings of anything later in the alphabet.
The unchangeable dark theme takes a bit of getting used to (but it matches my laptop, so thereâs that), and thereâs a GX home page thatâs superfluous for me.
I donât need the built-in ad blocker out of principle, but I do have certain anti-tracking plug-ins (e.g. Privacy Badger) that I was able to install from the Opera shop without incompatibility.
Hard-core gamers may like the CPU limiter and RAM limiter, to make sure the browser doesnât eat up capacity for their games. Itâs not something I need concern myself about, but I can see it being handy. I remember when old Chrome (many years ago) and Firefox (more recently) began eating memory like crazy with my settings (no idea why), and this would have been useful.
But as someone who reads online a lot, itâs important that type is properly handled. I donât know what Vivaldi has done to its type rendering, and thatâs probably the biggest thing that tipped me in favour of change.
That #Brexit bill is typeset in Palatino. That was designed by a German. Come on, people, donât you want to use British typefaces? Tell Johnny Foreigner what you think of his fonts!
Strictly speaking, I realize it was Book Antiqua, though as we all know, that’s a Palatino clone.
Since even English types like Baskerville were influenced by what was happening on the Continent, for official use, the UK really needs to go back to Old English. And yes, I realize that suggestion has unpleasant parallels to what was going on in Germany in the 1930s âŠ
There was a great follow-up to my Tweet, incidentally:
I need a "Tell Johnny Foreigner what you think of his fonts!" tee shirt, and I do not even wear clothes with writing on them.
